< Previous  | TOC | Index | Next  >

Configuring the new Oracle instance

 To configure the new Oracle instance

1. On an existing system, add a new instance. Refer to the Oracle9i Installation Guide. Highlights of the steps to add a new instance include:
   • Log in as the user oracle and connect to the instance.
   • Create 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 used by the 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 can be the number of the new instance.
   • Prepare the init{SID}.ora file for the new instance on the new node.
   • If the Oracle is installed locally on the new system, prepare the directories bdump, cdump, udump, and pfile.
2. If you use in-depth monitoring for the database, create the table for the database instance. Create the table on the new system. 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. ODM is automatically mounted on the new system during installation, but not linked.

     # umount /dev/odm

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

     # mount /dev/odm

4. Create a mount point directory for the database file system. For example:

   # mkdir /oradata

5. Set the permissions for the mount point:

   # chown oracle:dba /oradata

6. Mount the file system with the database on the new system:

   # mount -t vxfs -o cluster /dev/vx/dsk/oradatadg/oradatavol \

   /oradata

7. Log in as user oracle 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 system, place the instance under VCS control.
   • Add the new system to the SystemList. For example, where the existing nodes, galaxy and nebula are nodes 0 and 1, saturn, the new node, would be node 2:

     # haconf -makerw

     # hagrp -modify oradb1_grp SystemList -add saturn 2

   • Add the new system 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 \

     Pfile=/oracle/orahome/dbs/initrac3.ora -sys saturn

   • If you have 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. To verify the configuration, enter the following command on the new system:

   # hastop -local

   All resources should come offline on the new system.

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

    # hastart