Register Oracle resources in userApplication that is created at “2.2.4 userApplication with No Oracle Resources”.
In standby operation, userApplication is configured as follows.
Note that resource (Ora_App1) is being created and added.
Note
Check if Oracle database is properly running by starting and stopping manually before starting Oracle Resource Creation and Setting.
Before starting this procedure, Oracle instances, Oracle listeners and RMS on all the cluster nodes should stop.
Do not create multiple resources for the same Oracle instance or Listener.
userApplication is edited using the userApplication Configuration Wizard.
The flow of userApplication creation is as follows:
1 | userApplication deletion | |
2 | Oracle resources creation | |
3 | Other resources creation | |
4 | userApplication creation | |
5 | Other userApplication creation | |
6 | Configuration-Generate and Configuration-Activate |
Delete only the userApplication that was created in "2.2.4 userApplication with No Oracle Resources" using the userApplication Configuration Wizard. Do not delete resources that are included in the userApplication.
Information
For further details, refer to “PRIMECLUSTER Installation and Administration Guide”.
This section describes how to create an Oracle resource.
Select “Create Resource” in the “userApplication Configuration” menu.
Select “Oracle” in the “Resource Type” menu.
Add the Oracle instance and Oracle listener in the “Set up Resource” menu.
The settings are as follows:
Attributes | Description |
---|---|
ApplicationName | Change the application name. It can contain the following characters.
|
AdditionalInstance | Add an Oracle instance resource. |
AdditionalListener | Add an Oracle listener resource. |
AdditionalRAC11gR2/12cR1Instance | Not used. |
AdditionalRAC11gR2/12cR1Listener | Not used. |
AdditionalOracle11gR2/12cR1Clusterware | Not used. |
StartPriority | Set up the startup order of the Oracle instance and Oracle listener. The default is “Simultaneous startup”. |
Information
A resource name on RMS is based on the application name (SubApplicationName) entered in “ApplicationName” on this step.
Oracle instance resource/ Oracle ASM instance resource
ORACLE_<SubApplicationName>_<OracleSID>
Oracle listener resource
LISTENER_<SubApplicationName>_<ListenerName>
These resource names have the following convention and rules.
Characters per resource name must be up to 39 characters.
“ORACLE_” and “LISTENER_” are fixed words.
Note
If you create and register an Oracle ASM instance resource, refer to "2.4.2 Oracle ASM (Automatic Storage Management)".
Example
If a shared server configuration or dynamic service information is used, specify “Listener” for the StartPriority attribute.
Set up the Oracle instance as follows:
Enter ORACLE_SID.
Oracle instance settings
To change the settings, select setting item and click “Next” button.
To change the advanced settings, check “Advanced setup”.
The settings for Oracle instance resource are as follows:
Attributes | Description |
---|---|
OracleSID | ORACLE_SID It can contain the following characters. However, the character string must not start with the hyphen.
|
OracleUser |
It can contain the following characters. However, the character string must not start with the hyphen.
|
StartTimeout | Timeout (sec) duration of Oracle instance startup. |
StopTimeout | Timeout (sec) duration of Oracle instance stop. |
AbortTimeout | Timeout (sec) duration of forced termination in the event of an Oracle instance stop error. Default: 60 (60 - 86400) |
StopModeStop | Oracle instance stop mode in normal time. |
StopModeFail | Oracle instance stop mode in the event of a failure. |
Interval | Monitoring interval (sec) of Oracle instance. Default: 30 (5 - 86400) |
WatchTimeout | No response time (sec) during monitoring Oracle instance. Default: 300 (30 - 3600) |
REDOApply | Method of applying redo log to standby database in Oracle Data Guard environment. This setting is enabled with the Oracle instance resource of the standby database. This setting is disregarded in the following instance resource.
For details, see "G.2 Oracle Environment Setting". |
UsePDB | Set yes when you use the PDB of the Oracle database using the multitenant architecture. Set no when you do not use the PDB. Default: no (yes, no) This setting is not used for the Oracle ASM instance resource. |
The advanced settings are as follows. These settings are optional:
Attributes | Description | |
---|---|---|
PreOnlineScript | Executed before online processing. It can contain the following characters.
| |
PostOnlineScript | Executed after online processing. It can contain the following characters.
| |
PreOfflineScript | Executed before offline processing. It can contain the following characters.
| |
PostOfflineScript | Executed after offline processing. It can contain the following characters.
| |
FaultScript | Executed when a fault occurs. It can contain the following characters.
| |
Flags | NullDetector | If you do not want to monitor the resource, select this flag "NullDetector(D)". Default: "NullDetector(D)" is not selected. |
AutoRecover | If you want to restart the resource before failover when a resource failure occurs, select this flag "AutoRecover(A)". Default: "AutoRecover(A)" is not selected. | |
MonitorOnly | If you do not want to generate a failover when a resource failure occurs, select this flag "MonitorOnly(N)". Default: "MonitorOnly(N)" is not selected. |
Information
For details about Scripts, see “2.4.1 Oracle resource Online/Offline Script”.
For details about Flags, see “9 Appendix - Attributes” of the “PRIMECLUSTER RMS Configuration and Administration Guide”.
The following value is used for the timeout values (sec) of PreOnlineScript, PostOnlineScript, PreOfflineScript, PostOfflineScript and FaultScript.
StartTimeout + StopTimeout + AbortTimeout + 10
Note
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.
Calculate StartTimeout based on the time measured in "2.2.6 Oracle database Creation and Setting".
<UsePDB is no> Time of "startup"+60 seconds <UsePDB is yes> Time of "startup"+Time of "alter pluggable database all open;"+60 seconds
Set the value when this time is larger than default value 600. Otherwise, set default value 600.
Calculate StopTimeout based on the time measured in "2.2.6 Oracle database Creation and Setting".
Time of "shutdown StopModeStop"+60 seconds *When StopModeStop is not immediate, measure the time of StopModeStop.
Set the value when this time is larger than default value 180. Otherwise, set default value 180.
Calculate AbortTimeout based on the time measured in "2.2.6 Oracle database Creation and Setting".
<StopModeFail is immediate> Time of "shutdown immediate"+60 seconds <StopModeFail is abort> 60 seconds
Set the value when this time is larger than default value 60. Otherwise, set default value 60.
Flags=<Abbreviation> indicates that the flag attribute is enabled.
Set up the Oracle listener as follows:
Enter the listener name.
Oracle listener settings
To change the settings, select setting item and click “Next” button.
To change the advanced settings, check “Advanced setup”.
The settings for Oracle listener resource are as follows:
Attributes | Description |
---|---|
ListenerName | Listener name It can contain the following characters. However, the character string must not start with the hyphen.
|
OracleUser |
It can contain the following characters. However, the character string must not start with the hyphen.
|
StartTimeout | Timeout (sec) duration of Oracle listener startup. |
StopTimeout | Timeout (sec) duration of Oracle listener stop. |
Interval | Monitoring interval (sec) of Oracle listener. |
WatchTimeout | No response time (sec) during monitoring Oracle listener. |
The advanced settings are as follows. These settings are optional:
Attributes | Description | |
---|---|---|
TNSName | Network service for listener monitoring It can contain the following characters. However, the character string must not start with the hyphen.
| |
PreOnlineScript | Executed before online processing. It can contain the following characters.
| |
PostOnlineScript | Executed after online processing. It can contain the following characters.
| |
PreOfflineScript | Executed before offline processing. It can contain the following characters.
| |
PostOfflineScript | Executed after offline processing. It can contain the following characters.
| |
FaultScript | Executed when a fault occurs. It can contain the following characters.
| |
Flags | NullDetector | If you do not want to monitor the resource, select this flag "NullDetector(D)". Default: "NullDetector(D)" is not selected. |
AutoRecover | If you want to restart the resource before failover when a resource failure occurs, select this flag "AutoRecover(A)". Default: "AutoRecover(A)" is selected. | |
MonitorOnly | If you do not want to generate a failover when a resource failure occurs, select this flag "MonitorOnly(N)". Default: "MonitorOnly(N)" is not selected. |
Information
For details about Scripts, see “2.4.1 Oracle resource Online/Offline Script”.
For details about Flags, see “9 Appendix - Attributes” of the “PRIMECLUSTER RMS Configuration and Administration Guide”.
The following value is used for the timeout values (sec) of PreOnlineScript, PostOnlineScript, PreOfflineScript, PostOfflineScript and FaultScript.
StartTimeout + StopTimeout + 10
Note
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.
Save the settings by selecting “SAVE+EXIT”.
Check that the Oracle resource is set then save the settings by selecting SAVE+EXIT.
Information
After set up userApplication, the settings in this section can be confirmed with clorainfo -c command. See “4.6 clorainfo - Display Resource Configuration and Monitoring Status” for details.
If you have any other required resources, create them.
Information
Other resources (ex. Procedure resource, resource concerning backup software) should be registered here.
For details of them, refer to the each manual. (For Procedure resource, refer to “PRIMECLUSTER Installation and Administration Guide”.)
Select “Create userApplication” in the “userApplication Configuration” menu to create userApplication including the resources created in “2.2.7.2 Oracle Resource Creation” and “2.2.7.3 Other Resource Creation”.
For further details of the attributes of userApplication, refer to “2.2.3 userApplication Creation”.
Note
HELP description is common to GUI and CUI, so a part of them includes a description about CUI.
If you have any other required userApplications at "2.2.7.4 userApplication Creation", create them using the userApplication Configuration Wizard.
Check the set contents and then generate and activate the configuration. The image screens after activation are as follows: