|
The Oracle service starts, but does not start the database.
|
Make sure the Oracle database parameter startmode is set to auto.
Make sure the path of the initialization file is set correctly.
Verify access to the shared virtual disk.
|
|
Clients cannot connect to the virtual IP address set for the service group.
|
Make sure that the listener service is running. Verify that the listener is configured with virtual IP address in the host location.
|
|
Resource returns offline during detail monitoring.
|
This could occur because the database is offline or has not been mounted or opened properly. Check the error in the log file for further details.
Verify the configuration definition of the agent. Make sure that the correct file name is specified in the configuration. Verify access to sqlplus from the command prompt.
|
|
The sqlplus script cannot be run because sqlplus returns a process error.
|
If the script timed out, increase the timeout value set in the attribute SQLTimeOut. Otherwise, try recreating the Oracle service using the oradim utility.
|
|
The Oracle wizard could not locate PFILE or SPFILE for a database.
|
Make sure the initialization file settings are configured correctly.
|
|
Listener service does not start after configuring the virtual IP address.
|
Make sure the virtual IP address is configured correctly for the listeners.
Another possible cause is that the listener.ora file is corrupted.
Complete the following steps in the order given:
Stop the listener services on the node. Rename the listener.ora file. Recreate the listeners using the Net Configuration Assistant. Bring up the virtual IP on the node. Configure the virtual IP address for the newly created listeners using the Net Manager. Restart the listener services. Run lsnrctl status command for each listener to verify the virtual IP address.
Refer to the Oracle documentation for instructions on using the Net Configuration Assistant and the Net Manager.
|
