PRIMECLUSTER Wizard for Oracle Configuration and Administration Guide 4.2 - Linux for Itanium - |
Contents
![]() ![]() |
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.
For details of the commands, refer to "4.1 hvoradisable - Discontinue Monitoring Resources", "4.2 hvoraenable - Restart Monitoring Resources".
PRIMECLUSTER Wizard for Oracle outputs error messages to system console other than messages described above if error in Oracle instance startup occurs.
[Corrective action]
Check the system environment.
[Corrective action]
Retry with a correct RMS configuration name.
[Corrective action]
Check the system environment.
[Corrective action]
Check the system environment.
[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.
[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.
[Corrective action]
None.
[Corrective action]
None.
[Corrective action]
None.
[Corrective action]
None.
[Corrective action]
None.
[Corrective action]
None.
[Corrective action]
Check if CF (Cluster Foundation) has been configured and is "UP" state.
[Corrective action]
Check if PRIMECLUSTER installation, cluster setup and building a cluster application (userApplication) have been completed.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Corrective action]
Check if building a userApplication (cluster application) has been completed or Oracle instance resources or Listener resources are included in the userApplication.
[Corrective action]
Retry with a correct resource name.
[Corrective action]
Retry with a correct resource name.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Corrective action]
Retry with a correct RMS configuration name.
[Corrective action]
Contact your system administrator.
[Corrective action]
Contact your system administrator.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Corrective action]
Check if CF (Cluster Foundation) has been configured and is "UP" state.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Corrective action]
Check if building a userApplication (cluster application) has been completed.
[Corrective action]
Check if PRIMECLUSTER installation, cluster setup and building a cluster application (userApplication) have been completed.
[Corrective action]
Retry with a correct userApplication 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.
[Corrective action]
Check if building a userApplication (cluster application) has been completed or Oracle instance resources or Listener resources are included in the userApplication.
[Corrective action]
Retry with a correct userApplication name and resource name.
[Corrective action]
Retry with a correct resource name or retry on a correct node.
[Corrective action]
This setting will become effective in the next RMS startup.
[Corrective action]
Check if ORACLE_SID is correctly set for the environment variable.
[Corrective action]
Check if ORACLE_HOME is correctly set for the environment variable.
[Corrective action]
Check if ORACLE_BASE is correctly set for the environment variable.
[Corrective action]
Check if the directory exists.
[Corrective action]
Check if the directory exists.
[Corrective action]
Check if the directory exists.
[Corrective action]
Check the disk space or authority of /tmp directory.
[Corrective action]
Check the password file.
[Corrective action]
Delete the password file, set password again. If more than one password was registered in the file, set all of them.
[Corrective action]
The problem might be due to insufficient system resource. Check the system environment.
[Corrective action]
Check the password file.
[Corrective action]
Enter a correct password.
Contents
![]() ![]() |