Skip to Main Content

Database Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

LOG_ARCHIVE_DEST_2 parameter error and can't start up the primary database

user560159Apr 30 2012 — edited May 4 2012
Hi There,
I was getting errors in my RMAN backup script. I took a look at the database parameters. It looks like I made a mistake when I was setting the LOG_ARCHIVE_DEST_2 parameter within the standby database. Instead of setting it to the standby I set it to the primary instance name. I also noticed that the LOG_ARCHIVE_DEST_2 parameter was changed in the primary database where I first set it. I guess it changed when I changed the standby parameter. I have two questions:

1) Can the LOG_ARCHIVE_DEST_2 parameter be changes to the correct setting now that I have it set incorrectly. The reason I ask is because when I tried to change it using the following ALTER SYSTEM command I got an error saying something about conflicting attributes. I'm guessing it was because the primary instance name was set to the DB_UNIQUE_NAME instead of the standby instance name. If I could change the LOG_ARCHIVE_DEST_2 parameter on the standby first then maybe I can change the primary to the correct setting as well? Please provide steps.

ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=<PRIMARY DB>ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=<PRIMARY_INSTANCE>'

2) The second question is can you start a database using an spfile? (I am using ASM and data guard) The reason I ask is because while I was connected to the primary database I executed the following command:

ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=<PRIMARY_INSTANCE>ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=<PRIMARY_INSTANCE>' scope=spfile;

I then shutdown the database and tried to start it up but it won't start up because it says conflicting attributes. I didn't create a pfile from spfile before shutting down the database. (I know bad move). How can I change the parameter to get the primary database to start again. (The PFILE is different in ASM. It exists under +DATA but only has one line in it stating where the SPFILE location is) Will I have to run the following in RMAN RESTORE CONTROLFILE FROM AUTOBACKUP;

Please help as this is a production environment that was suppose to be delivered yesturday.

Any help will be greatly appreciated!

Thanks in advance.

J
This post has been answered by mseberg on May 1 2012
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 1 2012
Added on Apr 30 2012
61 comments
9,705 views