High Availability Data Guard, Sharding and Global Data Services (MOSC)

MOSC Banner

Log_archive_dest Issue

 I had an issue today where my production database wouldn't come up after a server reboot (yes, I said production).  I was able to figure out that it was an issue with the log_archive_dest parameter values being used for archiving and data guard.  The 2 parameters being used were log_archive_dest and log_archive_dest_1 which I come to find out don't work well together come database start up time.  I have changed the log_archive_dest parameter to be log_archive_dest_2 in both the init.ora file and spfile and have my production database back on line.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center