Oracle instance startup or stop failed.
[Case 1] (Standby Operation, Scalable Operation with Oracle RAC, Single-Node Cluster Operation)
Oracle instance startup or stop fails when the PRIMECLUSTER RMS resource settings are invalid.
Check the resource setup information by executing the “clorainfo -c” command. See “4.6 clorainfo - Display Resource Configuration and Monitoring Status”.
Oracle user
OracleSID
Scripts (e.g. PreOnlineScript)
A correct path must be set.
The script must have execution permission.
The script must behave correctly.
If your setup information is incorrect, set proper values again. See “Chapter 2 Environment setup”.
[Case 2] (Standby Operation, Single-Node Cluster Operation)
Oracle instance startup or stop fails when user script settings in /opt/FJSVclora/usr are incorrect (standby operation only).
Check if the user scripts behave correctly.
[Case 3] (Standby Operation, Scalable Operation with Oracle RAC, Single-Node Cluster Operation)
Oracle instance startup or stop fails when Oracle database settings are invalid.
Check the Oracle database alert log, so you might be able to detect the cause of the failure.
Also, check if Oracle database can be started or stopped properly. If you discontinue Oracle instance resource monitoring, you can operate Oracle database manually. See “3.2.4.1 Oracle database must be stopped”.
[Case 4] (Scalable Operation with Oracle RAC)
When starting userApplication with Oracle RAC Instances resource in the state where Oracle Clusterware is not running, the resource state enters Wait until exceeds the time set as ScriptTimeout (refer to step 10 of “2.3.5 userApplication with Oracle RAC Instances and Listeners”). If it exceeds the time set as ScriptTimeout with the resource state maintain Wait, the resource state will enter Faulted.
Execute the following methods according to each pattern.
In the case of configuration that the Oracle Clusterware and Oracle RAC instance are registered in different userApplication. (It matches “Configuration A” in “2.3.3 userApplication and Resource Configuration”.)
At first, check whether Oracle Clusterware is running.
The following command execution, you can check whether Oracle Clusterware is running.
# su - <Grid user> $ crsctl status resource
When the following message is outputted, Oracle Clusterware may be not running.
CRS-0184: Cannot communicate with the CRS daemon.
When Oracle Clusterware is not running, there is a possibility that the setting that Oracle Clusterware starts earlier than Oracle RAC Instance is incorrect.
Check whether the script which starts Oracle Clusterware resource is set as the PreOnlineScript of Oracle RAC Instance (refer to “note” of step 10 of “2.3.5 userApplication with Oracle RAC Instances and Listeners”).
In the case of configuration that the Oracle Clusterware and Oracle RAC instance are registered in the same userApplication. (It matches “Configuration B” in “2.3.3 userApplication and Resource Configuration”.)
There is a possibility that starting of Oracle RAC Instance resource is failed.
Check whether you have no mistakes in setting of Oracle RAC Instance resource (“2.3.5 userApplication with Oracle RAC Instances and Listeners”).
In addition, check whether you have no mistakes in setting of PRIMECLUSTER RMS and Oracle database (refer to “Case 1” and “Case 3”).
In the case of configuration that the Oracle Clusterware is not registered. (It matches “Configuration C” in “2.3.3 userApplication and Resource Configuration”.)
Check whether Oracle Clusterware is running.
The following command execution, you can check whether Oracle Clusterware is running.
# su - <Grid user> $ crsctl status resource
When the following messages are outputted, Oracle Clusterware may be not running.
CRS-0184: Cannot communicate with the CRS daemon.
Clear Faulted state of the resource, after that, execute the following commands and start Oracle Clusterware.
# <Grid user's $ORACLE_HOME>/crsctl start crs
After that, start userApplication.
[Case 5] (Scalable Operation with Oracle RAC)
In the case of userApplication or the resources setting is changed when Oracle Clusterware has stopped, Oracle RAC instance startup or stop fails. Start Oracle Clusterware on all nodes beforehand when you do the setting change of userApplication or the resources. (Refer to “2.3.7 Configuration-Generate and Configuration-Activate”)
