Cause: An attempt was made to create the Global Services Daemon (GSD) application while there is a running GSD application.
Action: Stop the running GSD, delete it and create the GSD application again using 'srvctl add nodeapps'
PRKA-2002: Listener already exists
Cause: An attempt was made to create a Listener application while there is a running Listener application.
Action: Stop the running Listener, delete it and create the Listener application again using 'srvctl add nodeapps'
Cause: An attempt was made to create a Virtual IP while there is a running Virtual IP application.
Action: Stop the running Virtual IP application, delete it and create the Virtual IP application using 'srvctl add nodeapps'
[@more@] PRKC—Cluster Command MessagesPRKC-1000 "No active nodes detected in the cluster"
Cause: The active node list of the cluster could not be retrieved. This can occur if the 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 'olsnodes' binary from your /bin and see if it prints the node list correctly.
PRKC-1001 "Error submitting commands in the buffer"
Cause: An internal error has occurred. This error is not exposed to the clients.
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: 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.
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. The possible causes are that one or more nodes failed during the operation, the destination directory did not have write permission for the user on one or more of the nodes, the source file did not exist, or the 'rcp/rsh/scp/ssh' command to one or more nodes failed on UNIX platforms.
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 can do 'rcp/rsh/scp/ssh' 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. The possible causes are that one or more nodes failed during the operation, the destination directory did not have write permission for the user on one or more of the nodes, the source file did not exist, or the 'rcp/rsh/scp/ssh' command to one or more nodes failed on UNIX platforms.
Action: See earlier error message 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. The possible causes are that one or more nodes failed during the operation, the destination directory did not have write permission for the user on one or more of the nodes, the source file did not exist, or the 'rcp/rsh/scp/ssh' command to one or more nodes failed on UNIX platforms.
Action: See earlier error message 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. The possible causes are that one or more nodes failed during the operation, the destination directory did not have write permission for the user on one or more of the nodes, the source file did not exist, or the 'rcp/rsh/scp/ssh' command to one or more nodes failed on UNIX platforms.
Action: See earlier error message 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: Check if all the nodes in cluster are up.
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: Check if all the nodes in cluster are up.
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: Check if all the nodes in cluster are up.
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 clusterware was not functioning properly or there is already a running GSD.
Action: Check the state of your clusterware by running 'lsnodes' from /bin. 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 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 clusterware cannot be contacted. This can occur because the clusterware was not functioning properly.
Action: Check the state of the clusterware.
PRKC-1022 "Could not get "node name" for node {0} in {1}"
Cause: The clusterware cannot be contacted. This can occur because the clusterware was not functioning properly.
Action: Check the state of the clusterware using 'olsnodes -n'.
PRKC-1023 "Invalid IP address format: {0}"
Cause: The given IP address is not valid.
Action: Check the format of the IP address.
PRKC-1024 "Invalid netmask: {0}"
Cause: Netmask passed was invalid.
Action: Check that it was a valid netmask.
PRKC-1025 "Failed to create a file in directory {0}"
Cause: Attempted file create operation(s) from the local node to one or more nodes in the cluster and one or multiple of those copy file operations failed. The possible causes are that one or more nodes failed during the operation, the destination directory did not have write permission for the user on one or more of the nodes, the source file did not exist, or the 'rcp/rsh/scp/ssh' command to one or more nodes failed on UNIX platforms.
Action: 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 can do 'rcp/rsh/scp/ssh' to all the nodes.
PRKC-1026 "Failed doing I/O to file {0}"
Cause: Attempted to write to or read from a file.
Action: Check the file exists. Check that the file has read/write permission for the user.
PRKC-1027 "Error checking existence of file {0} on {1}"
Cause: Attempted to check the existence of a file on a given node.
Action: Check that the user has execute permission on the given directory. On UNIX based platforms check that user can do 'rcp/rsh/scp/ssh' to the given node.
PRKC-1028 "Error checking write permission for directory {0} on {1}"
Cause: Attempted to check the write permission for the given directory on the given node.
Action: On UNIX based platforms check that user can do 'rcp/rsh/scp/ssh' to the given node.
PRKC-1029 "Failed to get modification time for file {0} on {1}"
Cause: Cannot do rsh/ssh to the given node.
Action: On UNIX based platforms check that user can do 'rcp/rsh/ssh/scp' to the given node.
PRKC-1030 "Error checking accessibility for node {0}"
Cause: Cannot do rsh/ssh to the given node.
Action: On UNIX based platforms check that user can do 'rcp/rsh/ssh/scp' to the given node.
PRKC-1031 "Error checking free space for {0} on {1}"
Cause: Cannot get free amount of available free space on a given node.
Action: On UNIX based platforms check that user can do 'rcp/rsh/ssh/scp' to the given node.
PRKC-1032 "Directory {0} does not exist"
Cause: Attempted an operation on a directory which does not exist.
Action: Make sure that the directory exists.
PRKC-1033 "Executable {0} does not exist"
Cause: Attempted an invoke the given executable.
Action: Make sure that the executable exists.
PRKC-1034 "No local node name found for host {0}"
Cause: Could not find the node name for a given host.
Action: Contact your local customer service representative.
PRKC-1035 "Node names for this cluster could not be retrieved"
Cause: Could not retrieve the node names for the Oracle clusterware. This could be caused if the Oracle clusterware was never installed on the system or if your Oracle Cluster Registry got corrupted.
Action: Install Oracle clusterware. Contact your local customer service representative
PRKC-1036 "CRS_HOME name passed to the method was null"
Cause: ORA_CRS_HOME retrieved from Oracle Cluster Registry was null.
Action: Contact your local customer service representative.
PRKC-1037 "Error removing files listed in {0} from node {1}"
Cause: Attempted to remove the given file from the given node.
Action: 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 can do 'rcp/rsh/scp/ssh' to all the nodes.
PRKC-1038 "Error copying files listed in {0} to node {1}"
Cause: Attempted file create operation(s) from the local node to one or more nodes in the cluster and one or multiple of those copy file operations failed. The possible causes are, one or more nodes failed during the operation, the destination directory did not have write permission for the user on one or more of the nodes, the source file did not exist, or the 'rcp/rsh/scp/ssh' command to one or more nodes failed on UNIX platforms.
Action: 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 can do 'rcp/rsh/scp/ssh' to all the nodes.
PRKC-1039 "Error creating directories listed in {0} on node {1}"
Cause: Attempted directory create operation(s) from the local node to one or more nodes in the cluster and one or multiple of those copy file operations failed. The possible causes are that one or more nodes failed during the operation, the destination directory did not have write permission for the user on one or more of the nodes, the source file did not exist, or the 'rcp/rsh/scp/ssh' command to one or more nodes failed on UNIX platforms.
Action: 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 can do 'rcp/rsh/scp/ssh' to all the nodes.
PRKC-1040 "Remote Shell is not known yet."}
Cause: Cannot determine the location of your remote shell command (rsh/ssh).
Action: Make sure you have rsh/ssh program installed on your system.
PRKC-1041 "Remote Copy command is not known yet."}
Cause: Cannot determine the location of your remote copy command (rcp/scp).
Action: Make sure you have rcp/scp program installed on your system.
PRKC-1042 "The Remote Shell {0} requested by client is not recognized "
Cause: Cannot determine the location of your remote shell command (rcp/scp).
Action: Make sure you have rsh/ssh program installed on your system.
PRKC-1043 "The Remote Copy command {0} requested by client is not recognized"
Cause: Cannot determine the location of your remote copy command (rcp/scp).
Action: Make sure you have rcp/scp program installed on your system.
PRKC-1044 "Failed to check remote command execution setup for node {0} using shells {1} and {2} "
Cause:
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/10685580/viewspace-1046405/，如需转载，请注明出处，否则将追究法律责任。
转载于:http://blog.itpub.net/10685580/viewspace-1046405/
1万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
