Skip Headers

Oracle9i Real Application Clusters Administration
Release 2 (9.2)

Part Number A96596-01
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback

Go to previous page Go to next page

C
Real Application Clusters Management Tools Error Messages

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:

Global Services Daemon Error Messages (PRKA)


PRKA-2001: GSD already exists

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.


PRKA-2002: Listener already exists

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.


PRKA-2003: Agent already exists

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.


PRKA-2004: VIP already exists

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.


PRKA-2006: Netmasks are different

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.


PRKA-2007: No free VIP is available

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'


PRKA-2008: VIP is not found

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'


PRKA-2009: Remote command failed

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'.


PRKA-2010: Failed to get the VIP Range configuration in formation from the OCR

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'


PRKA-2011: Failed to add the VIP Range configuration in formation to the OCR

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'

Cluster Command Error Messages (PRKC)


PRKC-1000 "No active nodes detected in the cluster"

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.


PRKC-1001 "Error submitting commands in the buffer"

Cause: An internal error has occurred.

Action: Contact your customer support representative.


PRKC-1002 "All the submitted commands did not execute successfully"

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.


PRKC-1004 "Problem in copying file to nodes"

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.


PRKC-1005 "Problem in removing file from 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.


PRKC-1006 "Problem in moving file to nodes"

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.


PRKC-1007 "Problem in creating directories on the nodes"

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.


PRKC-1009 "Failed to start the service on all nodes"

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.


PRKC-1010 "Failed to stop the service on all nodes"

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.


PRKC-1011 "Failed to delete the service from all nodes"

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.


PRKC-1012 "Failed to create the service on all node"

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.


PRKC-1016 "Problem in retrieving value of the enviornment variable"

Cause: Attempted to retrieve value of an environment variable which was not defined.

Action: Define the environment variable.


PRKC-1017 "Problem restarting GSD"

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.


PRKC-1018 "Error getting coordinator node"

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.


PRKC-1019 "Error creating handle to daemon on the node {0}"

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.


PRKC-1020 "Exception while executing the operation on the remote node {0}"

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'.


PRKC-1021 "Problem in the clusterware"

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.


PRKC-1022 "Could not get "node name" for node {0} in {1}"

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.

Cluster Setup for Windows NT Error Messages (PRKI)


PRKI-2059 "Unable to copy files to the nodes"

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.


PRKI-2119 "Unable to delete files on {0}. Install may not succeed if files are not deleted"

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.


PRKI-2060 "Unable to create service on the nodes"

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.


PRKI-2061 "Unable to start service on the nodes"

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.


PRKI-2064 "Unable to update registry entries on the nodes"

Cause: Lack of permission to modify registry entries on the nodes, error while updating the registries.

Action: Verify permission to modify registry entries.


PRKI-2066 "Unable to find an Oracle disk partition. Please exit from the wizard, create Oracle partitions and try again."

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.


PRKI-2114 "Cannot collect and verify hardware information for all the nodes. Press abort to exit the wizard or ignore to continue."

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.


PRKI-2116 "Cannot connect to remote drive on node {0}"

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".


PRKI-2120 "Unable to delete service {0} on {1}. Install may not succeed if services are not deleted"

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.

Server Control (SRVCTL) Utility Error Messages (PRKO)


PRKO-2001: "Invalid command line syntax"

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.


PRKO-2002: "Invalid command line option: "

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.


PRKO-2003: "Invalid command line option value: "

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.


PRKO-2004: "Repetition of command line option: "

Cause: Duplicate SRVCTL command line option was entered.

Action: Eliminate the duplicate and re-enter the command.


PRKO-2005: "Application error: Failure in getting Cluster Database Configuration for: "

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.


PRKO-2006: "Invalid node name: "

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.


PRKO-2007: "Invalid instance 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.


PRKO-2008: "Invalid connect string: "

Cause: An invalid connect string was entered.

Action: Use the correct connect string syntax: <user>/<password>[ as <role>]


PRKO-2009: "Invalid name/value string: "

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>


PRKO-2010: "Error in adding instance to node: "

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.


PRKO-2011: "Error in removing instance: "

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.


PRKO-2012: "Error in moving instance to node: "

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.


PRKO-2013: "Error in setting env: "

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.


PRKO-2014: "Error in unsetting env: "

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.


PRKO-2015: "Error in checking condition of instance on node: "

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.


PRKO-2016: "Error in checking condition of listener on node: "

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.

Cluster Database Management Error Messages (PRKP)


PRKP-1000 "Cannot retrive configuration for cluster database {0}"

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.


PRKP-1001 "Error starting instance {0} on node {1}"

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.


PRKP-1002 "Error stopping instance {0} on node {1}"

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.


PRKP-1003 "Startup operation partially failed"

Cause: Some components of the cluster database could not be started.

Action: See earlier error message for details


PRKP-1004 "Shutdown operation partially failed"

Cause: Some components of the cluster database reported errors while being stopped

Action: See earlier error messages for details


PRKP-1005 "Failed to start up cluster database {0}"

Cause: The cluster database could not be started

Action: See earlier error messages for details


PRKP-1006 "Failed to shut down cluster database {0}"

Cause: The cluster database reported errors while being shut down

Action: See earlier error messages for details


PRKP-1007 "Failed to start all the listeners associated with all the instances of cluster database {0}"

Cause:

Action: Contact your customer support representative


PRKP-1008 "Failed to start listeners associated with instance {0} on node {1}"

Cause:

Action: Contact your customer support representative


PRKP-1009 "Failed to stop all the listeners associated with all the instances of cluster database {0}"

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


PRKP-1010 "Failed to stop all the listeners associated with instance {0} on node{1}"

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


PRKP-1011 "Failed to get all the listeners associated with instance {0} on node{1}"

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


PRKP-1012 "Invalid environment variable {0} setting for cluster database {1}"

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.


PRKP-1013 "{0}: undefined environment variable for cluster database {1}"

Cause: The named environment variable is not defined for the named cluster database

Action: Set a value for the variable with "srvctl set env"


PRKP-1014 "{0}: undefined environment variable for instance {1} of cluster database {2}"

Cause: The named environment variable is not defined for the given instance

Action: Set a value for the variable with "srvctl set env"


PRKP-1015 "{0}: undefined environment variable"

Cause: The named environment variable is not defined

Action: Set a value for the named environment variable with "srvctl set env"


PRKP-1040 "Failed to get status of the listeners associated with instance {0} on node{1}"

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

Repository Error Messages (PRKR)


PRKR-1001 "cluster database {0} does not exist"

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'.


PRKR-1002 "cluster database {0} already exists"

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'.


PRKR-1003 "instance {0} does not exist"

Cause: The named instance was never registered in the repository.

Action: Use 'srvctl config' to discover all the databases and their instances.


PRKR-1004 "instance {0} already exists"

Cause: An attempt was made to register an instance which already existed.

Action: See earlier messages.


PRKR-1005 "adding of cluster database {0} configuration failed, {1}"

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.


PRKR-1006 "deleting of cluster database {0} configuration failed, {1}"

Cause: Same as PRKR-1005

Action: See earlier error messages.


PRKR-1007 "getting of cluster database {0} configuration failed, {1}"

Cause: Same as PRKR-1005

Action: See earlier error messages.


PRKR-1008 "adding of instance {0} on node {1} to cluster database {2} failed, {3}"

Cause: Same as PRKR-1005

Action: See earlier error messages.


PRKR-1009 "deleting of instance {0} from cluster database {1} failed, {2}"

Cause: Same as PRKR-1005

Action: See earlier error messages.


PRKR-1010 "moving of instance {0} to node {1} of cluster database {2} failed, {3}"

Cause: Same as PRKR-1005

Action: See earlier error messages.


PRKR-1011 "renaming of instance {0} to instance {1} of cluster database {2} failed, {3}"

Cause: Same as PRKR-1005

Action: Contact your customer support representative


PRKR-1012 "error {0} while serializing configuration of cluster database {1}"

Cause:

Action: Contact your customer support representative


PRKR-1013 "error {0} while deserializing configuration of cluster database {1}"

Cause:

Action: Contact your customer support representative


PRKR-1014 "error {0} while serializing directory"

Cause:

Action: Contact your customer support representative


PRKR-1015 "error {0} while deserializing directory"

Cause:

Action: Contact your customer support representative


PRKR-1016 "reading of cluster database {0} configuration failed, {1}, {2}"

Cause: Same as PRKR-1005

Action: See earlier error messages.


PRKR-1017 "writing of cluster database {0} configuration failed, {1}, {2}"

Cause: Same as PRKR-1005

Action: See earlier error messages.


PRKR-1018 "reading of directory failed, {0}, {1}"

Cause:

Action: Contact your customer support representative


PRKR-1019 "writing of directory failed, {0}, {1}"

Cause:

Action: Contact your customer support representative


PRKR-1020 "reading of version information failed, {0}, {1}"

Cause: Same as PRKR-1005

Action: See earlier error messages.


PRKR-1021 "writing of version information failed, {0}, {1}"

Cause: Same as PRKR-1005

Action: See earlier error messages.


PRKR-1022 "raw device {0} contains incompatible version, {1} != {2}"

Cause: An attempt was made to use an incompatible version of the configuration repository.

Action: Contact your customer support representative


PRKR-1023 "file {0} does not exist"

Cause: The named file did not exist.

Action: Check if the file exists


PRKR-1024 "file {0} does not have {1} permissions"

Cause: The named file did not have the specified permission.

Action: Try changing the permission on the file to the specified permission


PRKR-1025 "file {0} does not contain property {1}"

Cause: The file did not contain the specified property.

Action: Contact your customer support representative


PRKR-1026 "property {0} not set in file {1}"

Cause: The file did not contain the specified property.

Action: Contact your customer support representative


PRKR-1027 "failed to retrieve list of cluster databases"

Cause: Same as PRKR-1005

Action: See earlier error messages.


PRKR-1028 "raw device {0} is invalid\n[HINT: initialize raw device by using 'srvconfig' tool]"

Cause: The management repository was never initialized.

Action: Use 'srvconfig -init' to initialize the repository.


PRKR-1038 "invalid argument {0} specified to -init option"

Cause: Invalid argument specified to 'srvconfig -init'

Action: See usage of 'srvconfig -init' for details.


PRKR-1039 "invalid option {0} specified"

Cause: The specified option was invalid

Action: Check usage.


PRKR-1040 "missing <file> argument for {0} option"

Cause: The specified option was invalid for srvconfig

Action: Check usage for details


PRKR-1045 "raw device version '{0}'"

Cause: Attempted to retrieve the version of the repository.

Action: No action is required.


PRKR-1046 "srvconfig detected valid raw device '{0}'\n[HINT: please specify -init -f option to forcefully initialize it]"

Cause: A valid configuration repository was detected.

Action: No action is required.


PRKR-1047 "raw device {0} is in use by daemon(s) on node(s) {1}"

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.


PRKR-1050 "file {0} creation in {1} directory failed, check permissions, etc."

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.


PRKR-1051 "file {0} does not contain an entry for dbname {1}"

Cause:

Action: Contact your customer support representative


PRKR-1052 "file name {0} is not of <cluster database name>.conf form"

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.


PRKR-1053 "invalid range {0} specified in node_list = {1}"

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.


PRKR-1054 "invalid parameter {0} specified in inst_oracle_sid = {1}"

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.


PRKR-1055 "invalid extra arguments {0} specified to {1} option"

Cause: Extra number of arguments provided to 'srvconfig'.

Action: See usage of 'srvconfig' for details.


PRKR-1056 "invalid registry entry {0} found, should be of form {1}"

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.


PRKR-1057 "environment variable does not exist"

Cause: Attempted to retrieve non existing environment variable.

Action: Set the environment variable.


Go to previous page Go to next page
Oracle
Copyright © 1998, 2002 Oracle Corporation.

All Rights Reserved.
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback