PRGT-01000 to PRGT-01099

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.; Action: Ensure that the indicated JAR file is present and retry the command.
PRGT-01007: invalid value "{0}" specified for -pauseafter option: Cause: Unsupported phase was specified for -pauseafter option.; Action: Ensure that a valid phase value is specified for -pauseafter option and retry the command. Use -eval option to list the supported phases to pause.
PRGT-01008: Oracle home ___location {0} does not contain program {1}: Cause: The current Oracle home directory did not contain the indicated utility.; Action: Provide the correct Oracle home directory.
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.; Action: Verify that the 'bin' directory under the indicated Oracle home contains the 'oraclebasehome' binary, and verify execution of the command 'oraclebasehome' manually on that Oracle home.
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"; Action: Ensure that a valid offset value is specified for -schedule option and retry the command. Example 1: +44:22:33 to specify offset value of 44 hours, 22 minutes and 33 seconds. Example 2: +11:02:02:44:22:33 to specify offset value of 11 days, 02 months, 02 years, 44 hours, 22 minutes and 33 seconds.
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.; Action: Ensure that a valid offset value is specified for each of the fields of the offset value for the -schedule option and retry the command. Maximum allowed values for "+dd:mm:yy:hh:mm:ss" is "+31:12:99:23:59:59"
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.; Action: Retry the operation specifying a valid value for option '-raconetimeout'.
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.; Action: Retry the operation specifying valid options.
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.; Action: Rerun the migrate command with the '-ignoremissingpatches <patch_name>[,<patch_name>...]' option to ignore specific patches or with the '-ignore ALL|PATCH_CHECK' option to ignore patch checking, or apply the indicated patches to the target database and retry the migration.
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.; Action: Specify a valid client name.
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.; Action: Specify a valid working copy path.
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.; Action: Specify a valid Oracle base path.
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.; Action: Refer to MOS note 2485457.1, and retry the operation after installing the relevant Oracle AutoUpgrade software.
PRGT-01022: Invalid bug number list "{0}" was specified.: Cause: Bug numbers were specified in an incorrect format.; Action: Bug numbers should contain only comma separated numeric values. Please remove redundant commas and other illegal characters and retry the command.
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.; Action: Provide a valid value that doesn't contain invalid characters.
PRGT-01024: invalid value "{0}" specified for incremental interval option: Cause: Unsupported value was specified for the incremental interval option.; Action: Ensure that a valid numeric value is specified for incremental interval option and retry the command.
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.; Action: Correct the problem indicated by the accompanying error messages and then retry.
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.; Action: Retry the operation, providing a wallet containing the password.
PRGT-01027: -jobtype option cannot be used with any other options except -jobid: Cause: The option jobtype was used with incompatible options.; Action: Retry the command specifying only jobtype and jobid 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.; Action: Retry the command specifying a different node than current node for the '-batches' option.
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.; Action: Examine the accompanying error messages, address issues reported, and retry.
PRGT-01030: invalid value "{0}" specified for -stopafter option: Cause: Unsupported phase was specified for -stopafter option.; Action: Ensure that a valid phase value is specified for -stopafter option and retry the command.
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.; Action: Retry the command on RHP Server Cluster specifying the -zip option.
PRGT-01032: failed to open the wallet file "{0}": Cause: An attempt to read the wallet file failed.; Action: Verify the file access permissions and provide a valid user for opening the wallet.
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.; Action: Ensure that the file exists, is readable, and contains correct JSON content.
PRGT-01038: ZDM service is not running.: Cause: ZDM service was not running.; Action: Review the accompanying error messages, and resolve the indicated problems, if any. Ensure the ZDM service is running using zdmservice status command and if required, start the service using zdmservice start command and then retry the operation.
PRGT-01039: identity file "{0}" specified in param "{1}" not found on node "{2}": Cause: The exepcted identity file not found in specified path; Action: Provide a valid identity file path
PRGT-01040: Invalid command specified: {0}: Cause: The command keyword specified on the command line was not recognized.; Action: Valid commands are abort|add|audit|migrate|modify|query|resume. Inline help for zdmcli is printed with this error. Check the zdmcli usage printed along with this error and specify a valid command.
PRGT-01041: Command "{0}" is not supported for object "{1}": Cause: An unsupported command and object combination was specified.; Action: Use the command 'zdmcli -h' to identify valid combinations and re-issue the command.
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.; Action: Reissue the command specifying the '-datafileDestination' option with ASM disk group or with ACFS.
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.; Action: Retry the operation, ensuring that the response file contains only valid property names, refer to zdm_logical_template.rsp for the list of valid properties. The client should not retry the request without modifying the response file.
PRGT-01044: Invalid edition "{0}".: Cause: The edition type specified was not valid.; Action: Supply a valid edition type. Allowed values are: ENTERPRISE or STANDARD.
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.; Action: Examine the accompanying messages, resolve the issues, and then retry the operation.
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.; Action: Reissue the command specifying the '-datafileDestination' option with ASM disk group or with ACFS.
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.; Action: Retry the operation specifying valid options.
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.; Action: Retry the operation specifying valid options.
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.; Action: Examine the accompanying messages, resolve the issues, and then retry the operation.
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.; Action: Refer to the product documentation for the supported executable types and retry.
PRGT-01051: Identity file "{0}" specified in parameter "{1}" is not readable.: Cause: The specified identity file was not readable.; Action: Provide a valid identity file path and retry the operation.
PRGT-01052: Identity file "{0}" specified in parameter "{1}" is not a file.: Cause: The specified identity file was not a valid file.; Action: Provide a valid identity file path and retry the operation.
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.; Action: Reissue the command specifying the '-gimrwc' option.
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.; Action: Ensure specified bastion details are valid and retry the operation.
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.; Action: Refer to the product documentation for allowed values and ensure a valid value is specified and then retry the operation.
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.; Action: Retry the command specifying the list of nodes 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.; Action: Retry the operation after removing specified option.
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.; Action: Provide supported environment name and database type combination in response file and then retry the operation.
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.; Action: Retry the operation, providing DUMPTRANSFERDETAILS_S3BUCKET details.
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.; Action: Retry the operation, providing the DUMPTRANSFERDETAILS_S3BUCKET_NAME value.
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.; Action: Retry the operation, providing the DUMPTRANSFERDETAILS_S3BUCKET_REGION value.
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.; Action: Retry the operation, providing DUMPTRANSFERDETAILS_S3BUCKET_ACCESSKEY option.
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.; Action: Retry the operation, after providing the SOURCEDATABASE_ENVIRONMENT parameters.
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.; Action: Retry the operation after providing the correct value for SOURCEDATABASE_ENVIRONMENT_NAME and DATA_TRANSFER_MEDIUM.
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.; Action: Remove DATAPUMPSETTINGS_EXPORTDIRECTORYOBJECT_PATH and then retry the operation.
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.; Action: Retry the operation, after providing the correct value for proxy host and port.
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.; Action: Retry the operation, after removing the -sourcenode argument.
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.; Action: Retry the operation after removing specified option
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.; Action: Refer to the product documentation for the supported filter types and retry.
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.; Action: Refer to the product documentation for the supported filter types and retry.
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.; Action: Retry the operation after correcting the specified option.
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.; Action: Retry the operation after correcting the specified option.
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.; Action: Retry the operation after correcting the specified option.
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.; Action: Retry the operation after correcting the specified option.
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.; Action: Retry the operation after correcting the specified option.
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.; Action: Retry the operation after correcting the specified option.
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.; Action: Retry the operation after specifying a supported value.
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'.; Action: Retry the command, omitting the '-eval' option.
PRGT-01084: invalid value {0} specified for job tag parameter: Cause: Unsupported tag value was specified for -jobtag option.; Action: Ensure that a valid tag value is specified for -jobtag option and retry the command.
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.; Action: Retry the operation, specifying SOURCEDATABASE_GGADMINUSERNAME.
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.; Action: Retry the operation, specifying TARGETDATABASE_GGADMINUSERNAME.
PRGT-01087: Path "{0}" does not exist.: Cause: An attempt to locate the specified path failed.; Action: Ensure that the specified path exists, and retry the operation.
PRGT-01088: Path "{0}" is not a directory.: Cause: The specified path was not a directory.; Action: Ensure that the specified path is a directory, and retry the operation.
PRGT-01089: Directory "{0}" is not empty.: Cause: The specified directory was not empty.; Action: Ensure that the specified directory is empty, and retry the operation.
PRGT-01090: Directory "{0}" is empty.: Cause: The specified directory was empty.; Action: Ensure that the specified directory contains the backup files of a Fleet Patching and Provisioning Server, and retry the operation.
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.; Action: Retry the operation after removing the specified option.
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.; Action: Refer to the product documentation for the supported filter types and retry.
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.; Action: Retry the operation after correcting the specified option.
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.; Action: Refer to the product documentation for the supported parameters and retry.
PRGT-01095: File "{0}" does not exist.: Cause: An attempt to locate the specified file failed.; Action: Ensure that the specified file exists, and retry the operation.
PRGT-01096: Path "{0}" is not a file.: Cause: The specified path was not a file.; Action: Retry the operation, specifying the name of an existing 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.; Action: Refer to the product documentation for the supported parameters and retry.
PRGT-01098: Invalid site type specified: {0}: Cause: The site type specified was not valid.; Action: Supply a valid site type. The allowed values are ORACLERESTART, REMOTENODE, and STANDALONE.
PRGT-01099: Command '{0}' timed out after {1} seconds.: Cause: The specified command timed out.; Action: Retry the operation.