Re: Primary gets ora-16009 when attempting a heartbeat with standby

From: David Barbour <>
Date: Mon, 8 Sep 2008 14:58:07 -0400
Message-ID: <>

Interestingly, there is a Bug in, #4676659. Unfortunately, it's supposed to report in BOTH the primary and standby alert logs. Further, although the Bug is listed for Physical Standbys, the text refers to Logical Standbys. Gotta love that type of inconsistency from your vendor.

Anyway, I'm wondering what might happen if you ran an alter system register; on both databases? If you've got some type of service inconsistency related to OID, that might resolve it. Can't hurt. I don't think.

On Mon, Sep 8, 2008 at 2:35 PM, Finn Jorgensen <>wrote:

> If you're at a Unix prompt on the Primary server and do a
> sqlplus "sys/pwd_at_prodstby as sysdba"
> Do you end up in the standby database?
> What is the output of :
> show parameter 2 (or whatever destination is your standby)
> show parameter remote
> show parameter fal
> show parameter standby
> Finn
> On Mon, Sep 8, 2008 at 12:00 PM, Charles Schultz <>wrote:
>> Interesting, Oracle Support shared the same idea this morning. =) No
>> errors in the alert.log on the standby. We are not using tnsnames.ora (oid
>> ldap instead), but tnsping shows appropriate responses in all cases. I am
>> not sure what the listener has to do with it since the tns alias points to
>> the same service name. But Oracle Support is asking for more information
>> (ie, listener.log, etc), so we will see if that proves to be helpful or not.

Received on Mon Sep 08 2008 - 13:58:07 CDT

Original text of this message