Comments on: A misleading ORA-16047

By: Geroge

Geroge — Fri, 17 Feb 2012 21:17:13 +0000

Your article is continuously helping people to resolve such puzzle. You save my time to rebuild the test env.
George

By: Harald van Breederode

Harald van Breederode — Tue, 03 May 2011 07:40:03 +0000

Hi Jeroen,

Thanx for sharing this. I guess this is another reason for using the broker instead of manually managing your Data Guard environment ;-)
-Harald

By: Jeroen Rijs

Jeroen Rijs — Fri, 29 Apr 2011 10:48:29 +0000

Hi Harald,

Thanks for this great tip! I had a simillar problem when building a standby database. At the standby database, the setting of log_archive_config was blank (default) and it was not blank at the primary site. After changing this setting, the shipment without using the broker, started. The mistake was caused by creating and editing parameter files for primary and standby databases in the wrong order.

Regards,

Jeroen Rijs

By: Aseem

Aseem — Thu, 16 Dec 2010 18:58:29 +0000

Hey Harald,

Thanks a ton…it worked for me as well :)

By: Arun Kumar

Arun Kumar — Tue, 22 Dec 2009 23:10:19 +0000

Hi Harold,

I have also the same prob. But i do not have RAC involved in this. Please help me out resolving this.
Please mail me.. thanks in advance

Regards
Arun Kumar

By: Ingo Wevers

Ingo Wevers — Fri, 20 Nov 2009 13:17:09 +0000

Hi Harold,

I got the advice to use this parameter to avoid message “Standby mount ID 0xf5cc6ffe not found ” which was continuously dumped into arc process trace file. And yes, I found your supporting article also.

Thanks,
Ingo

By: praveen

praveen — Sun, 05 Apr 2009 03:16:13 +0000

Your article saved me a lot of confusion and frustration as I was getting the same error!
Thanks

By: Paul van Eldijk

Paul van Eldijk — Tue, 24 Feb 2009 18:16:39 +0000

I’m glad you found the problem, because during class it was indeed puzzeling to see thsi behaviour. And I agree, DG broker is in many cases your friend :)

Paul