Data Guard

Just a short post on this error code. Happened last time I recreated a physical standby . I could not find more than the reference note on this error on Metalink (a note that is just a copy of the output from command oerr ora 16047): Cause: The DB_UNIQUE_NAME specified for the destination does not match the DB_UNIQUE_NAME at the destination. Action: Make sure the DB_UNIQUE_NAME specified in the LOG_ARCHIVE_DEST_n parameter defined for the destination matches the DB_UNIQUE_NAME parameter defined at the destination. ...

After the incident with missing forced logging in primary database the logical standby had to be created again. Compared to what is normal these days the database is not huge, but the standby database remains on a server in a different city and the link between isn’t exactly a digital super highway. Also I had to restrict the consumed bandwidth during transfer with secure copy (scp -l 2500, restricts to 2500 kbs) or else connections to the primary database might suffer. ...

When you start with Oracle Data Guard you have three sources of useful information: The Data Guard Concepts and Administration manual, which is quite good, other peoples experience, and after some time your own. The manual does not include all the mistakes one can do, nor what many really don’t use (like the data guard broker; not everybody would leave switchover, or worse failover to a robot). After a planned switchover to the physical standby the following ora-600 error message was received on our logical standby: ...