Cluster Server 7.4.2 Database Agent for Oracle Configuration Guide - Windows

To configure Oracle on failover nodes

1. Verify that the volumes or LUNs created for the Oracle database, control files, log files, bdump, cdump, udump files, flash recovery area and archive location are mounted or connected on the node where you run the installer.

2. Bring the temporary service group online on the node where you run the installer.

3. Verify that the Oracle log files and the background_dump_dest (bdump), core_dump_dest (cdump), and user_dump_dest (udump) files are on the same volume on the shared storage.
4. Type the following on the command prompt:

   C:\>set ORACLE_SID=
   				<SID NAME>
   			

   The variable SID represents the database instance.

5. Run the oradim utility with the parameters as specified.

   Type the following on the command prompt:

   C:\>
   				<ORACLE_HOME>
   				\bin\oradim -new -sid
   				SID
   				-pfile
   				"pfile_location_on_shared_disk"
   				-startmode auto 
   -timeout 100 -shuttype srvc,inst -shutmode i
   			

   The variable SID represents the database instance.

   This command performs the following tasks:

   • Sets the -startmode parameter to start the database instance automatically when Oracle service is started.

   • Sets the -timeout parameter to 100. The timeout parameter specifies the maximum wait time (in seconds) for the database shutdown to complete before the service for a particular SID stops.

   • Sets the -shuttype parameter to stop both the database instance and the service while shutting the database.

   • Sets the -shutmode parameter to shut the database instance as soon as the VCS database agent for Oracle requests.

6. Create a listener service using the Oracle Net Configuration Assistant. Refer to the Oracle documentation for instructions.
7. Stop the listener service and make a backup copy of the original files, tnsnames.ora and listener.ora, from the first node.
8. Copy the files, tnsnames.ora and listener.ora from the first node to the current node, at the same directory as that on the first node.

   The path for tnsnames.ora and listener.ora must be the same on all failover nodes.

9. From the Windows Services console, set the startup type of the Listener service to Manual and then restart the Listener and the Oracle service for the database instance on the node.

   In the Services snap-in, the names of Oracle services appear as OracleServiceSID, where SID represents the database instance.

10. Verify access to the database by connecting to it and running a select query.

    Repeat these tasks on all the remaining nodes that will participate in the Oracle service group.