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

2.2.9 userApplication with Oracle Resources

The following example shows how to configure the Oracle environment.

1. Select Application-Edit in the "Main configuration menu" screen.

   

2. Select userApplication created at "2.2.4 userApplication with No Oracle Resources". For scalable operation, select "app1" and "app2".

   

3. Select ORACLE in the "Settings of turnkey wizard "WIZSTANDBY"" screen.

   

4. Add Oracle instances and Oracle listeners in the Oracle setup page.

   

   Attributes	Description
   AdditionalInstance	Add an Oracle instance resource.
   AdditionalListener	Add an Oracle listener resource.
   AdditionalOracle10gService	Not used.
   AdditionalOracle10gNodeapps	Not used.
   AdditionalOracle10gClusterware	Not used.
   StartPriority	Set up the startup order of the Oracle instance and Oracle listener. The default is "Simultaneous startup".

   
   If a shared server configuration or dynamic service information is used, specify "Listener" for the StartPriority attribute.

5. Add Oracle instances.

   

   Enter ORACLE_SID.

   

   
   An Oracle instance resource name on RMS is based on the ORACLE_SID entered on this step.

   • Oracle instance resource/ASM instance resource
     ORACLE_Ora_<ApplicationName>_<OracleSID>

   This resource name has the following convention and rules.

   • Characters per resource name must be less than 40 characters.
   • "ORACLE_Ora_" is a fixed character string.

   

   Oracle instance setup

   Attributes		Description
   OracleSID		ORACLE_SID
   OracleUser		DBA user for Oracle control.
   StartTimeout		Timeout duration of Oracle startup. Default: 600s (300s - 86400s)
   StopTimeout		Timeout duration of Oracle stop. Default: 180s (60s - 86400s)
   AbortTimeout		Timeout duration of forced termination in the event of an Oracle stop error. Default: 60s (60s - 86400s)
   StopModeStop		Oracle stop mode in normal time. Default: Immediate mode (abort, immediate, transactional)
   StopModeFail		Oracle stop mode in the event of a failure. Default: Abort mode (abort, immediate)
   Interval		Monitoring interval of Oracle instance. Default: 30s (5s - 86400s)
   WatchTimeout		No response time during monitoring Oracle. Default: 300s (30s - 3600s)
   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 resource monitoring is enabled. If it is enabled, resource monitoring will not be performed. The resource monitoring is disabled as default.
   	AutoRecover (A)	Selects whether or not resource restart is attempted before failover in the event of a resource failure. If it is enabled, the resource will be restarted. The resource is not restarted as default.
   	MonitorOnly (M)	Selects whether or not a failover is generated in the event of a resource failure. If it is enabled, the resource will not be switched. The resource will be switched 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".

   

   • If NullDetector is enabled, the AutoRecover and MonitorOnly attribute will automatically be disabled.
   • MonitorOnly can be enabled in the following cases:
   • -One resource of "Instance" type and one resource of "Listener" type exist, and StartPriority is set to "Same".
     In this case, MonitorOnly only for the one of them can be enabled.
   • -More than one resources of "Instance" type exist.
     In this case, MonitorOnly for the one of them cannot be enabled, but all of the others can be enabled.
   • Flags=<Abbreviation > indicates that the flag attribute is enabled.

6. Add Oracle listeners.

   

   Enter the listener name.

   

   
   An Oracle listener resource name on RMS is based on the listener name entered on this step.

   • Oracle listener resource
     LISTENER_Ora_<ApplicationName>_<ListenerName>

   This resource name has the following convention and rules.

   • Characters per resource name must be less than 40 characters.
   • "LISTENER_Ora_" is a fixed character string.

   

   Oracle listener setup

   Attributes		Description
   ListenerName		Listener name.
   OracleUser		DBA user for Oracle control.
   TNSName		Network service for listener monitoring Execute the tnsping command to monitor the Oracle listener when TNSName is set (tnsnames.ora). If the TNSName is omitted, process monitoring of the Oracle listener will only be performed.
   StartTimeout		Timeout during Oracle startup. Default: 180s (120s - 86400s)
   StopTimeout		Timeout during Oracle stop. Default: 60s (60s - 86400s)
   Interval		Monitoring interval of Oracle instance. Default: 30s (5s - 86400s)
   WatchTimeout		No response time during monitoring Oracle. Default: 300s (30s - 3600s)
   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 resource monitoring is enabled. If it is enabled, resource monitoring will not be performed. The resource monitoring is disabled as default.
   	AutoRecover (A)	Selects whether or not resource restart is attempted before failover in the event of a resource failure. If it is enabled, the resource will be restarted. The resource is not restarted as default.
   	MonitorOnly (M)	Selects whether or not a failover is generated in the event of a resource failure. If it is enabled, the resource will not be switched. The resource will be switched 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".

   

   • If NullDetector is enabled, the AutoRecover and MonitorOnly attribute will automatically be disabled.
   • MonitorOnly can be enabled in the following cases:
   • One resource of "Instance" type and one resource of "Listener" type exist, and StartPriority is set to "Same".
     In this case, MonitorOnly only for the one of them can be enabled.
   • More than one resources of "Listener" type exist.
     In this case, MonitorOnly for the one of them cannot be enabled, but all of the others can be enabled.
   • Flags=< Abbreviation > indicates that the flag attribute is enabled.
7. Save the above settings by selecting SAVE+EXIT.