Problem solve
Get help with specific problems with your technologies, process and projects.
Purpose of CLUSTER_DATABASE parameter
We have a two-node RAC database. Recently we switched our production database from no archive log mode to archive log. We changed the parameter CLUSTER_DATABASE=FALSE on one of the instances before converting and reverted back. Could you tell me the functionality of this parameter?
We have an Oracle 9i (9.2.0.7) two-node RAC database running on Solaris 5.8. Recently we have switched our production database from no archive log mode to archive log. We changed the parameter CLUSTER_DATABASE=FALSE on one of the instances before converting and reverted back. Could you please tell me the functionality of this parameter and why this parameter needs to be changed to false?
In release 9.2 a database must be mounted exclusively in order to switch the archiving mode, in your case from noarchivelog to archivelog. A RAC configuration, which requires a parameter value of CLUSTER_DATABASE=TRUE, mounts the instance in parallel.
By setting CLUSTER_DATABASE=FALSE, you are configuring your system to be a single-node database. This in turn enables you to 'MOUNT EXCLUSIVE,' allowing you to switch the archive mode for the instance. As you indicated, you need to set this parameter value back to TRUE to re-establish your RAC configuration after the archiving mode has been changed.
In 10gr2, you need not change this parameter to accomplish this task; you merely have to make sure the instance you are working from is the only instance with the database mounted.
Also, it is very important to take a fresh FULL backup of your database after changing from noarchivelog to archivelog. You will need this backup as the starting point to apply your archive logs in case of recovery.
Start the conversation
0 comments