Release 2 (9.2)
Part Number A96596-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Real Application Clusters Administration Release 2 (9.2) Part Number A96596-01 |
|
This appendix describes the Real Application Clusters management tools error messages. The groups of error messages in this appendix appear alphabetically. The error message groups in this appendix are:
| See Also:
Oracle9i Database Administrator's Guide for Windows for Windows-based error messages and Oracle9i Database Error Messages for all other error messages |
Cause: An attempt was made to create the Global Services Daemon (GSD) application while there is a GSD application already running.
Action: You cannot create the GSD application at this moment since it already exists. Stop the running GSD and create the GSD application again using 'srvctl add nodeapps'. You can also use the existing GSD application.
Cause: An attempt was made to create a Listener application while there is a running Listener application.
Action: You cannot create the Listener application at this moment since it already exists. Stop the running Listener and create the Listener application again using 'srvctl add nodeapps'. You can also use the existing Listener application.
Cause: An attempt was made to create an Agent application while there is a running Agent application.
Action: You cannot create the Agent application at this moment since it already exists. Stop the running Agent and create the Agent application again using 'srvctl add nodeapps'. You can also use the existing Agent application.
Cause: An attempt was made to create a Virtual IP application while there is a running Virtual IP application.
Action: You cannot create the Virtual IP application at this moment since it already exists. Stop the running Virtual IP application and create the Virtual IP application using 'srvctl add nodeapps'. You can also use the existing Virtual IP application.
Cause: Invalid range of VIP addresses specified for the cluster while doing 'srvctl add vip_range'
Action: Check if the starting and ending addresses in the VIP range being added, belong to the same netmask.
Cause: No free Virtual IP address available from the list of Virtual IP addresses added to the cluster database. All of the of Virtual IP addresses added are in use.
Action: Add new Virtual IP addresses using to the cluster database using 'srvctl add vip_range'
Cause: A Virtual IP address was not found in the Virtual IP range added to the cluster database.
Action: Add Virtual IP addresses to the cluster using 'srvctl add vip_range'
Cause: An error occurred while trying to execute an operation by the Global Services Daemon either on a local node or a remote node.
Action: Check whether the Global Services Daemon is up and responsive by doing 'srvctl config'.
Cause: An error occurred while trying to get the Virtual IP range configuration from the Configuration Repository. Either the Global Services Daemon is not up or the Configuration Repository is not accessible. The configuration repository may not be accessible if the repository is corrupted or for insufficient privileges.
Action: Check if the Global Services Daemon is up and the configuration repository is accessible by doing 'srvctl config'
Cause: An error occurred while trying to add a Virtual IP range configuration to the Configuration Repository. Either the Global Services Daemon is not up or the Configuration Repository is not accessible. The configuration repository may not be accessible if the repository is corrupted or for insufficient privileges.
Action: Check if the Global Services Daemon is up and the configuration repository is accessible by doing 'srvctl config'
Cause: The active node list of the cluster could not be retrieved. This could occur if the operating system dependent clusterware was not functioning properly in one or more nodes in the cluster, or because there was no clusterware installed on the machine.
Action: Check the state of the cluster by running 'lsnodes' binary from ORACLE_HOME/bin and see if it prints the node list correctly. Use vendor documentation to get additional information about the current state of the operating system dependent clusterware.
Cause: An internal error has occurred.
Action: Contact your customer support representative.
Cause: This could happen either because some node in the cluster failed in the middle of a manageability operation or because the communication channel between nodes failed.
Action: Check that all nodes are up and the communication between the nodes is working.
Cause: Attempted file copy operation(s) from the local node to one or more nodes in the cluster and one or multiple of those copy file operations failed. This can occur either because one or more nodes failed during the operation or the destination directory did not have write permission for the user on one or more of the nodes or the source file did not exist or on UNIX platforms 'rcp' command to one or more nodes failed.
Action: Check that the source file exists. Check that all nodes in the cluster are up. Check that destination directory had write permission for the user. On UNIX based platforms check that user has permission to do 'rcp' to all the nodes.
Cause: Attempted file remove operation(s) from the local node to one or more nodes in the cluster and one or multiple of those file remove operations failed. This can occur either because one or more nodes failed during the operation or the destination directory did not have write permission for the user on one or more of the nodes or the source file did not exist or on UNIX platforms 'rcp' command to one or more nodes failed.
Action: See earlier error messages for details.
Cause: Attempted file move operation(s) from the local node to one or more nodes in the cluster and one or multiple of those move file operations failed. This can occur either because one or more nodes failed during the operation or the destination directory did not have write permission for the user on one or more of the nodes or the source file did not exist or on UNIX platforms 'rcp' command to one or more nodes failed.
Action: See earlier error messages for details.
Cause: Attempted directory create operation(s) from the local node to one or more nodes in the cluster and one or multiple of those directory create operations failed. This can occur either because one or more nodes failed during the operation or the destination directory did not have write permission for the user on one or more of the nodes or the source file did not exist or on UNIX platforms 'rcp' command to one or more nodes failed.
Action: See earlier error messages for details.
Cause: Attempted to start a service on all the nodes in the cluster and one or multiple of those services did not start successfully.
Action: Check if all the nodes in cluster are up.
Cause: Attempted to stop a service on all the nodes in the cluster and one or multiple of those services did not start successfully.
Action: See earlier error messages.
Cause: Attempted to delete a service on all the nodes in the cluster and one or multiple of those services did not start successfully.
Action: See earlier error messages.
Cause: Attempted to delete a service on all the nodes in the cluster and one or multiple of those services did not start successfully.
Action: See earlier error messages.
Cause: Attempted to retrieve value of an environment variable which was not defined.
Action: Define the environment variable.
Cause: GSD (Global Services Daemon) could not be started on the local node. This can occur if the operating system dependent clusterware was not functioning properly or there is already a running GSD.
Action: Check the state of the clusterware by running 'lsnodes' from ORACLE_HOME/bin and following vendor documentation. It should list the nodes in the cluster. Try 'gsdctl stop' and then 'gsdctl start' again.
Cause: This can occur if the operating system dependent clusterware was not functioning properly.
Action: Use 'gsdctl stop' on each node to stop the GSDs. Use 'gsdctl start' on each node in the cluster.
Cause: Global Services Daemon was not running on the node.
Action: Use 'gsdctl stat' to check the status of the daemon. Use 'gsdctl start' to start it.
Cause: Attempted to execute an operation on the remote node when the Global Services Daemon was not up on the remote node {0}.
Action: Start the Global Services Daemon on the remote node using 'gsdctl start'.
Cause: The operating system dependent clusterware cannot be contacted. This can occur because the operating system dependent clusterware was not functioning properly.
Action: Check the state of the operating system dependent clusterware using 'lsnodes' and following vendor documentation.
Cause: The operating system dependent clusterware cannot be contacted. This can occur because the operating system dependent clusterware was not functioning properly.
Action: Check the state of the operating system dependent clusterware using 'lsnodes' and following vendor documentation.
Cause: Lack of permission to create destination file or copy file to the destination location.
Action: Verify permission to create the destination file. Also, please make sure that the destination file is not currently in use.
Cause: Files we are trying to delete do not exist, or are currently being used.
Action: If the files we are trying to delete do not exist, ignore this error. If the files we are trying to delete are currently being used, please end the processes that are using the files and then retry.
Cause: Lack of permission to create the service, or service already exists.
Action: Verify permission to create service on destination node or nodes. Also, verify that the service is not already existing.
Cause: Service is not created, service is already running, service marked for deletion, service could not be started properly.
Action: Try to start the service manually from the service control panel and check the Windows Error message that it gives.
Cause: Lack of permission to modify registry entries on the nodes, error while updating the registries.
Action: Verify permission to modify registry entries.
Cause: Absence of Oracle disk partition, failure to load OLM dll.
Action: Verify that OLM dll (oobjlib.dll) is present in the load path. Also, verify that Oracle disk partitions are present by going to the Disk Administrator and looking for partitions.
Cause: Failure to connect to the remote nodes while adding a node to a cluster. Failure to collect VIA information if VIA was chosen.
Action: If you are trying to add a node to an already existing cluster, try to map a drive letter to a drive on each of the remote node (using commands like "net use"). Also, verify the we have permission to start temporary service on remote nodes that will collect VIA information, in case VIA was chosen.
Cause: Failure to connect to remote node.
Action: Try to map a driver letter on local node to the remote node using commands like "net use".
Cause: Service does not exist, or service could not be deleted.
Action: Check the service control panel to see if the service exists. If the service does not exist, ignore this error. If the service exists, try to delete it from the command line using utilities like "net" and "sc". If this fails, check the Windows error message returned by these commands.
Cause: An invalid SRVCTL command line was entered.
Action: Use -h SRVCTL command line option to find out the correct command line syntax and re-enter the command.
Cause: An invalid SRVCTL command line option was entered.
Action: Use -h SRVCTL command line option to find out the correct command line syntax and re-enter the command.
Cause: An invalid SRVCTL command line option value was entered.
Action: Use -h SRVCTL command line option to find out the correct command line syntax and re-enter the command.
Cause: Duplicate SRVCTL command line option was entered.
Action: Eliminate the duplicate and re-enter the command.
Cause: An error occurred when getting Cluster Database configuration for the named database.
Action: Make sure that the database has been configured in Cluster Database Configuration Repository; make sure that GSDs are running on each node in the cluster.
Cause: An invalid node name was entered.
Action: Use the correct node name. A valid node name should match the output from 'lsnodes' and must not contain domain name.
Cause: An invalid instance name was entered.
Action: Use the correct instance name for the database. Run 'srvctl config database -d <db_name>' command to find out all instances of a database in the Cluster Database Configuration.
Cause: An invalid connect string was entered.
Action: Use the correct connect string syntax: <user>/<password>[ as <role>]
Cause: An invalid environment name/value pair was entered during SRVCTL setenv command.
Action: Make sure that the correct name/value string format is used: <name>=<value>
Cause: An error occurred when adding instance to Cluster Database configuration.
Action: Use 'srvctl config database -d <db_name>' command to check if the database has been configured in Cluster Database Configuration Repository; make sure that GSDs are running on each node in the cluster.
Cause: An error occurred when removing an instance from Cluster Database Configuration.
Action: Use 'srvctl config database -d <db_name>' command to check if the database and instance have been configured in Cluster Database Configuration Repository; make sure that GSDs are running on each node in the cluster.
Cause: An error occurred when changing the instance and node mapping in Cluster Database Configuration.
Action: Use 'srvctl config database -d <db_name>' command to check if the database and instance have been configured in Cluster Database Configuration Repository; make sure that GSDs are running on each node in the cluster.
Cause: An error occurred when setting environment variables for a database or an instance.
Action: Use 'srvctl config database -d <db_name>' command to check if the database and/or the instance have been configured in Cluster Database Configuration Repository; make sure that GSDs are running on each node in the cluster.
Cause: An error occurred when unsetting environment variables for a database or an instance.
Action: Use 'srvctl getenv' command to check if the environment variable exists for the database or instance; make sure that the database and/or the instance have been configured in Cluster Database Configuration Repository; make sure that GSDs are running on each node in the cluster.
Cause: Could not get status information of an instance.
Action: Use 'srvctl config database -d <db_name>' command to check if the instance has been configured in the Oracle database; make sure that GSDs are running on each node in the cluster.
Cause: Could not get status information of a listener.
Action: Check if the listener has been configured in the listener configuration file and if the database instance on the node is listed in SID_NAME in the listener configuration; make sure that GSDs are running on each node in the cluster.
Cause: The cluster database configuration cannot be retrieved from the repository. This can occur either because the database was never registered, or because the repository itself has not been created.
Action: Check if the database has been configured by printing a list of all cluster databases using 'srvctl config'. If the repository has not been created, use 'srvconfig -init' to create it.
Cause: The instance could not be started using the SQL*Plus startup command.
Action: Try starting the named instance manually using SQL*Plus to see why it failed.
Cause: The SQL*Plus shutdown command returned an error while stopping the instance.
Action: Try stopping the named instance manually using SQL*Plus to see why it failed.
Cause: Some components of the cluster database could not be started.
Action: See earlier error message for details
Cause: Some components of the cluster database reported errors while being stopped
Action: See earlier error messages for details
Cause: The cluster database could not be started
Action: See earlier error messages for details
Cause: The cluster database reported errors while being shut down
Action: See earlier error messages for details
Cause:
Action: Contact your customer support representative
Cause:
Action: Contact your customer support representative
Cause: Either the listener name associated with an instance could not be determined, or "lsnrctl start" failed for a listener.
Action: Verify that listener.ora contains a SID_LIST entry for each instance of the named database, and that the lsnrctl start command succeeds for those listeners
Cause: Either the listener name associated with an instance could not be determined, or "lsnrctl stop" failed for a listener.
Action: Verify that listener.ora contains a SID_LIST entry for each instance of the named database, and that the lsnrctl stop command succeeds for those listeners
Cause: The listener name associated with an instance could not be determined.
Action: Ensure that listener.ora contains a SID_LIST entry for the named instance
Cause: The argument to the -t option is not of the form <name>=<value> or it contains special characters.
Action: Ensure that the -t option has an argument of the form <name>=<value>. Enclose the argument to the -t flag in quotes.
Cause: The named environment variable is not defined for the named cluster database
Action: Set a value for the variable with "srvctl set env"
Cause: The named environment variable is not defined for the given instance
Action: Set a value for the variable with "srvctl set env"
Cause: The named environment variable is not defined
Action: Set a value for the named environment variable with "srvctl set env"
Cause: Either the listener name associated with the instance could not be determined, or "lsnrctl status" failed for that listener.
Action: Verify that listener.ora contains a SID_LIST entry for the named instance, and that the lsnrctl status command succeeds
Cause: The cluster database was never registered in the repository.
Action: Check if the database has been configured by printing a list of all cluster databases using 'srvctl config'.
Cause: An attempt was made to register a cluster database which was already existing in the repository.
Action: Check if the database has already been configured by printing a list of all cluster databases using 'srvctl config'.
Cause: The named instance was never registered in the repository.
Action: Use 'srvctl config' to discover all the databases and their instances.
Cause: An attempt was made to register an instance which already existed.
Action: See earlier messages.
Cause: An error occurred while attempting to add a new cluster database in the configuration repository. Either the Global Services Daemons were not up on all the nodes in the cluster or the configuration repository was not accessible or the configuration repository was never initialized.
Action: Use 'gsdctl stat' on each node to check if the Global Services Daemons are up. If the Global Services Daemon is not up on any node use 'gsdctl start' to start it. Check if the configuration repository is accessible by using 'srvctl config'. Use 'srvconfig -init' to initialize the configuration repository if it was never initialized.
Cause: Same as PRKR-1005
Action: See earlier error messages.
Cause: Same as PRKR-1005
Action: See earlier error messages.
Cause: Same as PRKR-1005
Action: See earlier error messages.
Cause: Same as PRKR-1005
Action: See earlier error messages.
Cause: Same as PRKR-1005
Action: See earlier error messages.
Cause: Same as PRKR-1005
Action: Contact your customer support representative
Cause:
Action: Contact your customer support representative
Cause:
Action: Contact your customer support representative
Cause:
Action: Contact your customer support representative
Cause:
Action: Contact your customer support representative
Cause: Same as PRKR-1005
Action: See earlier error messages.
Cause: Same as PRKR-1005
Action: See earlier error messages.
Cause:
Action: Contact your customer support representative
Cause:
Action: Contact your customer support representative
Cause: Same as PRKR-1005
Action: See earlier error messages.
Cause: Same as PRKR-1005
Action: See earlier error messages.
Cause: An attempt was made to use an incompatible version of the configuration repository.
Action: Contact your customer support representative
Cause: The named file did not exist.
Action: Check if the file exists
Cause: The named file did not have the specified permission.
Action: Try changing the permission on the file to the specified permission
Cause: The file did not contain the specified property.
Action: Contact your customer support representative
Cause: The file did not contain the specified property.
Action: Contact your customer support representative
Cause: Same as PRKR-1005
Action: See earlier error messages.
Cause: The management repository was never initialized.
Action: Use 'srvconfig -init' to initialize the repository.
Cause: Invalid argument specified to 'srvconfig -init'
Action: See usage of 'srvconfig -init' for details.
Cause: The specified option was invalid
Action: Check usage.
Cause: The specified option was invalid for srvconfig
Action: Check usage for details
Cause: Attempted to retrieve the version of the repository.
Action: No action is required.
Cause: A valid configuration repository was detected.
Action: No action is required.
Cause: An attempt was made to initialize the management repository while the Global Services Daemons were up on one or more nodes in the cluster.
Action: Stop all Global Services Daemons on all nodes in the cluster by using 'gsdctl stop' command on every node. Try the 'srvconfig -init' operation again.
Cause: Attempted to create a file in a directory which did not exist or which d id not have the right permissions.
Action: Create the directory if it did not exist or change the permission of the directory.
Cause:
Action: Contact your customer support representative
Cause: An attempt was made to register an 8.1.7 or previous database in the management repository and the file argument passed was not of <cluster database name>.conf form.
Action: See usage of srvconfig for details.
Cause: Detected an invalid parameter specified in <opsName>.conf file while attempting conversion of 8.l.7 or previous version of Oracle Parallel Server into RAC.
Action: Check 8.1.7 documentation and make sure that format of <opsName>.conf file is consistent with the documentation.
Cause: Detected an invalid parameter specified in <opsName>.conf file while attempting to add a 8.l.7 or previous version of Oracle Parallel Server database in the configuration repository.
Action: Check 8.1.7 documentation and make sure that format of <opsName>.conf file is consistent with the documentation.
Cause: Extra number of arguments provided to 'srvconfig'.
Action: See usage of 'srvconfig' for details.
Cause: Detected an invalid registry entry while attempting to add a 8.1.7 or previous version of Oracle Parallel Server in the configuration repository.
Action: See earlier error messages.
Cause: Attempted to retrieve non existing environment variable.
Action: Set the environment variable.
|
 Copyright © 1998, 2002 Oracle Corporation. All Rights Reserved. |
|
