129 PRGT-01000 to PRGT-01099
- PRGT-01000: 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-01007: invalid value "{0}" specified for -pauseafter option
-
Cause: Unsupported phase was specified for -pauseafter option.
- PRGT-01008: Oracle home location {0} does not contain program {1}
-
Cause: The current Oracle home directory did not contain the indicated utility.
- PRGT-01009: 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-01012: 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-01013: 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-01015: 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-01016: 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-01017: The target Oracle Database home "{0}" is missing the patches for bug numbers "{1}" which are present in the source Oracle Database home "{2}". The target database has a lower patch level compared to the source database patch level. Apply the indicated patches to the target database and retry the migration.
-
Cause: An attempt to migrate a database with zero downtime was rejected because the target Oracle Database home did not include the patches for the indicated bugs.
- PRGT-01018: 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-01019: 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-01020: 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-01021: 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-01022: Invalid bug number list "{0}" was specified.
-
Cause: Bug numbers were specified in an incorrect format.
- PRGT-01023: The option value provided for "{0}" contains one or more of the following invalid characters "{1}".
-
Cause: An invalid value was provided for a given option.
- PRGT-01024: invalid value "{0}" specified for incremental interval option
-
Cause: Unsupported value was specified for the incremental interval option.
- PRGT-01025: GIMR upgrade failed while executing mgmtua.\n{0}
-
Cause: An attempt to execute the management database upgrade assistant (mgmtua) to upgrade the Grid Infrastructure Management Repository (GIMR) failed.
- PRGT-01026: password in the wallet {0} is missing
-
Cause: An attempt to read the password in the wallet file failed because the password was not found.
- PRGT-01027: -jobtype option cannot be used with any other options except -jobid
-
Cause: The option jobtype was used with incompatible options.
- PRGT-01028: 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-01029: 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-01030: invalid value "{0}" specified for -stopafter option
-
Cause: Unsupported phase was specified for -stopafter option.
- PRGT-01031: failed to import an image from a remote zip file
-
Cause: An attempt to use the -zip option to import from a remote location using the -targetnode or -client option failed. The -zip option is supported only on the Rapid Home Provisioning (RHP) server cluster.
- PRGT-01032: failed to open the wallet file "{0}"
-
Cause: An attempt to read the wallet file failed.
- PRGT-01033: failed to deserialize JSON content in file "{0}"
-
Cause: An attempt to deserialize JavaScript Object Notation (JSON) content in the specified file failed.
- PRGT-01038: ZDM service is not running.
-
Cause: ZDM service was not running.
- PRGT-01039: identity file "{0}" specified in param "{1}" not found on node "{2}"
-
Cause: The exepcted identity file not found in specified path
- PRGT-01040: Invalid command specified: {0}
-
Cause: The command keyword specified on the command line was not recognized.
- PRGT-01041: Command "{0}" is not supported for object "{1}"
-
Cause: An unsupported command and object combination was specified.
- PRGT-01042: The '-datafileDestination' option was not specified.
-
Cause: An attempt to add a Standard Edition High Availability database was rejected because the data file destination was not specified.
- PRGT-01043: An unrecognized property name "{0}" was found in the response file "{1}".
-
Cause: A request was rejected because the response file contained a property name that was not recognized.
- PRGT-01044: Invalid edition "{0}".
-
Cause: The edition type specified was not valid.
- PRGT-01045: 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-01046: The '-datafileDestination' location specified "{0}" was not ASM disk group name or ACFS file system when '-dbtype' was SINGLE (SEHA).
-
Cause: An attempt to add a Standard Edition High Availability database was rejected because the data file destination was not an Oracle Automatic Storage Management disk nor an ASM Cluster File System path.
- PRGT-01047: 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 indicated RHP operation.
- PRGT-01048: Option "{0}" need to specify {ONENODE | ALLNODES | AUTO} supported runscope
-
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 indicated RHP operation.
- PRGT-01049: 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.
- PRGT-01050: The file specified for the '-actionscript' option "{0}" is not supported.
-
Cause: An attempt to add a 'useraction' was rejected because the file specified for the '-actionscript' option was not supported.
- PRGT-01051: Identity file "{0}" specified in parameter "{1}" is not readable.
-
Cause: The specified identity file was not readable.
- PRGT-01052: Identity file "{0}" specified in parameter "{1}" is not a file.
-
Cause: The specified identity file was not a valid file.
- PRGT-01053: The '-gimrwc' option missing for self upgrade of Rapid Home Provisioning Server
-
Cause: An attempt to upgrade Rapid Home Provisioning Server was rejected as '-gimrwc' option was not specified.
- PRGT-01055: failed to establish connection with specified bastion server {0}
-
Cause: An attempt to migrate a database with zero downtime failed to establish connection with the specified bastion server.
- PRGT-01056: invalid value "{0}" specified for parameter {1}
-
Cause: An attempt to migrate the database was rejected because the indicated parameter value specified was not valid.
- PRGT-01058: 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-01060: Option "{0}" is not allowed.
-
Cause: An attempt to migrate a database with zero downtime was rejected because the specified option was not allowed.
- PRGT-01061: Database type {1} is not supported with environment {0}.
-
Cause: An attempt to migrate a database with zero downtime was rejected because the provided database type is not supported with the provided environment type.
- PRGT-01063: missing Amazon S3 bucket details for selected data transfer medium AMAZONS3
-
Cause: An attempt to migrate a database with zero downtime was rejected because DUMPTRANSFERDETAILS_S3BUCKET parameters were missing for the selected data transfer medium AMAZONS3.
- PRGT-01064: missing Amazon S3 bucket name for selected data transfer medium AMAZONS3
-
Cause: An attempt to migrate a database with zero downtime was rejected because DUMPTRANSFERDETAILS_S3BUCKET_NAME was missing for the selected data transfer medium AMAZONS3.
- PRGT-01065: missing Amazon S3 bucket region for selected data transfer medium AMAZONS3
-
Cause: An attempt to migrate a database with zero downtime was rejected because DUMPTRANSFERDETAILS_S3BUCKET_REGION was missing for the selected data transfer medium AMAZONS3.
- PRGT-01066: missing Amazon S3 bucket access key for selected data transfer medium AMAZONS3
-
Cause: An attempt to migrate a database with zero downtime was rejected because DUMPTRANSFERDETAILS_S3BUCKET_ACCESSKEY was missing for the selected data transfer medium AMAZONS3.
- PRGT-01067: missing SOURCEDATABASE_ENVIRONMENT parameters for selected data transfer medium AMAZONS3
-
Cause: An attempt to migrate a database with zero downtime was rejected because SOURCEDATABASE_ENVIRONMENT parameters were missing for the selected data transfer medium AMAZONS3.
- PRGT-01068: invalid data transfer medium {0} specified for environment {1}
-
Cause: An attempt to migrate a database with zero downtime was rejected because an invalid data transfer medium was specified for the selected environment.
- PRGT-01069: DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_PATH is not supported with data transfer medium {0}.
-
Cause: An attempt to migrate a database with zero downtime was rejected because DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_PATH was not supported with the selected data transfer medium.
- PRGT-01070: invalid proxy details specified for parameters {0}
-
Cause: An attempt to migrate a database with zero downtime was rejected because the proxy details were invalid.
- PRGT-01071: sourcenode argument is not supported for AMAZON environment
-
Cause: An attempt to migrate a database with zero downtime was rejected because the -sourcenode argument was not supported for the AMAZON environment.
- PRGT-01072: object name "{0}" selection not allowed for object type {1}.
-
Cause: An attempt to migrate a database with zero downtime was rejected because the specified option was not allowed.
- PRGT-01073: mutually exclusive INCLUDEOBJECT and EXCLUDEOBJECT parameters were both specified
-
Cause: An attempt to migrate a database with zero downtime was rejected because the mutually exclusive parameters INCLUDEOBJECT and EXCLUDEOBJECT were specified.
- PRGT-01074: mutually exclusive object type TABLE INCLUDEOBJECT and EXCLUDEOBJECT parameters were both specified
-
Cause: An attempt to migrate a database with zero downtime was rejected because the mutually exclusive parameters INCLUDEOBJECT and EXCLUDEOBJECT were specified.
- PRGT-01075: include owners "{0}" with wildcard specified for migration
-
Cause: An attempt to migrate a database with zero downtime was rejected because the specified option incldued unsupported wildcard characters.
- PRGT-01076: more than one object type included in addition to include of object type {0}
-
Cause: An attempt to migrate a database with zero downtime was rejected because the specified option includes entire schema and one or more object type in addition.
- PRGT-01077: include object type {0} specified for job mode FULL
-
Cause: An attempt to migrate a database with zero downtime was rejected because the specified option incldued indicated object type for job mode FULL.
- PRGT-01078: multiple owners {0} specified for migration
-
Cause: An attempt to migrate a database with zero downtime was rejected because the specified option was not valid as it included more than one owners for migration.
- PRGT-01079: duplicate include object type {0} specified
-
Cause: An attempt to migrate a database with zero downtime was rejected because the specified option was not valid as same object type was included more than once.
- PRGT-01080: all objects of type {0} excluded for owner {1}
-
Cause: An attempt to migrate a database with zero downtime was rejected because the specified exclude option omits all objects of specified type and is not supported.
- PRGT-01081: invalid value {0} specified for EXCLUDEOBJECTS or INCLUDEOBJECTS parameters
-
Cause: An attempt to migrate a database with zero downtime was rejected because the specified wildcard is not supported.
- PRGT-01083: Invalid option '-eval' specified with '-rollback' or '-backup'
-
Cause: An invalid combination of options was specified for the 'update exadata -dbnodes' command. The '-eval' option cannot be specified with '-rollback' or '-backup'.
- PRGT-01084: invalid value {0} specified for job tag parameter
-
Cause: Unsupported tag value was specified for -jobtag option.
- PRGT-01085: GoldenGate administrator user name for source database was not specified.
-
Cause: An attempt to migrate a database with zero downtime was rejected because parameter SOURCEDATABASE_GGADMINUSERNAME was not specified for the selected ONLINE_LOGICAL migration method.
- PRGT-01086: GoldenGate administrator user name for target database was not specified.
-
Cause: An attempt to migrate a database with zero downtime was rejected because parameter TARGETDATABASE_GGADMINUSERNAME was not specified for the selected ONLINE_LOGICAL migration method.
- PRGT-01087: Path "{0}" does not exist.
-
Cause: An attempt to locate the specified path failed.
- PRGT-01088: Path "{0}" is not a directory.
-
Cause: The specified path was not a directory.
- PRGT-01089: Directory "{0}" is not empty.
-
Cause: The specified directory was not empty.
- PRGT-01090: Directory "{0}" is empty.
-
Cause: The specified directory was empty.
- PRGT-01091: schema batches selected for job mode {0}
-
Cause: An attempt to migrate a database with zero downtime was rejected because the specified option was not allowed.
- PRGT-01092: mutually exclusive DATAPUMPSETTINGS_SCHEMABATCH and DATAPUMPSETTINGS_SCHEMABATCHCOUNT parameters were both specified
-
Cause: An attempt to migrate a database with zero downtime was rejected because the mutually exclusive parameters DATAPUMPSETTINGS_SCHEMABATCH and DATAPUMPSETTINGS_SCHEMABATCHCOUNT were specified.
- PRGT-01093: invalid characters specified for schema names "{0}" for migration
-
Cause: An attempt to migrate a database with zero downtime was rejected because the specified option included invalid characters.
- PRGT-01094: mutually exclusive DATAPUMPSETTINGS_SCHEMABATCH, DATAPUMPSETTINGS_SCHEMABATCHCOUNT, and INCLUDEOBJECTS parameters were specified
-
Cause: An attempt to migrate a database with zero downtime was rejected because the mutually exclusive parameters INCLUDEOBJECTS, DATAPUMPSETTINGS_SCHEMABATCH and DATAPUMPSETTINGS_SCHEMABATCHCOUNT were specified.
- PRGT-01095: File "{0}" does not exist.
-
Cause: An attempt to locate the specified file failed.
- PRGT-01096: Path "{0}" is not a file.
-
Cause: The specified path was not a file.
- PRGT-01097: mutually exclusive DATAPUMPSETTINGS_SCHEMABATCH, DATAPUMPSETTINGS_SCHEMABATCHCOUNT, and DATAPUMPSETTINGS_METADATAFIRST parameters were specified
-
Cause: An attempt to migrate a database with zero downtime was rejected because the mutually exclusive parameters DATAPUMPSETTINGS_METADATAFIRST, DATAPUMPSETTINGS_SCHEMABATCH and DATAPUMPSETTINGS_SCHEMABATCHCOUNT were specified.
- PRGT-01098: Invalid site type specified: {0}
-
Cause: The site type specified was not valid.
- PRGT-01099: Command '{0}' timed out after {1} seconds.
-
Cause: The specified command timed out.