74 PRKP-01000 to PRKP-01088

PRKP-01000: Cannot retrive configuration for cluster database {0}: Cause: The cluster database configuration could not be retrieved from the repository. This could occur either because the database was never registered, or because the repository itself had not been created.; Action: Check if the database has been configured by printing a list of all cluster databases using 'srvctl config'. If the repostitory has not been created, use 'srvconfig -init' to create it.

PRKP-01001: Error starting database 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 and examine the database instance alert log.

PRKP-01002: Error stopping database 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 and examine the database instance alert log.

PRKP-01003: Startup operation partially failed: Cause: Some components of the cluster database could not be started.; Action: Check the accompanying error messages for details.

PRKP-01004: Shutdown operation partially failed: Cause: Some components of the cluster database reported errors while being stopped.; Action: Check the accompanying error messages for details.

PRKP-01005: Failed to start up cluster database {0}: Cause: The cluster database could not be started.; Action: Check the accompanying error messages for details.

PRKP-01006: Failed to shut down cluster database {0}: Cause: The cluster database reported errors while being shut down.; Action: Check the accompanying error messages for details.

PRKP-01007: Failed to start all the listeners associated with all the instances of cluster database {0}: Cause: Internal error.; Action: Contact your customer support representative.

PRKP-01008: Failed to start listeners associated with instance {0} on node {1}: Cause: Internal error.; Action: Contact your customer support representative.

PRKP-01009: 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 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-01010: 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-01011: 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-01012: Invalid environment variable {0} setting for cluster database {1}: Cause: The argument to the -t option was not of the form <name>=<value> or it contained 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-01013: {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 setenv'.

PRKP-01014: {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 setenv'.

PRKP-01015: {0}: undefined environment variable: Cause: The named environment variable is not defined; Action: Set a value for the named environment variable with 'srvctl setenv'.

PRKP-01084: Database "{0}" cannot have more than "{1}" services: Cause: Attempt to add a new service to database was rejected because database has already reached the maximum services limit.; Action: Retry after removing a service of this database via 'srvctl remove service' command, or contact Oracle Support Services.

PRKP-01088: Failed to retrieve configuration of cluster database {0}: Cause: Attempt to retrieve configuration of cluster database failed. This failure is most likely due to user incorrectly using a tool, such as SRVCTL, that is of different version than that of database's configuration.; Action: If error is due to user using SRVCTL that is of different version than than of the database's, then run SRVCTL tool from the ORACLE_HOME reported in the error message. Otherwise, contact Oracle support services.