This chapter describes messages generated by PRIMECLUSTER Wizard for Oracle and lists the possible causes and actions you can take to resolve any problems indicated by a message.
The following messages appear in syslog (daemon.err).
Oracle instance resource messages
Oracle listener resource messages
Common messages
The following messages appear in command execution screen.
clgetoralog messages
clorainfo messages
hvoradisable/hvoraenable messages
cloracpy messages
clorapass messages
Oracle instance resource messages
[Content]
A system error occurred. Acquisition of shared memory or semaphores failed.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
[Content]
The action definition file cannot be opened.
[Corrective action]
Check if the action definition file already exists, or file access privileges have been changed.
[Content]
The errno setting of the action definition file is incorrect.
[Corrective action]
Check the errno setting of line=linenumber in the action definition file.
[Content]
The status setting of the action definition file is incorrect.
[Corrective action]
Check the status setting of line=linenumber in the action definition file.
[Content]
The action setting of the action definition file is incorrect.
[Corrective action]
Check the action setting of line=linenumber in the action definition file.
[Content]
An Oracle instance process error was detected.
[Corrective action]
Check if Oracle instance is properly running by referring to the Oracle instance alert log.
[Content]
The Offline state of the resource will be notified.
[Corrective action]
Check if Oracle instance is properly running by referring to the Oracle instance alert log.
[Content]
The Faulted state of the resource will be notified.
[Corrective action]
Check if Oracle instance is properly running by referring to the Oracle instance alert log.
[Content]
Monitoring will be retried.
[Corrective action]
Check if Oracle instance is properly running by referring to the Oracle instance alert log.
[Content]
The RMS configuration file (hvgdconfig file) cannot be read.
[Corrective action]
If you modify the RMS configuration file manually, check the settings.
[Content]
The ResourceName setting of the RMS configuration file (hvgdconfig file) is incorrect.
[Corrective action]
If you modify the RMS configuration file manually, check the settings.
[Content]
The AttributeName setting of the RMS configuration file (hvgdconfig file) is incorrect.
[Corrective action]
If you modify the RMS configuration file manually, check the settings.
[Content]
An internal error occurred. Acquisition of shared memory or semaphores failed.
[Corrective action]
Contact system administrators.
[Content]
An internal error occurred. Notification of monitoring result failed.
[Corrective action]
Contact system administrators.
[Content]
An internal error occurred. Checking whether or not the detector process is alive failed.
[Corrective action]
Contact system administrators.
[Content]
The AttributeName setting of the RMS configuration file (hvgdconfig file) is incorrect.
[Corrective action]
If you modify the RMS configuration file manually, check the settings.
[Content]
An Oracle instance error ORA-xxxxx is output.
[Corrective action]
Check if Oracle instance is properly running by referring to the Oracle instance alert log.
[Content]
The warning state of the resource will be notified.
[Corrective action]
Check if Oracle instance is properly running by referring to the Oracle instance alert log.
[Content]
An Oracle instance error occurred while Oracle instance startup or shutdown was in progress (svrmgrl).
[Corrective action]
Check if Oracle instance is properly running by referring to the Oracle instance alert log.
[Content]
An Oracle instance error occurred while Oracle instance startup or shutdown was in progress (sqlplus).
[Corrective action]
Check if Oracle instance is properly running by referring to the Oracle instance alert log.
Oracle listener resource messages
[Content]
A system error occurred. Acquisition of shared memory or semaphores failed.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
[Content]
ORACLE_HOME cannot be acquired.
[Corrective action]
Check if ORACLE_HOME is correctly set for the environment variable.
[Content]
The RMS configuration file (hvgdconfig file) cannot be read.
[Corrective action]
If you modify the RMS configuration file manually, check the settings.
[Content]
The ResourceName setting of the RMS configuration file (hvgdconfig file) is incorrect.
[Corrective action]
If you modify the RMS configuration file manually, check the settings.
[Content]
The AttributeName setting of the RMS configuration file (hvgdconfig file) is incorrect.
[Corrective action]
If you modify the RMS configuration file manually, check the settings.
[Content]
Listener monitoring with tnsping command failed.
[Corrective action]
Check the Listener log and if the Listener is properly running.
[Content]
The Oracle listener name is incorrect.
[Corrective action]
Check the Listener settings such as listener.ora and tnsnames.ora.
[Content]
An Oracle listener process failure was detected. It will be output along with userApplication stop.
[Corrective action]
If the error is output during userApplication is online, check the Listener log and if the Listener is properly running.
[Content]
The Listener process ID is unknown.
[Corrective action]
Check the Listener log and if the Listener is properly running.
[Content]
An internal error occurred. Notification of monitoring result failed.
[Corrective action]
Contact system administrators.
[Content]
A system error occurred.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
[Content]
An internal error occurred. Acquisition of shared memory or semaphores failed.
[Corrective action]
Contact system administrators.
[Content]
An internal error occurred. Checking whether or not the detector process is alive failed.
[Corrective action]
Contact system administrators.
Common messages
[Content]
Monitoring resource was discontinued after the hvoradisable was executed.
[Corrective action]
None. Execute "hvoraenable" command to restart resource monitoring.
Information
For details, refer to "4.1 hvoradisable - Discontinue Monitoring Resources".
[Content]
Resource monitoring was restarted after hvoraenable command was executed.
[Corrective action]
None.
Information
For details, refer to "4.2 hvoraenable - Restart Monitoring Resources".
[Content]
A system error occurred. Acquisition of memory failed.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
[Content]
A system error occurred. Acquisition of semaphore failed.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
[Content]
A system error occurred. Generation of process failed.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
[Content]
The Oracle user settings are incorrect.
[Corrective action]
Check if Oracle user information (e.g. username) is correct.
[Content]
Log files cannot be created.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
[Content]
A system error occurred. Initialization failed.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
[Content]
A system error occurred. The detector will be terminated.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
[Content]
The AttributeName setting of the RMS configuration file (hvgdconfig file) is not set.
[Corrective action]
If you modify the RMS configuration file manually, check the settings.
[Content]
The AttributeName setting of the RMS configuration file (hvgdconfig file) is incorrect.
[Corrective action]
If you modify the RMS configuration file manually, check the settings.
[Content]
An internal error occurred. Checking monitoring disruption failed.
[Corrective action]
Contact system administrators.
[Content]
An internal error occurred. Checking whether or not the monitoring process is alive failed.
[Corrective action]
Contact system administrators.
[Content]
A system error occurred. Acquisition of shared memory or semaphores failed.
[Corrective action]
Contact system administrators.
[Content]
A system error occurred. Acquisition of shared memory or semaphores failed.
[Corrective action]
Contact system administrators.
[Content]
Since there is no response from Oracle instance or Listener, timeout occurs.
[Corrective action]
Check if Oracle instance or Listener is properly running by referring to the Oracle instance alert log or Listener log.
[Content]
An internal error occurred. Communication with the script failed.
[Corrective action]
Contact system administrators.
[Content]
Startup of the monitoring process failed.
[Corrective action]
Contact system administrators.
[Content]
A system error occurred. Creation of output pipe failed.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
Note
PRIMECLUSTER Wizard for Oracle outputs error messages to system console other than messages described above if error in Oracle instance startup occurs.
clgetoralog messages
[Content]
Cannot make a temporary directory.
[Corrective action]
/tmp space may be insufficient. Check the system environment.
[Content]
The specified RMS configuration RMS_configuration does not exist.
[Corrective action]
Retry with a correct RMS configuration name.
[Content]
Not enough disk space in path_name.
[Corrective action]
path_name space may be insufficient. Check the system environment.
[Content]
Cannot make a directory directory_name where collected information is stored.
[Corrective action]
Disk space may be insufficient. Check the system environment.
[Content]
Cannot make file_name because the same name file already exists.
[Corrective action]
The directory where the collected information has been stored is shown in the following message. Create an archive file from the directory manually with other file name.
[Content]
Cannot create an archive file file_name.
[Corrective action]
The directory where the collected information has been stored is shown in the following message. Create an archive file from the directory manually.
[Content]
Cannot get local SysNode name, but clgetoralog continues collecting information.
[Corrective action]
None.
[Content]
Cannot execute an RMS command hvw(1M) correctly, but clgetoralog continues collecting information.
[Corrective action]
None.
[Content]
An RMS command hvw(1M) has returned unexpected result, but clgetoralog continues collecting information.
[Corrective action]
None.
[Content]
There are no definitions of Wizard for Oracle resources in hvgdconfig file, but clgetoralog continues collecting information.
[Corrective action]
None.
[Content]
Cannot get RMS configuration name, but clgetoralog continue collecting information.
[Corrective action]
None.
[Content]
Cannot get RMS configuration name, but clgetoralog continue collecting information.
[Corrective action]
None.
clorainfo messages
[Content]
Cannot get a local SysNode name.
[Corrective action]
Check if CF (Cluster Foundation) has been configured and is "UP" state.
[Content]
Cannot check if RMS is running or not.
[Corrective action]
Check if PRIMECLUSTER installation, cluster setup and building a userApplication (cluster application) have been completed.
[Content]
Cannot get an RMS configuration name.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Content]
CONFIG.rms file does not exist.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Content]
There are no Wizard for Oracle resources in a build userApplication (cluster application).
[Corrective action]
Check if building a userApplication (cluster application) has been completed or Oracle instance resources or Listener resources are included in the userApplication.
[Content]
The specified resource resource_name does not exist on the local node SysNode_name, or is not a Wizard for Oracle resource.
[Corrective action]
Retry with a correct resource name.
[Content]
The specified resource resource_name is not a Wizard for Oracle resource.
[Corrective action]
Retry with a correct resource name.
[Content]
RMS configuration is invalid.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Content]
The specified RMS configuration does not exist.
[Corrective action]
Retry with a correct RMS configuration name.
hvoradisable/hvoraenable messages
[Content]
Internal error occurred.
[Corrective action]
Contact system administrators.
[Content]
Cannot disable or enable monitoring.
[Corrective action]
Contact system administrators.
[Content]
hvgdconfig file does not exist.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Content]
Cannot get a local SysNode name.
[Corrective action]
Check if CF (Cluster Foundation) has been configured and is "UP" state.
[Content]
Cannot get an RMS configuration name.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Content]
Cannot execute an RMS command hvw(1M) correctly.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Content]
Cannot get an result of RMS command hvw(1M) correctly.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Content]
Cannot disable or enable monitoring because of details.
[Corrective action]
Check if PRIMECLUSTER installation, cluster setup and building a userApplication (cluster application) have been completed.
[Content]
There are no Wizard for Oracle resources in the specified userApplication userApplication_name.
[Corrective action]
Retry with a correct userApplication name.
[Content]
There are no Wizard for Oracle resources in the current RMS configuration.
[Corrective action]
Check if building a userApplication (cluster application) has been completed or Oracle instance resources or Listener resources are included in the userApplication.
[Content]
There are no Wizard for Oracle resources on a local node SysNode_name.
[Corrective action]
Check if building a userApplication (cluster application) has been completed or Oracle instance resources or Listener resources are included in the userApplication.
[Content]
The specified userApplication name or resource name is invalid.
[Corrective action]
Retry with a correct userApplication name and resource name.
[Content]
The specified resource does not exist on a local node SysNode_name.
[Corrective action]
Retry with a correct resource name or retry on a correct node.
[Content]
The monitoring is disabled or enabled although RMS is not running.
[Corrective action]
This setting will become effective in the next RMS startup.
cloracpy messages
[Content]
ORACLE_SID cannot be acquired.
[Corrective action]
Check if ORACLE_SID is correctly set for the environment variable.
[Content]
ORACLE_HOME cannot be acquired.
[Corrective action]
Check if ORACLE_HOME is correctly set for the environment variable.
[Content]
ORACLE_BASE cannot be acquired.
[Corrective action]
Check if ORACLE_BASE is correctly set for the environment variable.
[Content]
ORACLE_HOME/dbs directory does not exist.
[Corrective action]
Check if the directory exists.
[Content]
ORACLE_HOME/network/admin directory does not exist.
[Corrective action]
Check if the directory exists.
[Content]
ORACLE_BASE/admin/ORACLE_SID directory does not exist.
[Corrective action]
On the standby node, extract the backup data and create directory which is specified in the AUDIT_FILE_DEST initialization parameter.
The access privilege to the directory must be also the same as that on the operating node.
[Content]
ORACLE_BASE/diag directory does not exist.
[Corrective action]
On the standby node, extract the backup data and create directory which is specified in the DIAGNOSTIC_DEST initialization parameter.
The access privilege to the directory must be also the same as that on the operating node.
[Content]
Cannot execute tar(1) command correctly.
[Corrective action]
Check the disk space or authority of /tmp directory.
clorapass messages
[Content]
Cannot read the password file.
[Corrective action]
Check the password file.
[Content]
Password file occurred format error.
[Corrective action]
Delete the password file, set password again. If more than one password was registered in the file, set all of them.
[Content]
A system error occurred. Acquisition of memory failed.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
[Content]
Cannot write the password file.
[Corrective action]
Check the password file.
[Content]
An incorrect password was entered.
[Corrective action]
Enter a correct password.
