< Previous  | TOC | Index | Next  >

Configuring new Oracle instance on the new node

Review the procedure to configure a new Oracle instance on the new node.

 To configure new Oracle instance on the new node

1. On an existing node, add a new instance. Refer to the Oracle9i Installation Guide. Highlights of the steps to add a new instance include:
   • Logging in as the oracle user and connecting to the instance.
   • Creating a new "undotbs" tablespace for the new instance. For example, if the tablespace is for the third instance, name it "undotbs3." If the database uses raw volumes, create the volume first. Use the same size as the one for existing "undotbs" volumes.
   • Create two new "redo" log groups for the new instance. For example, if the tablespace is for the third instance, create the tablespaces "redo3_1" and "redo3_2." If the database uses raw volumes, create the volume for the redo logs first. Use the size used by the existing redo volumes.
   • Enable "thread 3" where 3 is the number of the new instance.
   • Prepare the init{SID}.ora file for the new instance on the new node.
   • If Oracle is installed locally on the new node, prepare the bdump, cdump, udump, and pfile directories.
2. If you use in-depth monitoring for the database, create the table for the database instance. Create the table on the new node.

   Refer to the Veritas High Availability Agent for Oracle Installation and Configuration Guide for instructions on creating the table.

3. Configure the ODM port on the new node.
   • Unmount the ODM directory to unconfigure port d:

     # /sbin/init.d/odm stop

     The installation automatically mounts ODM on the new node but does not link it.

   • Mount the ODM directory. Re-mounting the ODM directory configures port d and re-links the ODM libraries with SF Oracle RAC:

     # /sbin/init.d/odm start

4. Create a mount point for the shared file system:

   # mkdir /rac_ts

5. From the same node, mount the file system:

   # mount -F vxfs -o cluster /dev/vx/dsk/rac_dg/rac_vol1 /rac_ts

6. Set "oracle" as the owner of the file system, and set "755" as the permissions:

   # chown oracle:dba /rac_ts

   # chmod 755 /rac_ts

7. Log in as oracle user and attempt to manually start the new instance; the following example is for a third system:

   $ export ORACLE_SID=rac3

   $ sqlplus '/as sysdba'

   sqlplus> startup pfile=/oracle/orahome/dbs/initrac3.ora

8. After the new Oracle instance is brought up manually on the new node, place the instance under VCS control.
   • Add the new node to the SystemList. For example, if the existing nodes (galaxy and nebula) are nodes 0 and 1, the new node (saturn) is node 2:

     # haconf -makerw

     # hagrp -modify oradb1_grp SystemList -add saturn 2

   • Add the new node to the AutoStartList for oradb1_grp:

     # hagrp -modify oradb1_grp AutoStartList galaxy \

     nebula saturn

   • Modify the Sid (system ID) and Pfile (parameter file location) attributes of the Oracle resource. For example:

     # hares -modify VRTdb Sid rac3 -sys Saturn

     # hares -modify VRTdb Pfile /oracle/orahome/dbs\

     /initrac3.ora -sys Saturn

   • If you created a table for in-depth monitoring, modify the Table attribute of the Oracle resource. For example:

     # hares -modify VRTdb Table vcstable_saturn -sys saturn

   • Close and save the configuration:

     # haconf -dump -makero

9. From the new node, verify the configuration:

   # hastop -local

   VCS takes all resources offline on the new node.

10. Verify all resources come online after starting VCS on the new node:

    # hastart