No SID specified

The Sid attribute in the Oracle type has not been set.

Solution: Set the Sid attribute value to the correct database instance.

sqlplus not found in <Oracle_Home>/bin

The client utility sqlplus is not found in the $ORACLE_HOME/bin directory.

Solution: Verify that the Oracle home has been correctly specified and that this executable is present.

srvctl not found in <Oracle_Home>/bin

The client utility srvctl is not found in the $ORACLE_HOME/bin directory.

Solution: Verify that the Oracle home has been correctly specified and that this executable is present.

Oracle <SID> failed to stop

Oracle database <SID> not running

Warning message to indicate that the database instance was not running even before the clean or offline entry points were executed.

Solution: No action required.

Oracle (<SID>) kill TERM <PID1, PID2, ...>

Warning message to indicate that the Oracle processes would be signaled with SIGTERM.

Solution: No action required.

Oracle (<SID>) kill KILL <PID1, PID2, ...>

Warning message to indicate that the Oracle processes would be signaled with SIGKILL.

Solution: No action required.

Database in QUIESCING/QUIESCED mode

Warning message to indicate that database is in QUIESCING or QUIESCED mode.

Database in RESTRICTED mode

Warning message to indicate that database is in RESTRICTED mode.

Database in SUSPENDED state

Warning message to indicate that database is in SUSPENDED state.

Resource <Res_name> - monitor procedure did not complete within the expected time.

Refer to Oracle's alert log for more information.

When a monitor times out as many times as the value specified, the corresponding resource is brought down by calling the clean entry point. The resource is then marked FAULTED, or it is restarted, depending on the RestartLimit attribute value.

Solution: Set the FaultOnMonitorTimeouts attribute value to 0 so that the monitor failures are not considered indicative of a resource fault.

Another possible reason could be that automatic archiving was not enabled while setting up the database.

Solution: Archive the database manually. If automatic archival is enabled, set the LOG_ARCHIVE_START parameter value in the file init.ora to TRUE.

VCS ERROR Resource <Res_name>: online procedure did not complete within the expected time.

Solution: Increase the Oracle agent's OnlineTimeout interval.

Custom script /opt/VRTSagents/ha/bin/Oracle/start_custom_<SID>.sql does not exist. Will not be able to start the database.

The agent could not find the custom script at the specified location to start the database.

Solution: Make sure the custom file exists at the specified location and has valid permissions.

Custom script /opt/VRTSagents/ha/bin/Oracle/shut_custom_<SID>.sql does not exist. Using default shutdown option.

The agent could not find the custom script at the specified location to stop the database.

Solution: Make sure the custom file exists and the specified location and has valid permissions.

oraerror.dat did not have records that could be parsed

The file oraerror.dat is not present or has records in an unsupported format.

Solution: Make sure the file exists and has data in the supported format.

Incorrect Monitor Option

The MonitorOption value is less than 0 or greater than 1.

Solution: Set the MonitorOption attribute value to 0 or 1.

MonitorOption value not applicable for this Oracle Version

The health check monitoring option is selected when Oracle version is not Oracle 10g or later.

Solution: Set the MonitorOption value to 0 to select the process check monitoring option.

VCSAgExec returned failure when trying to execute health check monitor test

Internal error.

Solution: Contact Technical Support for further assistance.

VCSAgExec returned failure while trying to find Oracle version

Internal error.

Solution: Contact Technical Support for further assistance.

One or more of the attributes User:Pword:Table:MonScript are not set correctly. Detail monitoring will not be enabled!!

Detail Monitoring has been enabled but the necessary attributes for detail monitoring have not been set correctly.

Solution: Set the values of the required attributes for detail monitoring correctly.