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

2.3.5 userApplication with Oracle RAC Instances and Listeners

This section describes how to register Oracle instance resources on each node using the RMS Configuration Wizard. Before resource registration, it is necessary to associate the Oracle instances with Oracle 10g RAC. Out of the Oracle 10g resources that are displayed with the "crs_stat" command, the ora.*.inst resources must be registered.

Refer to the following example:

$ crs_stat -t

Name Type Target State Host
------------------------------------------------------------

ora....1.lsnr application ONLINE ONLINE node1

ora.node1.gsd application ONLINE ONLINE node1

ora.node1.ons application ONLINE ONLINE node1

ora.node1.vip application ONLINE ONLINE node1

ora....2.lsnr application ONLINE ONLINE node2

ora.node2.gsd application ONLINE ONLINE node2

ora.node2.ons application ONLINE ONLINE node2

ora.node2.vip application ONLINE ONLINE node2

ora....rac.db application ONLINE ONLINE node1

ora....1.inst application ONLINE ONLINE node1

ora....2.inst application ONLINE ONLINE node2

$

In the above configuration, "ora....1.inst" included in node1, and "ora....2.inst" included in node2 are registered as a resource respectively.

Before configuring userApplication, make sure that Oracle Clusterware has been activated on the node where RMS Configuration Wizard is running, so the "crs_stat" command can be executed correctly with Oracle DBA user.

If Oracle Clusterware has not been activated, execute the following command as a root user.

# /etc/init.d/init.crs start

When Oracle Clusterware startup is completed, be sure to confirm that the "crs_stat" command can be executed correctly.

# su - <Oracle User>

$ crs_stat

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

   

2. Select WIZSTANDBY in the "Application type selection menu" page.

   

3. Specify a userApplication name of ApplicationName in the "Settings of turnkey wizard WIZSTANDBY" page.

   

4. Select Machies+Basics(-)

   

5. Set up nodes and following menu items.
   Set an operating node to Machines [0], and standby nodes to Machines [n]. Select AdditionalMachines when adding a new node. For other settings, refer to HELP or PRIMECLUSTER Installation and Administration Guide.

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

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

     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

   • The Oracle Clusterware resource is not registered in an RMS resource (Configuration C)

     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

   
   Be sure to set AutoStartUp=yes when the Oracle instance is activated from Oracle Clusterware right after OS startup, data inconsistency might occur (default: no). If the controlling userApplication is not used, select AutoStartUp=yes.

   Save the above settings by selecting SAVE+EXIT.

   

   
   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, the users can detect which userApplication failed even after server reboot. Even though AutoStartUp setup is set, userApplication will not be started, however, automatic startup will prevent recurrence of the failure.

6. Select Oracle in the "Settings of turnkey wizard "WIZSTANDBY"" page.

   

7. Add Oracle instances and listeners in the Oracle setup screen.

   

   
   Based on the Oracle RAC 10g resource name that is set in the AdditionalOracle10gNodeapps, the Wizard for Oracle resource name is created on the RMS instance. For details, refer to"2.3.2 Oracle Software Installation and Configuration".

8. Select FREECHOICE and enter Oracle user name.

   

9. From the result of the "crs_stat" command execution, a list of the Oracle instance resources will be displayed. Select the Oracle instance on the node that is set in the Machines+Basics.
   The selected CRS resources here should exist on the node that has set on the step "4" "Machines+Basics" of "2.3.5".

   

   

   Do not register the resources of the other nodes at the same time.
   It is possible to prevent it by specifying a node name as ScopeFilter. The following sample indicates that CRS resources on node1 are listed.

   

   

   

   

   The resource name begins with "Ora_<ApplicationName>_" instead of "ora" of the CRS resource name of Oracle RAC(displayed with "crs_stat" command).
   The RMS resource name is generated based on the CRS resource name as follows:

   • Oracle RAC instance resource
     Ora_<ApplicationName>_<inst_name>.i
   • Listener resource
     Ora_<ApplicationName>_<lsnr_name>.l
     The default value of <lsnr_name> is "LISTENER_<node name>".
   • 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"2.3.4".
   • <inst_name> indicated by bold type is part of CRS resource name.
     ora.rac.rac1.inst
   • <lsnr_name> indicated by bold type is part of CRS resource name.
     ora.node1.LISTENER_NODE1.lsnr
     

   Confirm that CRS resources selected at previous screen appear after "Currently set". After that, select SAVE+RETURN.

   

   

   Do not register the resources of the other nodes at the same time.

10. Selecting Oracle10gNAPResource[0] allows for more detailed setup.

    

11. Select SELECTED.

    

12. You can set up details. Check the settings then select SAVE+RETURN.

    

    Attributes		Description
    OracleUser		Oracle DBA user name
    ScriptTimeout		Timeout of Oracle RAC Instance and Listener resource startup and stop Default : 900 s (300s - 86400s)
    WFTime		Waiting time for resource failure recovery through Oracle Clusterware - PersistentWarning : Notifies Warning until resource recovery - ImmediateFault : Notifies Faulted without waiting resource recovery - 60s - 86400s Default time for instance resources: 900s Default time for listener resources: PersistentWarning
    PreOnlineScript		Executed before online processing. No default
    PostOnlineScript		Executed after online processing. No default
    PreOfflineScript		Executed before offline processing. No default
    PostOfflineScript		Executed after offline processing. No default
    FaultScript		Executed when a fault occurs. No default
    Flags	NullDetector (D)	Selects whether or not a resource should be monitored. If it is enabled, the resource will be monitored. Resource monitoring is disabled 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".

    

    • Startup of Oracle Clusterware userApplication through PreOnlineScript
      If Oracle Clusterware and Oracle RAC instance are registered in different userApplication (Configuration A), set up the following script in PreOnlineScript of the Oracle RAC instance resource;

      /opt/FJSVclora/sbin/clorastartwait <userApplication with Oracle Clusterware>

      
      

    
    Specify the following userApplication "Configuration A":
    For app3 : app1
    For app4: app2

    • WFTime
      In Oracle RAC 10g, Oracle Clusterware will recover a failure of an RAC instance or listener instance. PRIMECLUSTER Wizard for Oracle, the wait time for the failure recovery can be set for WFTime
      
      If WFTime=PersistentWarning is set, completion of the failure recovery will be waited forever. In the meantime, an RMS resource will enter Warning, so userApplication will not be degenerated. As soon as recovery is detected, the RMS resource will get back to Online.
      
      If WFTime=ImmediateFault is set, completion of the failure recovery will not be waited but an RMS resource will be considered as fault. As soon as the RMS resource fails, userApplication will be degenerated.
      
      WFTime=<second> is set, completion of the failure recovery will be waited for a certain period of time. After the predetermined amount of wait time passes, an RMS resource will be considered as fault then userApplication will be degenerated. During the wait time, the RMS resource indicates Warning. If recovery is detected within the wait time, the RMS resource will get back to Online.
    • Flags
      Flags=< Abbreviation > indicates that the flag attribute is enabled.

13. Select "SAVE+EXIT"

    

14. Select "SAVE+EXIT"

    

15. Repeat the procedure from step 1 to 14 for each node.