Re: Oracle Standby - DB_UNIQUE_NAME
Date: Thu, 13 Apr 2023 15:56:41 +0000
Message-ID: <LO2P123MB4446569E0601DAE99DD565A4EF989_at_LO2P123MB4446.GBRP123.PROD.OUTLOOK.COM>
Hello Andrew
Thanks for coming back.
I missed a detail in the original email.
The DB_UNIQUE_NAME is set on the primary and the standby in the SPFILE. The table V$DATABASE column DB_UNIQUE_NAME on the standby is what is blank while it is populated on the Primary.
From: Andrew Kerber <andrew.kerber_at_gmail.com> Sent: Thursday, April 13, 2023 4:53 PM
To: chinedui_at_live.co.uk <chinedui_at_live.co.uk> Cc: oracle-l_at_freelists.org <oracle-l_at_freelists.org> Subject: Re: Oracle Standby - DB_UNIQUE_NAME
I cant swear to this, but I think the unique name will show as blank if the db_name is the same as the db_unique_name.
On Thu, Apr 13, 2023 at 10:51 AM Ndidi Ibeachum <chinedui_at_live.co.uk<mailto:chinedui_at_live.co.uk>> wrote: Hello Team
I have an issue. We have an Oracle 11g Database running on AIX. This also has a standby configured. The archives are synced to a directory on the standby server and recovery is performed every 20 minutes to keep the standby in sync.
I observed an anomaly while fixing one of our shell scripts and found that the V$DATABASE table column - DB_UNIQUE_NAME is blank but the parameter is set on both the standby and primary.
Checked an oracle note - 2491642.1 which spoke about this but pointed to PRIMARY_DB_UNIQUE_NAME.
I have checked all the parameters and even RMAN and yet I am baffled at how this happened. Has anyone come across this before and what can be done to remedy it?
Appreciate your feedback.
Thanks so much
Chinedu I.
--
Andrew W. Kerber
'If at first you dont succeed, dont take up skydiving.'
--
http://www.freelists.org/webpage/oracle-l
Received on Thu Apr 13 2023 - 17:56:41 CEST