Oracle RAC instances and listeners are managed as PRIMECLUSTER RMS resources. Also, the Oracle Clusterware can be registered in an RMS resource optionally.
Configuration A
The Oracle Clusterware and Oracle RAC instance are registered in different userApplication.
Use this configuration if Oracle Clusterware is registered in an RMS resource and you have plan to add Oracle RAC instances in the future or each node has multiple Oracle RAC instances.
userApplication | Description | Resources |
app1, app2 | Controls Oracle Clusterware. | Oracle resource (Clusterware) |
app3, app4 | Controls Oracle instances and listeners. | Oracle resource (instances, listeners) |
app5, app6 | Used as standby for Gls or takeover network. (Option) | Gls resource, etc |
app7 | Starts up or stops Oracle instance userApplication (app3 and app4) simultaneously on all nodes. (Option) | Controller resource |
If userApplication app3 and app4 are stopped due to an Oracle RAC instance resource failure, userApplication app1 and app2 of Oracle Clusterware will not be affected.
Information
The following setup values are recommended for userApplication which controls Oracle Clusterware (app1, app2). The other attributes that are not described below are optional.
Attributes | Values |
Operation method | Standby |
AutoSwitchOver | No |
PersistentFault | 1 |
The following setup values are recommended for userApplication which controls Oracle instances and listeners (app3, app4). The other attributes that are not described below are optional.
Attributes | Values |
Operation method | Standby |
AutoStartUp | If you control userApplication startup and stop on all nodes by using the controlling userApplication, be sure to specify No. |
AutoSwitchOver | No |
PersistentFault | 1 |
Note
If the “KeepOnline” flag of Oracle Clusterware resource is disabled, the userApplication which controls Oracle instances should be stopped first, and then the userApplication which controls Oracle Clusterware should be stopped.
(In the above image, app3 should be stopped before app1 stopping. app4 should be stopped before app2 stopping.)
For further details of the “KeepOnline” flag, refer to “2.3.4 userApplication with Oracle Clusterware”.
Configuration B
The Oracle Clusterware and Oracle RAC instance are registered in the same userApplication.
Use this configuration if Oracle Clusterware is registered in an RMS resource and only one Oracle RAC instance exists on a node and having no plan to add Oracle RAC instances in the future.
userApplication | Description | Resources |
app1, app2 | Controls Oracle Clusterware. | Oracle resource (Clusterware, instances, listeners) |
app3, app4 | Used as standby for Gls or takeover network. (Option) | Gls resource, etc |
app5 | Starts up or stops Oracle instance userApplication (app1 and app2) simultaneously on all nodes. (Option) | Controller resource |
If userApplication app1 and app2 are stopped due to an Oracle RAC instance resource failure, Oracle Clusterware will also be stopped (when the KeepOnline flag is disabled).
Information
The following setup values are recommended for userApplication which controls Oracle Clusterware, Oracle instance and listener (app1, app2). The other attributes that are not described below are optional.
Attributes | Values |
Operation method | Standby |
AutoStartUp | If you control userApplication startup and stop on all nodes by using the controlling userApplication, be sure to specify No. |
AutoSwitchOver | No |
PersistentFault | 1 |
Configuration C
The Oracle Clusterware is not registered.
Use this configuration if you want to make Oracle Clusterware automatically start up along with OS startup without registering it in an RMS resource.
userApplication | Description | Resources |
app1, app2 | Controls Oracle instances and listeners. | Oracle resources (instances, listeners) |
app3, app4 | Used as standby for Gls or takeover network. (Option) | Gls resource, etc |
app5 | Starts up or stops Oracle instance userApplication (app1 and app2) simultaneously on all nodes. (Option) | Controller resource |
Information
The following setup values are recommended for userApplication which controls Oracle instances and listeners (app1, app2). The other attributes that are not described below are optional.
Attributes | Values |
Operation method | Standby |
AutoStartUp | No. |
AutoSwitchOver | No |
PersistentFault | 1 |
Confirm Oracle Clusterware has already been started when you start userApplication (app1,app2). It fails in the start of the Oracle instance resources when Oracle Clusterware is starting or Oracle Clusterware has stopped.
The flow of userApplication creation is as follows:
1 | Register Oracle Clusterware resources | |
2 | Register Oracle instance and listener resources | 2.3.5 userApplication with Oracle RAC Instances and Listeners |
3 | Register the other required resources | |
4 | Create userApplication | 2.3.7 Configuration-Generate and Configuration-Activate |
userApplication is configured with the userApplication Configuration Wizard. This userApplication Configuration Wizard forms Wizard format as follows:
Menu -> Settings -> Next button
Information
For setting the userApplication Configuration Wizard, see “Chapter 6 Cluster application configuration” of the “PRIMECLUSTER Installation/Administration Guide”.
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.
Note
Do not create multiple resources for the same Oracle RAC instance, Listener or Oracle Clusterware.
