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

From: Charles Schultz <>
Date: Mon, 8 Sep 2008 14:09:28 -0500
Message-ID: <>

We did mention that bug back when we filed the SR, and eventually Oracle Support said:
"your Standby does not use VALID_FOR=(ONLINE_LOGFILE, PRIMARY_ROLE) in the LOG_ARCHIVE_DEST parameter."

"Can't hurt. I don't think." I am going to stick the BAAG on you guys! =) I do not think service registration is the issue at all, since I can reproduce the symptoms by merely switching the log_arch_dest_2 parameter back to the known problematic alias. Keep in mind that the service_name has never changed, only the alias we are using to get to it.

Oh the joys of Oracle. I am just waiting for the Oracle trolls to say * something*.... *grin*

For the curious (and have all the proper privs), the two SRs I have are 7057019.994 and 19545566.6.

On Mon, Sep 8, 2008 at 1:58 PM, David Barbour <>wrote:

> 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.

Charles Schultz

Received on Mon Sep 08 2008 - 14:09:28 CDT

Original text of this message