|Archivelog Mode On RAC - The differences between resetting the archive log mode on a single node instance and a Real Application Cluster (RAC).|
Mahesh said...Its been short and sweet, very good for RAC novice!
vikash prasad sah said...good,proper sequence in archive start
Ankit said...In a very short and precise manner you have explained...
Arvind said...After issuing "srvctl stop database -d MYSID", does the ASM instance has to be started before issuing "STARTUP MOUNT" on (either) instance? Does "srvctl stop database -d MYSID" leave the ASM insance running or it stops that as well?
That is stopping the database instance, not the ASM instance, so you will be fine to just start again.
Dani said...I tried the code for a single node instance on an 9i standard editions, and met with the following problems:
- log_archive_dest_1 is not supported, you have to use log_archive_dest and don't use location=
- log_archive_format %r is not supported, this is a tricky one since archiving stopped working and database became stale.
Milind said...This means the whole clustered database must be stopped before the operation can be performed. First we set the relevant archive parameters.
ALTER SYSTEM SET log_archive_start=TRUE SCOPE=spfile;
log_archive_start is deprecated and should not be set even after stating that it is deprcated infact are incompatible if used with log_archive_dest_n
It's a 9i article. It worked fine in 9i.
I later added the mention of 10g upward is just to stop people getting confused. I did not rewrite the whole article, hence the repeated references to the deprecated parameters.
I've split the article up into sections to make it a little clearer.
what I was trying to say is that:
- log_archive_dest_n is not supported on Standard Edition
- %r is not supported on Oracle 9i ( http://docs.oracle.com/cd/B10501_01/server.920/a96536/ch195.htm#REFRN10089 ). If you set log_archive_dest with %r, the DB will not be able to generate archive log.
Tim... said...OK. :)