Skip Headers
Oracle® Database Error Messages
11g Release 2 (11.2)

Part Number E17766-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

67 PRKU-01001 to PRKU-01039

PRKU-01001: Unexpected argument {0}.
Cause: The command line argument reported in above error message is not expected the by tool
Action: Refer to the tool's inline help display or to the product documentation of the command line tool for valid options and arguments, and then rerun the tool.
PRKU-01002: The option {0} is required.
Cause: The command line option reported by the above error message is a mandatory option required by the tool
Action: Review the tool's inline help display or to the product documentation of the command line tool for type of value required for this option. And then rerun the command specifying the above option in command line options.
PRKU-01003: The parameter {0} requires an argument.
Cause: The command line parameter reported in error message needs a value.
Action: Review the tool's inline help display or to the product documentation of the command line tool for type of value required for this option. And then rerun the command specifying the above option in command line options.
PRKU-01015: Oracle Clusterware is not properly stopped and de-configured on node "{0}". The files "{1}" exist as configured.
Cause: The files init.ohasd, or ocr.loc and/or directory scls_scr still exists on this node which makes the tool believe that the clusterware stack is not shutdown properly
Action: Run the Oracle clusterware deconfiguration utility to completely cleanup the configuration. The Clusterware deconfiguration tool is available in Oracle clusterware home and also on Oracle OTN (Technology Network) page.
PRKU-01016: Failed to stop Oracle Clusterware on nodes "{0}". Run the command "{1}" after fixing the problem.
Cause: The clusterware deconfiguration tool has failed to stop Oracle clusterware stack. The reason for failure can be found browsing through clusterware alert logs found in log/<hostname>/alert<hostname>.log directory under Oracle clusterware.
Action: You should browse through deamon logs in log/<hostname> under Oracle clustereware home and manually correct the problem to stop clusterware stack. And then rerun the command specified in above error message.
PRKU-01018: Run the following command as the root user on node "{0}".
Cause: The clusterware deconfiguration that is run as non-root user cannot automatically run the command specified in above message.
Action: You should login to another session as a privileged user and run the command specified in above message
PRKU-01019: Run the following command as administrator.
Cause: The clusterware deconfiguration which is run as non-root user cannot automatically run the command specified in above message.
Action: You should login to another session as a privileged user and run the command specified in above message
PRKU-01021: As the privileged user, Execute "{0}" on every node in this cluster except for this node, and then execute "{1}" on this node to remove the configuration of the Oracle Clusterware and to completely remove the Oracle software
Cause: This is the message reported by Oracle clusterware deconfiguration tool when it is run in non-interactive (or silent) mode.
Action: Execute the identified scripts as described. Deconfiguring Oracle Clusterware in silent mode requires one set of operations on all nodes but the last followed by a special set of operations on the last node.
PRKU-01023: Oracle Clusterware is not stopped and de-configured on node "{0}" due to error "{1}"
Cause: The tool failed to deconfigure Oracle clusterware stack on the node because of errors reported in the above message
Action: You should review the error messages reported in above message to perform corrective actions and then rerun the tool
PRKU-01024: The stopping and de-configuring of Oracle Clusterware failed on some nodes. Fix the problem and rerun this tool to completely remove the Oracle Clusterware configuration and the software
Cause: This is a message reported by the tool to inform you that the Oracle clusterware deconfiguration did not happen on some of the nodes in the cluster.
Action: You should review the error messages reported by the tool for failing to deconfigure clusterware stack on each node, perform corrective actions after reviewing the error messages, and rerun the tool to completely deconfigure Oracle clusterware stack
PRKU-01025: You must delete or downgrade Clusterware-managed Oracle databases and de-install Clusterware-managed Oracle homes before attempting to remove the Oracle Clusterware home.
Cause: An attempt was made to deconfigure the Oracle Clusterware when one or more Clusterware-managed Oracle databases still exist.
Action: Run the Oracle Clusterware deconfiguration tool from Clusterware-managed Oracle homes to delete, deconfigure or downgrade Oracle database and then run the same tool from Oracle Clusterware home to deconfigure Clusterware.
PRKU-01029: The node "{0}" is currently not responding.
Cause: The host reported in the above message may have rebooted or hung
Action: Login to the host if possible and review system logs, correct the problem
PRKU-01035: The stopping and de-configuring of Oracle Restart failed. Fix the problem and rerun this tool to completely remove the Oracle Restart configuration and the software
Cause: The Oracle Restart stack couldn't be stopped cleanly before de-configuring.
Action: Review the error messages reported by the tool for failing to deconfigure Oracle Restart stack, perform corrective actions after reviewing the error messages, and rerun the tool to completely deconfigure Oracle Restart stack.
PRKU-01036: The deinstall tool failed to create the script file "{0}" that needs to be run in silent mode due to error "{1}"
Cause: The tool failed to create silent mode script file because of errors reported in the above message.
Action: You should review the error messages reported in above message to perform corrective actions and then rerun the tool.
PRKU-01037: As the privileged user, execute "{0}" and then execute "{1}" on this node to remove the configuration of the Oracle Restart and to completely remove the Oracle software
Cause: This is the message reported by Oracle Restart deconfiguration tool when it is run in non-interactive (or silent) mode.
Action: Execute the identified scripts as described.
PRKU-01039: Can't deconfigure Oracle Restart before removing or downgrading managed Oracle databases.
Cause: A request to deconfigure Oracle Restart found one or more managed Oracle database homes, so the request was rejected.
Action: Run the Oracle deconfiguration tool from Oracle database homes to delete, deconfigure or downgrade Oracle database and then run the same tool from Oracle Restart home to deconfigure the Oracle Restart stack.