Author A.Kishore Convert 11gR2 non-rac database to RAC database using rconfig

Transcription

1 Convert 11gR2 non-rac database to RAC database using rconfig I ve installed the new 11gR2 clustered ORACLE_HOME at /d01/oracle/app/oracle/product/11.2.0/dbhome_1 on both the nodes linux1 and linux2 New Oracle 11gR2 RAC Home - /d01/oracle/app/oracle/product/11.2.0/dbhome_1 SourceDBHome - /d01/oracle/racdb/db/tech_st/ 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 2. 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. 3. 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: I have started from NEW_ORACLE_HOME

2 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;

3 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

4 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 to $ORACLE_HOME/ assistants/rconfig/samplexmls and issue the following command

5 cd /d01/oracle/app/oracle/product/11.2.0/dbhome_1/assistants/rconfig/samplexmls rconfig ConvertToRAC_AdminManaged.xml The above command validates( as we ve set convert= ONLY ) if rconfig is ready for conversion. If the output throws any error, diagnose and troubleshoot to fix the issue. Refer to the following output for successful validation: 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:

6 9. Perform the conversion rconfig ConvertToRAC_AdminManaged.xml The conversion will take some time to complete. The progress can be monitored from the logs located at $ORACLE_BASE/cfgtoollogs/rconfig

7

8 Post-RAC Migration Steps Author A.Kishore Back out archivelog mode changes implemented by Rconfig (conditional). Rconfig will put the database into archive log mode. If you do not want the database to be in archive log mode, you can disable it using the following steps: Shut down the instances all on database nodes. Set cluster_database=false in the $ORACLE_HOME/dbs/init<SID>.ora file from any one node. Start up the instance using "Startup mount" option. Disable the archive logging using Alter database noarchivelog; Shut down the database. Set cluster_database=true in the $ORACLE_HOME/dbs/ini<SID>.ora file. Start up all the instances. Check the archive log setting using the command "archive log list". Remove the Listener configuration generated by Rconfig using NetCA (Conditional) If the existing single instance Net Listener was not reused during the Rconfig conversion, or is named something other than LISTENER_<hostname>, remove the Listener configuration generated by Rconfig using NetCA, then verify that the listener was removed from CRS by issuing the crs_stat command from a session set to the CRS_ORACLE_HOME location. Shut down the Listeners Using the command "srvctl stop listener -n <nodename>", shut down the listeners with the name LISTENER_<nodename>. These were created in Step 3.3 using srvctl login as the owner of the CRS_ORACLE_HOME. 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 one s needs. My recent work involved the conversion of non-rac single instance database to RAC database using rconfig, although I ve tested all the 3 methods but concluded on rconfig.

9 Listener Configuration in 11gR2 Listener configuration can often be confusing when converting an Oracle E-Business Suite database to use Oracle RAC. There are two types of listener in 11gR2 Clusterware: the Scan listener and general database listeners. The Scan listener provides a single named access point for clients, and replaces the use of Virtual IP addresses (VIP) in client connection requests (tnsnames.ora aliases). However, connection requests can still be routed via the VIP name, as both access methods are fully supported. Note: At present, AutoConfig does not support Scan listeners. This will be addressed in a future version of AutoConfig. To start or stop a listener from srvctl, three configuration components are required: An Oracle Home from which to run lsncrtl The listener.ora file under the TNS_ADMIN network directory The listener name (defined in listener.ora) to start and stop 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 Listener Configuration in 11gR2 Clusterware In 11gR2, listeners are configured at the cluster level, and all nodes inherit the port and environment settings. This means that the TNS_ADMIN directory path will be the same on all nodes. So to create a new listener, listener_ebs, on port 1522, running from the database ORACLE_HOME and with a user defined TNS_ADMIN directory, you would execute commands based on the following: srvctl add listener -l listener_ebs -o <11gR2 ORACLE_HOME> -p 1522 srvctl setenv listener -l listener_ebs -T TNS_ADMIN= $TNS_ADMIN When the listener starts, it will run from the database ORACLE_HOME. srvctl manages the listener.ora file across all nodes Listener requirements for converting to Oracle RAC Tools such as rconfig impose additional restrictions on the choice of listener. The listener must be the default listener, and it must run from the Grid Infrastructure home. So the example in above would need to be changed to:

10 srvctl add listener -p 1531 After conversion, you can reconfigure the listener as required. -- I did not create any of the above 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 , 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 )