126 PRGP-01001 to PRGP-01123
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- PRGP-01027: The specified wallet file '{0}' already exists.
-
Cause: An attempt to write a wallet file failed because the wallet file already exists.
- 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.
- 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).
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- PRGP-01047: failure to move Oracle Grid Infrastructure home.
-
Cause: An attempt to move the Oracle Grid Infrastructure home failed.
- 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.
- 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.
- 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.
- PRGP-01061: stop phase {0} does not exist
-
Cause: An attempt to locate the specified stop phase failed.
- 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.
- 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.
- 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.
- 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.
- PRGP-01073: Failed the patching operation for the Grid Infrastructure Management Repository.
-
Cause: The attempted patching operation for the Grid Infrastructure Management Repository failed.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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..
- PRGP-01091: failed to get the list of pluggable databases on node "{0}"
-
Cause: An attempt to retrieve the list of pluggable databases failed.
- 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.
- PRGP-01094: failed to update Exadata
-
Cause: An attempt to update Exadata failed.
- PRGP-01095: 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.
- 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.
- PRGP-01100: failed to execute datapatch
-
Cause: An attempt to execute datapatch failed.
- PRGP-01115: 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.
- PRGP-01116: failed to downgrade Oracle Grid Infrastructure on node "{0}"
-
Cause: An attempt to downgrade Oracle Grid Infrstrcuture on the indicated nodes failed.
- PRGP-01117: 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.
- PRGP-01118: 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.
- PRGP-01121: 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.
- PRGP-01122: 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.
- PRGP-01123: 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.