Oracle instance startup or stop failed.
[Case 1]
Oracle instance startup or stop fails when the PRIMECLUSTER RMS resource settings are invalid.
Check the resource setup information by executing "clorainfo -c" command. Refer to "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. Refer to "Chapter 2 Environment Setup".
[Case 2]
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]
Oracle instance startup or stop fails when Oracle database settings are invalid.
Check the Oracle database alertlog, 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. Refer to "3.2.4.1 Oracle database must be stopped".
