PRGP-01001 to PRGP-01142

126 PRGP-01001 to PRGP-01142

PRGP-01001: There is no cluster being moved to destination path {0}.: Cause: An attempt to resume or abort moving a cluster to the specified destination path was rejected because a move operation had not been initiated for the specified destination path.; Action: None
PRGP-01002: There are no databases being moved to destination path {0}.: Cause: An attempt to resume or abort moving databases from the specified destination path was rejected because a move operation had not been specified for the indicated destination path.; Action: None
PRGP-01003: No databases are being moved from Oracle home "{0}".: Cause: An attempt to patch Oracle databases was rejected because the '-excludedblist' option resulted in no database being identified as a database that needed to be moved from the specified Oracle home.; Action: Retry the operation, ensuring that the input for option '-excludedblist' is not excluding all databases in the specified Oracle home from being patched.
PRGP-01004: missing information to move databases from or to Oracle home "{0}" on cluster "{1}": Cause: An attempt to patch Oracle databases was rejected because the specified Oracle home is involved in parallel 'rhpctl move database' operations and the user did not specify sufficient information to uniquely identify a specific operation.; Action: Retry the operation, ensuring that the input for option '-dbname' or option '-excludedblist' uniquely identifies a specific operation.
PRGP-01005: cannot specify databases "{0}" along with databases "{1}": Cause: An attempt to patch Oracle databases was rejected because the input for option '-dbname' was incorrect.; Action: Retry the operation, ensuring that the input for option '-dbname' does not include the offending values.
PRGP-01006: Value for option '-excludedblist' matched multiple 'rhpctl move database' operations in progress: "{0}": Cause: An attempt to patch Oracle databases was rejected because the input for option '-excludedblist' was incorrect.; Action: Retry the operation, ensuring that the input for option '-excludedblist' identifies a specific 'rhpctl move database' operation among the indicated operations in progress.
PRGP-01013: The specified source home "{0}" is not an active Cluster Ready Services (CRS) home.: Cause: An attempt to move or upgrade Oracle Grid Infrastructure home was rejected because the specified source home was not an active Cluster Ready Services (CRS) home.; Action: Retry the operation specifying an active, configured Oracle Grid Infrastructure home as the source.
PRGP-01014: failed to move the Oracle Grid Infrastructure home because the source and the destination home cannot be the same: Cause: An attempt to move the Oracle Grid Infrastructure home was rejected because the specified source and destination homes were the same.; Action: Specify different source and destination homes and retry the operation.
PRGP-01015: Neither GNS server nor GNS client is configured on this RHP server cluster.: Cause: An 'rhpctl add workingcopy' command was rejected because neither the Grid Naming Service (GNS) server nor GNS client was configured on the Rapid Home Provisioning (RHP) server cluster.; Action: Configure either the GNS server or the GNS client using the command 'srvctl add gns' in the RHP server cluster, and retry the command.
PRGP-01016: Zero impact patching is supported only for STANDALONE cluster, whereas the detected cluster is {0}.: Cause: An attempt to revert or move the Oracle Grid Infrastructure home was rejected because zero impact patching is not supported for the specified cluster class.; Action: Retry the revert or move operation without specifying the '-tgip' option.
PRGP-01017: Specifying more than one node for zero impact patching is unsupported.: Cause: An attempt to revert or move the Oracle Grid Infrastructure home was rejected because zero impact patching is supported one node at a time and more than one node was specified for the '-batch' option.; Action: Retry the command specifying only one node for the '-batch' option or without specifying the '-tgip' option.
PRGP-01018: Zero impact patching is not supported on Oracle Restart.: Cause: An attempt to revert or move the Oracle Grid Infrastructure home was rejected because zero impact patching is not supported on Oracle Restart.; Action: Retry the revert or move operation without specifying the '-tgip' option.
PRGP-01019: Zero impact patching is supported only on Oracle Linux platform, whereas the detected platform is {0}.: Cause: An attempt to revert or move the Oracle Grid Infrastructure home was rejected because zero impact patching is not supported for the indicated platform.; Action: Retry the revert or move operation without specifying the '-tgip' option.
PRGP-01025: No clients were found in the wallet file.: Cause: An attempt to import client credentials from a wallet file was rejected because the wallet file did not have client credentials.; Action: Retry the import operation with a valid wallet file that contains client credentials.
PRGP-01026: The specified wallet file '{0}' does not exist.: Cause: An attempt to read from a wallet file failed because the wallet file did not exist.; Action: Retry the import operation with a valid wallet file that contains client credentials.
PRGP-01027: The specified wallet file '{0}' already exists.: Cause: An attempt to write a wallet file failed because the wallet file already exists.; Action: Retry the export operation with a different wallet file name.
PRGP-01028: An invalid client name '{0}' was found while reading the wallet file: Cause: An attempt to read clients from a wallet file failed because a client name was invalid.; Action: Retry the operation with a different wallet file.
PRGP-01029: Delete working copy partially failed.: Cause: An attempt to delete a working copy partially failed as there was a failure to connect to Rapid Home Provisioning Client (RHPC). Only the working copy metadata was deleted from Rapid Home Provisioning Server (RHPS).; Action: Manually remove the working copy storage data from the Rapid Home Provisioning Client (RHPC) with operating system commands.
PRGP-01031: Specified first batch '{0}' contains multiple nodes.: Cause: An attempt to perform a patching operation in batch mode was rejected because specified first batch contained multiple nodes.; Action: Retry the operation after ensuring that first batch contains only one node.
PRGP-01032: The specified destination home '{0}' is not a software only home.: Cause: An attempt to upgrade or move the Oracle Grid Infrastructure (GI) was rejected because the destination home was not a software only home.; Action: Retry the move or upgrade command specifying a different destination home that is software only.
PRGP-01033: Oracle RAC database provisioning in Standard Edition home is not supported.: Cause: The target home for the Oracle RAC database provisioning is installed as Standard Edition. This only applies to version 19c and later.; Action: Select a valid Enterprise Edition home for the provisioning of Oracle RAC database.
PRGP-01034: Cluster Ready Services (CRS) is not running on node "{0}" after patch manager execution.: Cause: Cluster Ready Services (CRS) was not running on the indicated node.; Action: Start the Cluster Ready Services (CRS) on the indicated node.
PRGP-01036: failed to execute patch manager on node '{0}'.: Cause: An attempt to execute patch manager on indicated node failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address issues described and retry.
PRGP-01037: failed to disable resource use on node '{0}': Cause: An attempt to disable all CRSD resources failed on the specified node. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGP-01038: failed to enable resource use on node '{0}': Cause: An attempt to enable all CRSD resources failed on the specified node. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGP-01043: cannot move the Oracle Grid Infrastructure home for incomplete exadata image "{0}": Cause: An attempt to move the Oracle Grid Infrastructure for exadata image was rejected because creation of the specified exadata image was not complete.; Action: Specify a complete exadata image for move opration.
PRGP-01044: failure to move Oracle Grid Infrastructure home Option because exadata image "{0}" base image type is not EXAPATCHSOFTWARE: Cause: An attempt to move the Oracle Grid Infrastructure home was rejected because the specified exadata image base image type is not EXAPATCHSOFTWARE; Action: Specify a complete image of base image type EXAPATCHSOFTWARE.
PRGP-01047: failure to move Oracle Grid Infrastructure home.: Cause: An attempt to move the Oracle Grid Infrastructure home failed.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGP-01051: User '{0}' specified to be the owner of a GIMR working copy is not the Grid Infrastructure user '{1}'.: Cause: The user specified as the owner of a Grid Infrastructure Management Repository (GIMR) working copy was not the Grid Infrastructure user.; Action: Specify the Grid Infrastructure user as the owner of the working copy or submit the command without the flag indicating that the working copy is for a GIMR home.
PRGP-01052: Working copy '{0}' is not a GIMR working copy.: Cause: A Grid Infrastructure Management Repository (GIMR) only operation was attemped on a non-GIMR working copy.; Action: Specify a GIMR working copy and retry the command.
PRGP-01053: Gold image path '{0}' does not exist or is empty on node '{1}'.: Cause: The gold image path did not exist or was empty in at least one of the cluster nodes.; Action: Manually create the gold image path and unzip the contents of the gold image under it.
PRGP-01061: stop phase {0} does not exist: Cause: An attempt to locate the specified stop phase failed.; Action: Ensure that the stop phase exists in the workflow. Use -listphases option to list the phases involved.
PRGP-01064: the specified -pauseafter phase {0} is beyond -stopafter phase {1}: Cause: Pause phase can't be a phase after the last phase of the job.; Action: Ensure that the pause phase exists in the workflow. Use -listphases option to list the phases involved.
PRGP-01068: User "{0}" failed to add Grid Infrastructure Management Repository (GIMR) database to the working copy in the cluster "{1}".: Cause: The indicated user could not add Grid Infrastructure Management Repository (GIMR) database to the working copy because the working copy was not owned by the Grid Infrastructure user of the indicated cluster.; Action: Create the working copy so that it is owned by the Grid Infrastructure user of the indicated cluster.
PRGP-01070: failed to update exadata on the Rapid Home Provisoning client "{0}": Cause: An attempt to update exadata on the node where Rapid Home Provisoning client was running failed because 'exadata update' actions either failed with an error or timed out.; Action: Examine the accompanying error messages and retry the command after addressing the cause for the error.
PRGP-01071: Option '-continue' is supported only for 'update exadata' batch operations.: Cause: An attempt to update exadata was rejected because the '-continue' option was specified, but the update exadata operation requested was not a batch operation.; Action: Resume the move operation by reissuing the command with the options that were originally specified.
PRGP-01073: Failed the patching operation for the Grid Infrastructure Management Repository.: Cause: The attempted patching operation for the Grid Infrastructure Management Repository failed.; Action: Examine the accompanying error messages and retry the operation after addressing the cause for the error.
PRGP-01075: Unexpected option '{0}' specified for moving the Grid Infrastructure Management Repository between Oracle homes.: Cause: The attempted 'move database' operation was rejected because the indicated option was not supported.; Action: Retry the command without the indicated option.
PRGP-01076: Option '{0}' not specified for moving the Grid Infrastructure Management Repository.: Cause: The attempted 'move database' operation was rejected because the indicated option was not specified.; Action: Specify the indicated option and retry the command.
PRGP-01077: Flash Recovery Area is not configured in the database.: Cause: AutoUpgrade relied on a Guarantee Restore Point (GRP) because the rollback strategy required the database to have the flash recovery area configured.; Action: Execute one of the following: - Manually configure flash recovery area in the database and enable the archive mode of the database and retry the command. - Add '-fra <db_recovery_file_dest>' option and retry the command to configure flash recovery area as part of operation. This restarts all of the database instances. - Add '-grp NO' option and retry the command to disable the AutoUpgrade rollback mechanism. If you select this option, then both database backup and database restoration must be performed manually by the DBA.
PRGP-01078: Oracle Home "{0}"is not a Standard Edition home.: Cause: The target home for the Oracle Standard Edition High Availability database provisioning is not installed as Standard Edition. This only applies to version 19.7 and later.; Action: Select a valid Standard Edition home for the provisioning of Oracle SEHA database.
PRGP-01079: Image version "{0}" is lower than 19.7.: Cause: The target Standard Edition image is on Database Release lower than 19.7. Standard Edition High Availability is only supported from Database Release 19.7 and later.; Action: Select a valid Standard Edition Database image for the provisioning of Oracle Standard Edition High Availability database.
PRGP-01081: Oracle Grid Infrastructure on node(s) "{0}" is not running from Oracle home "{1}": Cause: Failed to force completion of 'move gihome' command as Oracle Grid Infrastructure was not running from specified Oracle home.; Action: Ensure that the Oracle Grid Infrastructure is running from the specified Oracle home on all nodes and resubmit the command.
PRGP-01083: failed to copy User action files\n{0}: Cause: The user action file copy operation failed either because the file system was full or the destination directory did not have write permissions for the specified user.; Action: Retry the command making sure that the file system is not full and the destination directory has requisite permissions.
PRGP-01084: failed to suspend the job "{0}" because it is not executing. Current job status is: "{1}": Cause: An attempt to suspend the specified job was rejected because the specified job was not in the EXECUTING state.; Action: Retry the operation, specifying a job in the EXECUTING state.
PRGP-01085: suspend job operation allowed only for Zero Downtime Migration (ZDM) jobs: Cause: An attempt to suspend the specified job was rejected because suspend job operation is allowed only on Zero Downtime Migration (ZDM) jobs.; Action: Retry the operation on Zero Downtime Migration (ZDM) jobs.
PRGP-01086: User "{0}" lacks the authority to abort the scheduled job {1}.: Cause: An attempt to abort a scheduled job was rejected because the indicated user did not have the required authorization.; Action: Retry the operation after requesting the authorization from the administrator or retry the operation from a user ID that has the required authorization.
PRGP-01087: User "{0}" lacks the authority to suspend the job {1}.: Cause: An attempt to suspend a scheduled job was rejected because the indicated user did not have the required authorization.; Action: Retry the operation after requesting the authorization from the administrator or retry the operation from a user ID that has the required authorization.
PRGP-01088: User "{0}" lacks the authority to resume the job {1}.: Cause: An attempt to resume a job was rejected because the indicated user did not have the required authorization.; Action: Retry the operation after requesting the authorization from the administrator or retry the operation from a user ID that has the required authorization.
PRGP-01089: failed to abort the job "{0}" because it is not in abortable state. Current job status is: "{1}": Cause: An attempt to abort the specified job was rejected because the specified job was not abortable..; Action: Retry the operation, specifying a job which is in abortable state.
PRGP-01091: failed to get the list of pluggable databases on node "{0}": Cause: An attempt to retrieve the list of pluggable databases failed.; Action: Examine the accompanying error messages.
PRGP-01092: failed to find {0} available ports in the port range {1}-{2}: Cause: Failed to find the required number of available ports in the port range to copy remote files.; Action: Ensure that the indicated number of required ports are available in the indicated port range. Alternatively, change the port range using srvctl modify rhpserver -port_range x-y.
PRGP-01093: failed to downgrade Oracle Grid Infrastructure on node "{0}": Cause: An attempt to downgrade Oracle Grid Infrastructure on the indicated nodes failed.; Action: Examine the accompanying error messages, resolve the issues and retry the command.
PRGP-01094: no Oracle Grid Infrastructure upgrade in progress to working copy "{0}": Cause: An attempt to downgrade Oracle Grid Infrastructure on the indicated working copy failed.; Action: Ensure that the right working copy name is used to perform Oracle Grid Infrastructure downgrade.
PRGP-01095: Source working copy is not provisioned on the specified nodes "{0}" in the batches argument.: Cause: An attempt to perform a patching operation in batch mode was rejected because the specified node was not part of the nodes on which the source working copy was provisioned.; Action: Reissue the command with a node on which the source working copy was provisioned or specify a source working copy that exists on the specified node."
PRGP-01097: failed to update Exadata: Cause: An attempt to update Exadata failed.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGP-01098: The -iso_repo option value "{0}" is a file path.: Cause: The requested operation failed because the -iso_repo option value was a file path.; Action: Only specify the ISO image name and retry the command.
PRGP-01099: failed to patch the database node "{0}" where RHPS/RHPC container is running: Cause: An attempt to update Exadata nodes was rejected because the patch manager utility could not be launched from the indicated node which was listed in patch manager server list file.; Action: Retry the command specifying the '-batches' option with non-container node.
PRGP-01100: Site with cluster name "{0}" already exists for an another cluster.: Cause: An attempt to add a working copy was rejected because the site with the indicated cluster name already exists for an another cluster.; Action: Specify '-clusternamealias alias' to add working copy.
PRGP-01101: failed to execute datapatch: Cause: An attempt to execute datapatch failed.; Action: Examine the accompanying error messages, address the issues described, and retry the operation.
PRGP-01102: The Rapid Home Provisioning Server (RHPS) version {0} does not match with Rapid Home Provisioning Client (RHPC) version {1}.: Cause: An attempt to modify the RHPC failed because the RHPS and RHPC versions are different.; Action: Ensure that the RHPS and RHPC versions are the same for the modify client operation.
PRGP-01103: The Rapid Home Provisioning Client (RHPC) "{0}" has only one node: Cause: An attempt to modify the RHPC failed because the RHPC has only one node.; Action: Ensure that the RHPC contains minimum of two nodes for the modify client operation.
PRGP-01110: Image "{0}" is not deployed to the cluster "{1}".: Cause: An attempt to update the exadata was rejected because the specified exadata image was not deployed to the specified cluster.; Action: Retry the command after executing the command 'rhpctl deploy image' to deploy the specified image on the specified cluster.
PRGP-01111: cannot deploy image "{0}" because creation of this image was not complete: Cause: An attempt to deploy an image was rejected because creation of the specified image was not complete.; Action: Specify a complete image to deploy.
PRGP-01112: Image "{0}" is already deployed to the cluster "{1}" at location "{2}".: Cause: An attempt to deploy the Oracle Exadata image was rejected because the specified image was already deployed to the specified cluster.; Action: Retry the operation after ensuring that the Oracle Exadata image is not yet deployed or specify a different image to deploy.
PRGP-01113: failed to relocate one or more database services: Cause: An error occurred while attempting to relocate the services. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGP-01114: failed to stop one or more database services: Cause: An error occurred while attempting to stop the services. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGP-01115: failed to start one or more database services: Cause: An error occurred while attempting to start the services. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGP-01116: failed to stop one or more databases: Cause: An error occurred while attempting to stop the databases. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGP-01117: failed to start one or more databases: Cause: An error occurred while attempting to start the databases. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGP-01118: The specified patch manager location "{0}" does not contain 'patchmgr' executable on nodes ''{1}''.: Cause: An attempt to update the Exadata was rejected because 'patchmgr' executable did not exist in the specified patch manager location on the specified nodes.; Action: Specify the correct patch manager location, and then retry the operation.
PRGP-01119: The specified ISO file "{0}" does not exist on the deployed path "{1}" on nodes ''{2}'': Cause: An attempt to update the Exadata was rejected because the specified 'iso_repo' file did not exist in the deployed path on specified nodes.; Action: Specify the correct iso repository, and then retry the operation.
PRGP-01120: The specified path "{0}" for importing Exadata image is empty: Cause: An attempt to import image failed because specified image path directory is empty.; Action: Retry the command ensuring that the specified directory contains Exadata software with ISO image.
PRGP-01124: An attempt to get the target cluster name failed: Cause: Remote execution of the command failed.; Action: Examine the accompanying error messages for details.
PRGP-01125: An attempt to fetch the remote source home info failed: Cause: Remote execution of the command failed.; Action: Examine the accompanying error messages for details.
PRGP-01126: relocate of database services failed: Cause: Remote execution of the command failed.; Action: Examine the accompanying error messages for details.
PRGP-01127: Stop of database services failed: Cause: Remote execution of the command failed.; Action: Examine the accompanying error messages for details.
PRGP-01128: An attempt to fetch the home information for home path "{0}" failed with the error \n"{1}": Cause: Remote execution of the command failed.; Action: Examine the accompanying error messages for details.
PRGP-01129: retry attempts of command "{0}" failed even after retrying "{1}" times with error \n"{2}": Cause: Remote execution of the command failed.; Action: Examine the accompanying error messages for details.
PRGP-01130: failure detected while unregistering peer server "{0}". Perform unregister on peer server as well to complete the cleanup.: Cause: An attempt to unregister peer server encountered a failure.; Action: Retry the command on peer RHPS to complete the cleanup.
PRGP-01131: checksum of the source zip file "{0}" and the target zip file"{1}" do not match: Cause: The zip file was corrupted while transferring from the source node to the target node; Action: Retry the command.
PRGP-01136: The database rollback cannot be completed in a rolling manner because the source home at "{0}" contains more restricted RAC rolling patches compared to the target home at "{1}".: Cause: The restricted RAC rolling patches enabled in the source home are more than in the target home and therefore cannot be rolled back in a rolling manner.; Action: Reissue the command specifying the '-nonrolling' option to complete the rollback in a non-rolling manner.
PRGP-01137: An error occurred when moving the database to Oracle home location "{1}".: Cause: An attempt to move the database to the new Oracle home failed.; Action: Examine the accompanying error messages.
PRGP-01138: Enabling restricted RAC rolling patches on database "{0}" failed.: Cause: Enabling restricted RAC rolling patches on specified database failed because the execution of the SQL statement 'ALTER SYSTEM ENABLE_ALL PATCH' to enable restricted RAC rolling patches failed.; Action: Retry the SQL statement manually.
PRGP-01139: Warning: The maintenance database plan for one or more databases could not be updated, as per the following details:: Cause: An error occurred while attempting to update the maintenance database plan data. The accompanying messages provide detailed failure information.; Action: Examine the accompanying error messages for details.
PRGP-01140: failed to relocate one or more database services: Cause: An error occurred while attempting to relocate the services. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages and resolve the indicated problems.
PRGP-01142: An error occurred when an attempt was made to fetch the site name for node "{0}".: Cause: An attempt to get the site name for the specified node failed.; Action: Examine the accompanying error messages. Address the reported issues and retry the operation.