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.

Pre-requisites:

1. Configure Shared Storage setup ASM, NFS (NAS) or clustered storage.

2. A clustered Grid Infrastructure install with at least one Scan listener address. See

Oracle Grid Infrastructure Installation Guide 11g Release 2 (11.2) Linux

3.  rconfig imposes a restriction on the choice of listener. The listener must be the default listener, and it must run from the Grid Infrastructure home.

srvctl add listener -p 1522

After conversion, you can reconfigure the listener as required.

4.  Install Clustered Oracle Database Software as per documentation, this can be done by choosing the right configuration option. Refer to :

http://download.oracle.com/docs/cd/E11882_01/install.112/e10813/racinstl.htm#BABJGBHB

I’ve installed the new 11gR2 clustered ORACLE_HOME at

/u01/app/oracle/product/11.2.0/db_2

on both the nodes orarac01 and orarac02



Converting Single Instance Database using rconfig

1. As an “oracle” OS user navigate to

$ORACLE_HOME/assistants/rconfig/sampleXMLs

2. Open the sample file ConvertToRAC_AdminManaged.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.

3.  Ensure you edit the xml with convert verify="ONLY"
The following are the sample entries:


<!--Specify current OracleHome of non-rac database for SourceDBHome -->
 /u01/app/oracle/product/11.2.0/db_1
<!--Specify OracleHome where the rac database should be configured. It can be same as SourceDBHome -->
 /u01/app/oracle/product/11.2.0/db_2
<!--Specify SID of non-rac database and credential. User with sysdba role is required to perform conversion -->

...

<!--Specify the list of nodes that should have rac instances running for the Admin Managed Cluster Database. LocalNode should  be the first node in this nodelist. -->

...

<!--Specify Database Area Location to be configured for rac database.If this field is left empty, current storage will be use d for rac database. For CFS, this field will have directory path. -->
 +DATA

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.

So create spfile in the shared disk location


SQL>create spfile='+DATA/TEST/spfiletest.ora' from pfile;

You can check if the file is created through “asmcmd”

5. Take a backup of existing $SOURCE_ORACLE_HOME/dbs/initTEST.ora, and create a new $SOURCE_ORACLE_HOME/dbs/initTEST.ora with the following parameter:


spfile='+DATA/TEST/spfiletest.ora'

6. Restart the Database

7. Now lets test if “rconfig” is ready for conversion, navigate to $ORACLE_HOME/bin and issue the following command


$./rconfig $ORACLE_HOME/assistants/rconfig/sampleXMLs/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:


...

 Operation Succeeded

There is no return value for this step

..

8. Now are we are ready for conversion, edit the xml file “ConvertToRAC_AdminManaged.xml” and change:

from:


..
 <n:Convert verify="ONLY">
..

to


..
 <n:Convert verify="YES">
..

9. Perform the conversion


$./rconfig $ORACLE_HOME/assistants/rconfig/sampleXMLs/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

10. Once the conversion is complete you’d get a similar message in step 7.

11. Perform sanity checks and tweak the listener to suit your needs.

That sums up the procedure to convert Single Instance Oracle Database to RAC database. Please do share your thoughts and comments.

Reference:

http://download.oracle.com/docs/cd/E11882_01/install.112/e17214/cvrt2rac.htm#BABGGEGJ

Advertisements

This week  I was working on a project to implement Single Sign On with EBS R12,  as a first pre-requisite I had to install and configure WebLogic Server.

Here are the steps to install and perform a basic configuration for WebLogic Server.

Software

1. Download Weblogic Server from the following URL:

http://www.oracle.com/technology/software/products/middleware/htdocs/fmw_11_download.html

2. Review documentation to meet the basic hardware and software requirements:

http://download.oracle.com/docs/cd/E15523_01/doc.1111/e14142/toc.htm

Installation

1. I’ve created an operating user “oracle” to own the WebLogic Server, so as a “root” Super User do the following:

#groupadd dba
#useradd -g dba oracle
#mkdir -p /u01/oracle/middleware
#chown -Rh oracle:dba /u01/oracle/middleware
#xhost +

2. Now login as “oracle” and invoke the installer (I’ve downloaded the installer at /u01/dumps) as seen below. Click “Next”

3. Enter the location for Middle Ware Home and click “Next”

4.  Register for Security Updates if you wish to and click “Next”

5. Choose Install Type, I’ve chosen “Custom” and click “Next”

6. Choose “Products and Components”  you wish to use and click “Next”

7. If you have previous JDK/JRockit SDK, you can choose to browse the path, although Oracle recommends that you download the latest JRockit SDK to use with WebLogic. You can download the latest JRockit from:
http://www.oracle.com/technology/products/jrockit/index.html

8.  Choose “Product Installation Directories” and click “Next”

9. Review the Installation Summary and click “Next”

10. Once the installation completes, the “Run QuickStart” is checked. We’ll launch the QuickStart by clicking “Done”

11. Once clicked “Done”, You will be presented with the following which lets you choose 3 Options, We’ll go ahead with the 1st  to proceed with the configuration wizard.

Configuration

12. Now in the configuration wizard, we’ll choose “Create New WebLogic Domain” and click “Next”

13. Choose the defaults, I’ve also chosen “WebLogic Advanced Web Services Extension” from the following screen, click “Next” to proceed

14.  Now enter the Domain Name and Enter the Domain Location, click “Next” to proceed:

15.  Configure the WebLogic Administrator and Password, click “Next” to proceed.

16. As this is a basic install and for development purposes, I will choose the “Domain Startup Mode” as “Development. Careful consideration should be taken for production deployment. Click “Next” to proceed

17.  Select the Optional Configuration , I’ve selected the following options(we can configure JMS at a later stage):

18.  Configure the Admin Server:

19. Configure the Managed servers and click “Next”

20.  Next screen asks you if you wish to configure cluster, I did not configure any cluster. Click “Next” to proceed.

21. Next Screen is Configure Machines, I’ve not configured any. Click ” Next” to proceed

22. Configure Target Services to Clusters or Servers, review and click “Next” to proceed

23.  Review the Configuration Summary and click “Create”

24.  Click “Done” to finish and close the quickstart screen.

Now that we have installed and configured the WebLogic server, lets start the WebLogic server for the domain we configured. The startup scripts are placed in the user_projects directory for the domain we configured.

25.  Start the WebLogic Server

[oracle@oralin03 zakkiahmed.com]$ cd
[oracle@oralin03 ~]$ cd /u01/oracle/middleware/user_projects/domains/zakkiahmed.com
[oracle@oralin03 zakkiahmed.com]$ ls
autodeploy            init-info                        startWebLogic.sh
bin                   lib                              WseeFileStore
config                security                         WseeFileStoreAdminServer
console-ext           servers
fileRealm.properties  startManagedWebLogic_readme.txt
[oracle@oralin03 zakkiahmed.com]$./startWebLogic.sh

Now that the WebLogic Server is started lets login to the console

26. In to order login to the console open the web browser , the URL will be of the following format:

http://<hostname&gt;.<domain name>:7001/console

In my case it will be

http://oralin03.zakkiahmed.com:7001/console

You will be presented with the following screen:

The user name is “weblogic” and the password is what you configured during the configuration.

27. You will be presented with a neat front page, navigate to check the state of services on the left panel, follow the screenshot:

Thats it folks, the installation and basic configuration of WebLogic Server is complete. Feel free to comment and share your thoughts.

Thanks for reading.