125 PRGT-1000 to PRGT-1049
- PRGT-1000: The remote authentication plug-in Java archive {0} was not found for option {1}.
-
Cause: An attempt to execute the 'zdmcli' command with the '-srcauth' archive (JAR) file was not found.
- PRGT-1007: invalid value "{0}" specified for -pauseafter option
-
Cause: Unsupported phase was specified for -pauseafter option.
- PRGT-1008: Oracle home location {0} does not contain program {1}
-
Cause: The current Oracle home directory did not contain the indicated utility.
- PRGT-1009: Attempt to retrieve Oracle base home from Oracle home {0} failed. Detailed error: \n {1}
-
Cause: An attempt to execute the 'oraclebasehome' command failed. See the accompanying error message for further details.
- PRGT-1012: invalid offset value "{0}" specified for -schedule option
-
Cause: Offset value specified was not in the expected format "+dd:mm:yy:hh:mm:ss"
- PRGT-1013: invalid offset value "{0}" specified for "{1}" field of -schedule option
-
Cause: The offset value did not contain a valid value for the indicated field of the offset value for the -schedule option.
- PRGT-1015: The value specified for the '-raconetimeout' option is invalid.
-
Cause: An attempt to move a database was rejected because the integer specified for '-raconetimeout' was not a value between 1 and 720.
- PRGT-1016: Option "{0}" not allowed for specified operation type {1}.
-
Cause: An attempt to run an rhpctl command was rejected because the indicated option was not allowed.
- PRGT-1017: The target Oracle Database home "{0}" is missing the patches for bug numbers "{1}" which are present in the source Oracle Database home "{2}".
-
Cause: An attempt to migrate a database with zero downtime was rejected because the destination Oracle Database home did not include the patches for the indicated bugs.
- PRGT-1018: Specified client name "{0}" contains invalid characters or is too long.
-
Cause: An attempt to add client was rejected because the indicated client name was not valid. Client names must not contain the characters $@"'>();*? and must be no longer than 128 characters.
- PRGT-1019: Specified working copy path "{0}" contains invalid characters or is too long.
-
Cause: An attempt to create or patch a working copy was rejected because the indicated working copy path was not valid. Working copy path must not contain the characters $@"'>();*? and must be no longer than 128 characters.
- PRGT-1020: Specified working copy Oracle base path "{0}" contains invalid characters or is too long.
-
Cause: An attempt to create or patch a working copy was rejected because the indicated working copy Oracle base path was not valid. Working copy Oracle base path must not contain the characters $@"'>();*? and must be no longer than 128 characters.
- PRGT-1021: The file {0} required by option '-autoupg' was not found.
-
Cause: An attempt to upgrade a database failed using the option -autoupg because the indicated Java Archive (JAR) file was not found.
- PRGT-1023: The command is submiited from the node '{0}' which is the same as the the nodes to be patched specified in the '-batches' option
-
Cause: An attempt to update Exadata nodes was rejected because the nodes specified for patching using the '-batches' option was the same as current node.
- PRGT-1024: failed to update exadata to cluster '{0}'
-
Cause: An attempt to update the exadata to the specified cluster failed. The accompanying error messages provide detailed failure information.
- PRGT-1025: Invalid list of nodes "{0}" specified for parameter {1}
-
Cause: The requested 'update exadata' operation was rejected because the indicated nodelist was not specified in the correct format.
- PRGT-1043: AutoUpgrade database checks have failed for database "{0}" from source home "{1}".
-
Cause: The preexecution evaluation check for the upgrade database command showed that some prerequisites were not met. The accompanying messages provide detailed failure information.
- PRGT-1047: Root user action requested for the operation "{0}" failed.
-
Cause: An attempt to add a root user action to a Rapid Home Provisioning (RHP) operation was rejected because the root user action was not supported for the specified RHP operation.
- PRGT-1048: The supported run scopes for adding a root user action are ONENODE, ALLNODES and AUTO.
-
Cause: An attempt to add a root user action to a Rapid Home Provisioning (RHP) operation was rejected because the root user action was not supported for the specified run scope.
- PRGT-1049: failed to configure flash recovery area for database "{0}" on source home "{1}"
-
Cause: An attempt to configure the flash recovery area failed. The accompanying messages provide detailed failure information.