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 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]
Oracle instance startup or stop fails when user script settings in /opt/FJSVclora/usr are incorrect (standby operation or scalable operation with Oracle9i RAC only).
Check if the user scripts behave correctly.
[Case 3]
Oracle instance startup or stop fails when Oracle settings are invalid.
Check the Oracle alert log, so you might be able to detect the cause of the failure.
Also, check if Oracle can be started or stopped properly. If you discontinue Oracle instance resource monitoring, you can operate Oracle manually. See “3.2.4.1 Oracle must be stopped”.
