PRIMECLUSTER Wizard for Oracle Configuration and Administration Guide 4.2 - Linux for Itanium -

2.3.4 userApplication with Oracle Clusterware

This section describes how to register the Oracle Clusterware in an RMS resource using the RMS Configuration Wizard.

If the Oracle Clusterware resource is not registered in an RMS resource (Configuration C), skip the procedure then go to "2.3.5 userApplication with Oracle RAC Instances and Listeners".

1. Select Application-Create in the Main configuration menu.

   

2. Select WIZSTANDBY in the Application type selection menu.

   

   

   Do not select ORACLE (all caps) in this screen. This is for backward compatibility.

3. Set up the turkey wizard in the "Settings of turnkey wizard "WIZSTANDBY".

   

4. Select Machines+Basics.

   

5. Set up the node and userApplication.
   

   
   The following setup values are recommended. The other attributes that are not described below are optional.

   • The Oracle Clusterware and Oracle RAC instance are registered in different userApplication (Configuration A)

     Attributes	Values
     AutoSwitchOver	No
     PersistentFault	1

   • The Oracle Clusterware and Oracle RAC instance are registered in the same userApplication (Configuration B)

     Attributes	Values
     AutoStartUp	Optional If you control userApplication startup and stop on all nodes by using the controlling userApplication, be sure to specify No.
     AutoSwitchOver	No
     PersistentFault	1

   
   
   PersistentFault setup
   PersistentFault remains the same resource status (Faulted) even after RMS is restarted in the event of a resource failure. Users are supposed to locate the fault and check completion of recovery processing then start userApplication manually. For example, if a failure occurs, users can detect which userApplication failed even after server reboot. Even though AutoStartUp setup is set, userApplication will not be started, and automatic startup will prevent recurrence of the failure.

6. Select Oracle in the Setting of turnkey wizard "WIZSTANDBY".

   

7. Add Oracle Clusterware in the Oracle setup screen.

   

   
   

   • Oracle Clusterware resource name in RMS is generated as follows:
     Ora_<ApplicationName>_Clusterware
   • This resource name has the following convention and rules:
   • The resource name must be up to 39 characters.
   • For information on how to set up <ApplicationName>, refer to the step "3" of "2.3.4".
8. Perform the detailed setup.

   

   Enter a DBA user for Oracle control.

   

   Attributes		Description
   OracleUser		DBA user for Oracle control
   ScriptTimeout		Timeout of Oracle instance resource startup and stop Default : 600s (300s - 86400s)
   PreOnlineScript		Executed before online processing
   PostOnlineScript		Executed after online processing
   PreOfflineScript		Executed before offline processing
   PostOfflineScript		Executed after offline processing
   FaultScript		Executed in the event of a fault
   Flags	KeepOnline (K)	Selects whether or not Online should remain without stopping resources when userApplication is stopped. If it is enabled, Online will remain. The Online state remains as default.

   

   • For details about *Scripts, refer to"2.4.1 Oracle Online/Offline Script".
   • For details about Flags, refer to "9 Appendix - Attributes" of the "PRIMECLUSTER RMS Configuration and Administration Guide".

   

   • Flags=<Abbreviation> indicates that the flag attribute is enabled.
   • If the "KeepOnline" flag is enabled, and userApplication is stopped, an Oracle Clusterware resource will look Offline on the Cluster admin view. Actually, it remains active.
   • Stop of userApplication including Oracle RAC instance resource through PreOfflineScript
     When Oracle Clusterware and Oracle RAC instance are registered in different userApplication (Configuration A) and the "KeepOnline" flag is disabled, it is necessary to set the following script for PreOfflineScript of Oracle Clusterware resource;

   /opt/FJSVclora/sbin/clorastopwait <userApplication>

   <userApplication> : userApplication including Oracle RAC instance resource>

   userApplication name specifiable for <userApplication> are as follows "Configuration A":

   • - app1 in process of creation in this section : specify app3
   • - app2 in process of creation in this section : specify app4

   If there are multiple userApplications that include Oracle RAC instance resource, specify all of them space-delimited for <userApplication>.

9. Check the above settings then select SAVE+RETURN.

   

10. Select SAVE+EXT to register the resource.

    

    
    If you register the Oracle Clusterware and Oracle RAC instance in the same userApplication (Configuraiton B), select AddtionalOracle10gNodeapps then register Oracle RAC instances and listeners. For details, refer to Step 7 to 13 of "2.3.5 userApplicaiton with Oracle RAC Instances and Listeners".

11. Check that the Oracle resource is set then save the above settings by selecting SAVE+EXIT.

    

12. Repeat from Step 1 to 11 for each node.