Professional Documents
Culture Documents
info
New Oracle 11gR2 RAC Home - /d01/oracle/app/oracle/product/11.2.0/dbhome_1 SourceDBHome - /d01/oracle/RACDB/db/tech_st/11.2.0 ORACLE_SID RACDB
1. As the oracle user, navigate to the directory $ORACLE_HOME/assistants/rconfig/sampleXMLs, and open the sample file ConvertToRAC.xml using a text editor such as vi. This XML sample file contains comment lines that provide instructions on how to edit the file to suit your site's specific needs. Connect to new home . ./oracle.env [oracle@linux1 ~]$ cat oracle.env export ORACLE_HOME=/d01/oracle/app/oracle/product/11.2.0/dbhome_1 export LD_LIBRARY_PATH=$ORACLE_HOME/lib,$ORACLE_HOME/ctx/lib export ORACLE_SID=RACDB export PATH=$PATH:$ORACLE_HOME/bin export TNS_ADMIN=/d01/oracle/app/oracle/product/11.2.0/dbhome_1/network/admin/RACDB 1_linux1 cd /d01/oracle/app/oracle/product/11.2.0/dbhome_1/assistants/rconfig/sampleXMLs cp ConvertToRAC_AdminManaged.xml ConvertToRAC_AdminManaged.xml_org Copy the sample ConvertToRAC_AdminManaged.xml, and modify the parameters as required for your system. Make a note of the name of your copy of the XML file. To test the settings specified, it is advisable to execute rconfig using convert verify="ONLY" before carrying out the actual conversion. This will perform a test run to validate parameters and flag any incorrect settings or issues that need to be resolved before the final conversion takes place. Note: Specify 'SourceDBHome' variable in ConvertToRAC_AdminManaged.xml as Non- RAC oracle home (e.g. $OLD_ORACLE_HOME path). If you wish to specify as NEW_ORACLE_HOME then start the database from new oracle home using:
2.
3.
4. Move the spfile to the shared location, in this case the Single Instance Database was hosted on file system, in this process we will move the datafiles from file system storage to ASM. -- From New Home -- copy the initRACDB.ora from Source DB Home
Create the spfile from pfile using the command: sqlplus /as sysdba So create spfile in the shared disk location create spfile='+DATA/spfile/spfileracdb.ora' from pfile;
You can check if the file is created through asmcmd cat grid.env export ORACLE_HOME=/d01/oracle/app/11.2.0/grid export PATH=$PATH:$ORACLE_HOME/bin . ./grid.env
. ./oracle.env
5.Take a backup of existing $ORACLE_HOME/dbs/init<ORACLE_SID>.ora and create a new $ORACLE_HOME/dbs/init<ORACLE_SID>.ora with following parameter: spfile='<Path of spfile on shared disk>/spfile<ORACLE_SID>.ora' spfile= +DATA/spfile/spfileracdb.ora 6. Start up the instance from the NEW ORACLE_HOME
7.
Now lets test if rconfig is ready for conversion, navigate t o $ORACLE_HOME/ assistants/rconfig/sampleXMLs and issue the following command
Issues faced Rconfig a> Default Listener is not configured in Grid Infrastructure Home. Solution - on the grid infrastruture - run netca - create a default listener b> /d02/oracle/RACDB/db/tech_st/11.2.0/dbs/arch LOG ARCHIVE DEST Solution - mkdir /d02/oracle/RACDB/db/tech_st/11.2.0/dbs/arch
8.
Now are we are ready for conversion, edit the xml file ConvertToRAC_AdminManaged.xml and change:
9.
The conversion will take some time to complete. The progress can be monitored from the logs located at $ORACLE_BASE/cfgtoollogs/rconfig
This post talks about the Conversion of 11gR2 non-RAC database to RAC database using rconfig. Oracle provides 3 methods to convert non-RAC single instance database to RAC databases: 1. DBCA 2. rconfig 3. Enterprise Manager All the 3 have their own benefits and can be used to suit ones needs. My recent work involved the conversion of non-RAC single instance database to RAC database using rconfig, although Ive tested all the 3 methods but concluded on rconfig.
The Oracle Home can either be the Infrastructure home or a database home. The TNS_ADMIN directory can be any accessible directory. The listener name must be unique within the listener.ora file. See Oracle Real Application Clusters Administration and Deployment Guide 11g Release 2 (11.2) There are three issues to be considered: Listener configuration in 11gR2 Clusterware. Listener requirements for converting to Oracle RAC Listener requirements for AutoConfig
-- I did not create any of the above 3.1.1.3 Listener requirements for AutoConfig
The current version of AutoConfig creates listener names of the form listener_<NODE_NAME>,
i.e. different listener names on each node in the cluster. This issue is being tracked via bug 8312164, and a future version of AutoConfig the listener name will be a user-defined context variable.
Using Oracle 11g Release 2 Real Application Clusters with Oracle E-Business Suite Release 12 (Doc ID 823587.1)