Conversion from NON-RAC to RAC using Mounted FS.... Basic Qs

  • From: "VIVEK_SHARMA" <VIVEK_SHARMA@xxxxxxxxxxx>
  • To: <oracle-l@xxxxxxxxxxxxx>
  • Date: Tue, 31 Oct 2006 17:42:09 +0530

Folks



Request a review of the following Steps for Conversion of NON RAC
Database to RAC using Mounted Filesystems.

Am NOT able to find the same in the Oracle 10g Documentation



Configuration

Solaris 10 , Oracle 10.2

NON-RAC Database existing on UFS

RAC Database to exist on Veritas SFRAC ver 5



Qs How will the names (with paths) for the Redologfiles of the 2nd
instance be specified? Is it's creation to be Coupled with Step 4 below?



Any Links, Docs on Conversion will help.



Thanks indeed





STEPS - For 2 node / instance RAC



1. In the initRACOL1.ora Set the following parameter (1 Time) in
addition to the required RAC parameters mentioned below in Appendix



_no_recovery_through_resetlogs=TRUE



2. RE-Create the Controlfile



"startup nomount" & Run the Trace SQL file for RE-Creating the
Controlfile



3. Add the 2nd thread

SQL>ALTER DATABASE ENABLE PUBLIC THREAD 2; 



4. Remove the following from initRACOL1.ora



_no_recovery_through_resetlogs=TRUE





APPENDIX



Sample initRACOL1.ora



*.db_name                  = RACOL

*.cluster_database=true

*.cluster_database_instances=2

*.service_names='RACOL'  # is same as db_name



RACOL1.instance_name=RACOL1

RACOL1.thread=1

RACOL1.instance_number=1

RACOL1.undo_tablespace=UNDO_TABLESPACE1



RACOL2.instance_name=RACOL2

RACOL2.thread=2

RACOL2.instance_number=2

RACOL2.undo_tablespace=UNDO_TABLESPACE2



RACOL1.LOCAL_LISTENER='LISTENER_RAC1'

RACOL2.LOCAL_LISTENER='LISTENER_RAC2'





**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are 
not to copy, disclose, or distribute this e-mail or its contents to any other 
person and any such actions are unlawful. This e-mail may contain viruses. 
Infosys has taken every reasonable precaution to minimize this risk, but is not 
liable for any damage you may sustain as a result of any virus in this e-mail. 
You should carry out your own virus checks before opening the e-mail or 
attachment. Infosys reserves the right to monitor and review the content of all 
messages sent to or from this e-mail address. Messages sent to or from this 
e-mail address may be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***

Other related posts: