PRGZ-01001 to PRGZ-03511

130 PRGZ-01001 to PRGZ-03511

PRGZ-01001: Query of the V$ARCHIVE_DEST_STATUS view for database "{0}" failed.\n{1}: Cause: An attempt to upgrade a database with zero downtime failed because a query of the V$ARCHIVE_DEST_STATUS view failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01002: The '{0}' property has to be set if the '{1}' property is set in the response file {2} and vice versa.: Cause: Only one of the indicated parameters was set in the response file.; Action: Either set both the indicated parameters or unset both of them in the response file.
PRGZ-01004: The directory "{0}" does not exist.: Cause: An attempt to upgrade a database with zero downtime failed because the specified directory did not exist.; Action: Ensure that the specified directory exists and then retry the operation.
PRGZ-01008: failed to execute the statement to convert the database "{0}" to snapshot standby database: Cause: An attempt to migrate a database with zero downtime failed because the execution of the statement to convert the specified database as SNAPSHOT STANDBY failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01009: No Oracle home is found for Oracle SID {0} on node {1}.: Cause: The specified Oracle system identifier (SID) was not found in the oratab file on the specified node.; Action: Ensure that the Oracle SID exists and then retry the operation.
PRGZ-01012: mandatory parameters "{0}" not set: Cause: Either one or all of the indicated parameters was not set in the response file.; Action: Set all of the indicated parameters in the response file.
PRGZ-01013: The path "{0}" does not exist.: Cause: An attempt to migrate a database with zero downtime failed because the specified path did not exist.; Action: Ensure that the specified path exists and then retry the operation.
PRGZ-01015: The specified phase "{0}" does not exist.: Cause: The requested operation failed because the specified phase did not exist.; Action: Retry the operation specifying a valid phase.
PRGZ-01016: ZDLRA is not supported for given Oracle Cloud type "{0}".: Cause: The attempted operation was rejected because it was not supported for the indicated Oracle Cloud type.; Action: Refer to the product documentation for the supported case and retry.
PRGZ-01017: Failure occurred during the creation of Oracle wallets on node "{0}".: Cause: An attempt to upgrade a database with zero downtime failed because the creation of Oracle wallets on the indicated node failed.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01100: The path "{0}" does not exist.: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) was rejected because the specified path did not exist.; Action: Ensure that the specified path exists and then retry the operation.
PRGZ-01101: The source database "{0}" is a multitenant container database.: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) was rejected because the specified source database was a CDB.; Action: Ensure that the source database is not a CDB and then retry the operation.
PRGZ-01102: The target database "{0}" is not a multitenant container database.: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) was rejected because the specified target database was not a CDB that could have the converted PDB plugged in.; Action: Ensure that the specified target database is a CDB and then retry the operation.
PRGZ-01103: The source database "{0}" is a pluggable database existing in the multitenant container database "{1}".: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) was rejected because the specified source database was a PDB existing in the indicated CDB.; Action: Ensure that the specified source database is not a PDB in any CDB and then retry the operation.
PRGZ-01104: The database "{0}" does not exist.: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) was rejected because the specified source database was not present.; Action: Ensure that the specified source database is present and then retry the operation.
PRGZ-01105: The database "{0}" is not running.: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) was rejected because the specified source database was not running.; Action: Ensure that the specified source database is running and then retry the operation.
PRGZ-01106: Stored procedure to create the PDB description file for database "{0}" failed.\n{1}: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) failed because the stored procedure to create the PDB description file for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01107: Stored procedure to check the plug compatibility for database "{0}" failed.\n{1}: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) was rejected because the stored procedure to check the plug compatibility for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01108: The source database "{0}" is not compatible with the multitenant container database "{1}".: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) was rejected because the specified source database was not compatible with the indicated CDB as a PDB.; Action: Ensure the source database is fully compatible with the indicated CDB, and then retry the operation.
PRGZ-01109: The PDB description file for source database "{0}" is missing.: Cause: An internal error occurred.; Action: Contact Oracle Support Services.
PRGZ-01110: SQL statement to show compatibility violations for source database "{0}" failed.\n{1}: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) failed because the statement to show compatibility violations for the specified source database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01111: SQL statement to create the pluggable database "{0}" failed.\n{1}: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) failed because the statement to create the specified PDB failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01112: SQL statement to open the pluggable database "{0}" failed.\n{1}: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) failed because the statement to open the specified PDB failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01113: SQL statements to convert database "{0}" to a PDB failed.\n{1}: Cause: An attempt to convert a nonmultitenant container database (CDB) to a pluggable database (PDB) failed because statements to convert the specified database to a PDB failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01114: unable to find a free port ranging from {0} to {1}: Cause: An attempt to upgrade a database with zero downtime failed because an attempt to find a free port within the indicated range failed.; Action: Ensure there is a free port within the indicated range and then retry the operation.
PRGZ-01115: parameter "{0}" not supported: Cause: Either one or all of the indicated parameters was set in the response file and not supported.; Action: Refer to the product documentation for the supported case and retry.
PRGZ-01116: The curl version from node {0} is not supported.: Cause: The current curl version of the specified node was not supported by zero downtime migration (ZDM).; Action: Ensure all nodes have a compatible version of curl installed.
PRGZ-01117: The curl package is not installed on node {0}.: Cause: The mentioned node did not have curl installed.; Action: Ensure that all nodes have a compatible version of curl installed.
PRGZ-01118: Database {0} is currently being migrated part of job {1}.: Cause: An attempt to start migrating specified database was rejected because of an ongoing migrate operation.; Action: Wait for specified job to complete or abort the ongoing migrate operation and retry.
PRGZ-01119: incorrect value specified for parameters "{0}": Cause: The indicated parameters were set with incorrect value in the response file.; Action: Refer to the product documentation, correct the values and retry.
PRGZ-01125: No Oracle base is found for Oracle Home {0} on node {1}.: Cause: The specified Oracle home has no Oracle base associated.; Action: Ensure that the Oracle home has an Oracle base associated with it.
PRGZ-01126: missing the "{0}" option or the "{1}" option in the response file: Cause: The response file was missing one of the mandatory options.; Action: One of the indicated options must be specified in the response file.
PRGZ-01128: file "{0}" not found on host "{1}": Cause: An attempt to access the specified file failed.; Action: Ensure that the specified file exists and retry.
PRGZ-01129: failed to locate Zero Downtime Migration property file "{0}": Cause: An internal error occurred. The included value was an internal identifier.; Action: Contact Oracle Support Services.
PRGZ-01130: failed to locate Zero Downtime Migration property "{0}": Cause: An internal error occurred. The included value was an internal identifier.; Action: Contact Oracle Support Services.
PRGZ-01131: The value "{1}" specified for parameter '{0}' is invalid.: Cause: An invalid value was specified for the specified parameter.; Action: Refer to the product documentation for the supported values and retry.
PRGZ-01132: -eval failed for the phase {0} with exception {1}.: Cause: An attempt to perform the -eval operation with zero downtime failed because the indicated phase evaluation failed with the indicated error message.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01133: failed to discover Oracle Database {0} in node {1}\n{2}: Cause: An attempt to migrate a database with zero downtime was rejected because the information about the specified Oracle Database could not be determined.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01134: payload is missing information about Oracle GoldenGate Microservices: Cause: An attempt to migrate a database with zero downtime was rejected because the user did not specify information about Oracle GoldenGate Microservices.; Action: Specify the required information and resubmit the job.
PRGZ-01135: password for user "{0}" was not specified: Cause: An attempt to migrate a database was rejected because the user did not specify the required password.; Action: Specify the required information and resubmit the job.
PRGZ-01136: failed to verify configuration and status of Oracle GoldenGate Microservices at URL "{0}": Cause: An attempt to verify the configuration and status of Oracle GoldenGate Microservices at the specified URL failed.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01137: Oracle GoldenGate Service Manager at URL "{0}" is not healthy.: Cause: An attempt to migrate a database with zero downtime was rejected because the specified Oracle GoldenGate Microservices were not in a healthy state.; Action: Ensure that the specified Oracle GoldenGate Microservices are running in a healthy state, and retry the operation.
PRGZ-01138: Oracle GoldenGate Microservices deployment "{0}" at URL "{1}" is not running.: Cause: An attempt to migrate a database with zero downtime was rejected because the specified Oracle GoldenGate Microservices deployment was not running.; Action: Ensure that the specified Oracle GoldenGate Microservices deployment is running, and retry the operation.
PRGZ-01139: Oracle GoldenGate Microservice "{0}" in deployment "{1}" at URL "{2}" is not healthy.: Cause: An attempt to migrate a database with zero downtime was rejected because the specified Oracle GoldenGate Microservice in the specified deployment was not in a healthy state.; Action: Ensure that the specified Oracle GoldenGate Microservice in the specified deployment is running, and retry the operation.
PRGZ-01140: User data directory for Oracle GoldenGate Microservice deployment "{0}" is "{1}" whereas the user data directory for Oracle GoldenGate Microservice deployment "{2}" is "{3}".: Cause: An attempt to migrate a database with zero downtime was rejected because the specified Oracle GoldenGate Microservice deployments were not using the same user data directory.; Action: Ensure that the specified Oracle GoldenGate Microservice deployments use the same user data directory, and retry the operation.
PRGZ-01141: failed to verify configuration and status of Oracle database "{0}": Cause: An attempt to verify the configuration and status of the specified Oracle database failed.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01142: parameter ENABLE_GOLDENGATE_REPLICATION is not set to 'true' for Oracle database "{0}": Cause: An attempt to migrate a database with zero downtime using Oracle GoldenGate was rejected because database parameter; Action: Set database parameter ENABLE_GOLDENGATE_REPLICATION to 'true' for the specified database, and then retry the operation.
PRGZ-01143: database user "{0}" in Oracle database "{1}" is missing Oracle GoldenGate privileges: Cause: An attempt to migrate a database with zero downtime using Oracle GoldenGate was rejected because the specified database user; Action: Grant the required Oracle GoldenGate privileges, and then retry the operation.
PRGZ-01144: Database "{0}" is not in ARCHIVELOG mode.: Cause: An attempt to migrate a database with zero downtime was rejected because the specified database was not in ARCHIVELOG mode.; Action: Set the database in ARCHIVELOG mode, and then retry the operation.
PRGZ-01145: Minimal supplemental logging is not enabled for database "{0}".: Cause: An attempt to migrate a database with zero downtime was rejected because minimal supplemental logging was not enabled for the specified database.; Action: Enable minimal supplemental logging for the database, and then retry the operation.
PRGZ-01146: FORCE LOGGING is not enabled for database "{0}".: Cause: An attempt to migrate a database with zero downtime was rejected because FORCE LOGGING was not enabled for the specified database.; Action: Enable FORCE LOGGING mode for the database, and then retry the operation.
PRGZ-01147: Database "{0}" contains tables which do not have FULL Oracle GoldenGate capture process support: "{1}": Cause: An attempt to migrate a database with zero downtime using Oracle GoldenGate was rejected because the specified database contained; Action: Exclude the inidicated tables from Oracle GoldenGate capture process, and then retry the operation.
PRGZ-01148: Maximum of "{0}" Oracle GoldenGate Extract processes can be created for source database.: Cause: An attempt to migrate a database with zero downtime using more than the allowed number of Oracle GoldenGate Extract processes was rejected.; Action: Specify settings for the valid number of Oracle GoldenGate Extract processes, and then retry the operation.
PRGZ-01149: Maximum of "{0}" Oracle GoldenGate Replicat processes can be created for target database.: Cause: An attempt to migrate a database with zero downtime using more than the allowed number of Oracle GoldenGate Replicat processes was rejected.; Action: Specify settings for the valid number of Oracle GoldenGate Replicat processes, and then retry the operation.
PRGZ-01150: Oracle GoldenGate Parallel Replicat parameter APPLY_PARALLELISM cannot be used with parameters MIN_APPLY_PARALLELISM or MAX_APPLY_PARALLELISM.: Cause: An attempt to migrate a database using Oracle GoldenGate was rejected because an invalid combination of APPLY_PARALLELISM Replicat paramters was specified.; Action: Either specify parameter APPLY_PARALLELISM or define a range using parameters MIN_APPLY_PARALLELISM and MAX_APPLY_PARALLELISM, and then retry the operation.
PRGZ-01151: Oracle database parameter STREAMS_POOL_SIZE is currently set to "{0}" instead of the minimum expected value of "{1}" for source database "{2}".: Cause: An attempt to migrate a database with zero downtime using Oracle GoldenGate was rejected because the Oracle database parameter STREAMS_POOL_SIZE was not set to the desired value.; Action: Increase the value of Oracle database parameter STREAMS_POOL_SIZE, and then retry the operation.
PRGZ-01153: Oracle GoldenGate Microservice deployment "{0}" with software version "{1}" at URL "{2}" does not support database of version "{3}".: Cause: An attempt to migrate a database with zero downtime was rejected because the specified Oracle GoldenGate Microservice deployment does not support the database.; Action: Ensure that the specified Oracle GoldenGate Microservice deployment supports the database version, and retry the operation.
PRGZ-01154: Oracle database parameter "{0}" is not set to the same value across all instances of Oracle database "{1}".: Cause: An attempt to migrate the specified database with zero downtime was rejected because the specified database parameter did not have the same setting across all instances of the database.; Action: Ensure that the specified database parameter has the same setting across all instances of the database, and then retry the operation.
PRGZ-01155: Database "{0}" contains no tables which are owned by users who are not Oracle-maintained.: Cause: An attempt to migrate a database was rejected because the specified database contained no tables which are owned by users that are not Oracle-maintained.; Action: None
PRGZ-01156: No object in database "{0}" has been selected for migration.: Cause: An attempt to migrate a database was rejected because all objects in the specified database have been excluded.; Action: Verify the input, ensure that not all database objects have been excluded, and then retry the operation.
PRGZ-01157: OCID "{0}" represents neither an Autonomous Database nor a user-managed database.: Cause: An attempt to migrate a database was rejected because the specified Oracle Cloud identifier (OCID) was not a valid OCID for a database system on Oracle Cloud Infrastructure (OCI).; Action: Verify the input, and then retry the operation.
PRGZ-01158: Current lifecycle state of OCI database "{0}" is "{1}".: Cause: An attempt to migrate a database was rejected because the lifecycle state of the database on Oracle Cloud Infrastructure (OCI) with the specified Oracle Cloud identifier (OCID) was not 'Available'.; Action: Ensure that the lifecycle state of the specified database on OCI is 'Available', and then retry the operation.
PRGZ-01159: OCI REST API for database "{0}" failed.: Cause: An attempt to migrate a database was rejected because a REST API call for the database on Oracle Cloud Infrastructure (OCI) with the specified Oracle Cloud identifier (OCID) failed.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-01160: failed to identify the infrastructure shape and workload type of OCI database "{0}": Cause: An attempt to migrate a database was rejected because the infrastructure shape and workload type of the database on Oracle Cloud Infrastructure (OCI) with the specified Oracle Cloud identifier (OCID) could not be determined.; Action: Ensure that the GET request to OCI database service for the specified database returns a valid response, and then retry the operation.
PRGZ-01161: Predefined database service "{0}" does not exist for Autonomous Database "{1}".: Cause: An attempt to migrate a database was rejected because the Autonomous Database on Oracle Cloud Infrastructure (OCI) with the specified Oracle Cloud Identifier (OCID) was not configured with the indicated predefined database service.; Action: Verify the configuration of the specified Autonomous Database, and then retry the operation.
PRGZ-01162: payload is missing information about on-premise Oracle database: Cause: An attempt to migrate a database was rejected because information about the on-premise database was not specified.; Action: Specify the required information and resubmit the job.
PRGZ-01163: payload is missing information about on-premise Oracle multitenant database's CDB root: Cause: An attempt to migrate a database was rejected because information about the CDB root of the on-premise Oracle multitenant database was not specified.; Action: Specify the required information and resubmit the job.
PRGZ-01164: payload is missing information about database on Oracle Cloud Infrastructure: Cause: An attempt to migrate a database was rejected because information about the database on Oracle Cloud Infrastructure was not specified.; Action: Specify the required information and resubmit the job.
PRGZ-01165: payload is missing OCID of database on Oracle Cloud Infrastructure: Cause: An attempt to migrate a database was rejected because the Oracle Cloud identifier (OCID) of the database on Oracle Cloud Infrastructure was not specified.; Action: Specify the required information and resubmit the job.
PRGZ-01166: payload is missing information about OCI user who will call OCI REST APIs: Cause: An attempt to migrate a database was rejected because information about the Oracle Cloud Infrastructure (OCI) user who will call OCI REST APIs was not specified.; Action: Specify the required information and resubmit the job.
PRGZ-01167: payload is missing connection details for user-managed database system on Oracle Cloud Infrastructure: Cause: An attempt to migrate a database was rejected because information about the user-managed database system on Oracle Cloud Infrastructure was not specified.; Action: Specify the required information and resubmit the job.
PRGZ-01168: failed to create directory "{0}" to store client credentials for Autonomous Database "{1}": Cause: An attempt to migrate a database was rejected because an attempt to create the indicated directory for the specified Autonomous Database failed.; Action: Verify file system permissions, and retry the operation.
PRGZ-01169: Client credentials downloaded for Autonomous Database "{0}" do not include tnsnames.ora file.: Cause: An attempt to migrate a database was rejected because the client credentials downloaded for the specified Autonomous Database did not include tnsnames.ora file.; Action: Ensure Oracle Cloud Infrastructure API GenerateAutonomousDatabaseWallet returns a valid response for the specified Autonomous Database, and then retry the operation.
PRGZ-01170: Parameter "{0}" is not valid for Oracle Data Pump operation type "{1}" with mode "{2}".: Cause: An attempt to migrate a database was rejected because the specified parameter did not apply to the specified Oracle Data Pump operation and mode.; Action: Do not specify the indicated parameter, and retry the operation.
PRGZ-01171: Oracle Data Pump parameter FLASHBACK_SCN or FLASHBACK_TIME is not required for online logical migration.: Cause: An attempt to migrate a database with zero downtime was rejected because Oracle Data Pump parameter FLASHBACK_SCN or FLASHBACK_TIME was specified. Schemas being migrated will be prepared for instantation before Oracle GoldenGate Extract process is started, thereby ensuring that Oracle GoldenGate Replicat process does not apply duplicate data. Because of this, there is no need to use Oracle Data Pump parameter FLASHBACK_SCN or FLASHBACK_TIME.; Action: Do not specify Oracle Data Pump parameter FLASHBACK_SCN or FLASHBACK_TIME, and retry the operation.
PRGZ-01172: Directory object 'data_pump_dir' does not exist in Autonomous Database "{0}".: Cause: An attempt to migrate a database was rejected because the Autonomous Database on Oracle Cloud Infrastructure (OCI) with the specified Oracle Cloud identifier (OCID) did not contain directory object 'data_pump_dir'.; Action: Verify the configuration of the specified Autonomous Database, and then retry the operation.
PRGZ-01173: OCI Object Store bucket for storing the wallet containing certificates for on-premise database was not specified.: Cause: An attempt to create a database link from an Autonomous Database on Oracle Cloud Infrastructure (OCI) to an on-premise database was rejected because was rejected because information was not specified about the OCI Object Store bucket which would be used to store the wallet containing certificates for the on-premise database.; Action: Specify information about the OCI Object Store bucket, and then retry the operation.
PRGZ-01174: OCI Object Store bucket for storing Oracle Data Pump dump files was not specified.: Cause: An attempt to migrate a database was rejected because information was not specified about the Oracle Cloud Infrastructure (OCI) Object Store bucket which would be used to store Oracle Data Pump dump files.; Action: Specify information about the OCI Object Store bucket, and then retry the operation.
PRGZ-01175: Information about transporting Oracle Data Pump dump files is missing.: Cause: An attempt to migrate a database was rejected because how to transfer Oracle Data Pump dump files from the on-premise database to a database on Oracle Cloud Infrastructure (OCI) was not specified.; Action: Specify the required information, and then resubmit the job. The following cases are supported: 1) Performing a remote network import using a newly created or an existing database link between database on OCI to on-premise database. 2) Uploading Oracle Data Pump dump files to an OCI Object Store bucket, if database on OCI is an Autonomous Database. 3) Transferring Oracle Data Pump dump files from on-premise database server to OCI database server using newly created or existing database directory objects, if database on OCI is a user-managed database system.
PRGZ-01176: Information about database directory object is missing for database "{0}".: Cause: An attempt to migrate a database was rejected because information about the directory object to be used for storing Oracle Data Pump dump files was not specified.; Action: Either specify information required to create a new directory object or specify an existing directory object, and then resubmit the job.
PRGZ-01177: Database link "{0}" is invalid and unusable.: Cause: An attempt to migrate a database was rejected because the specified database link was invalid and unusable.; Action: Drop the specified database link, and then resubmit the job. Oracle Zero Downtime Migration (ZDM) will automatically create a valid and usable database link.
PRGZ-01182: The parameter '{0}' modified during rerun.: Cause: The value of the indicated parameter was changed during rerun.; Action: Indicated parameter value can not be changed during rerun. Restore the original value and retry.
PRGZ-01184: Specified shard ID {0} does not match with current Zero Downtime Migration (ZDM) host {1}.: Cause: The shard ID specified in the response file did not match with the hostname of the current ZDM server.; Action: Verify that the current job is being executed in the correct host or that the information in the response file is correct.
PRGZ-01185: The source database version {0} and target database version {1} does not match.: Cause: An attempt to migrate the database failed because the source database and target database version did not match.; Action: Ensure that the source and target database major version are equal.
PRGZ-01186: SCAN listener details not found for database {0} on the target node {1}: Cause: An attempt to migrate a database was rejected because the specified database Single Client Access Name (SCAN) listener was either not configured or not enabled.; Action: Verify the configuration of the specified database, ensure the REMOTE_LISTENER parameter is set, and then retry the operation.
PRGZ-01187: identity file "{0}" specified in param "{1}" not found on node "{2}": Cause: The expected identity file not found in specified path; Action: Provide a valid identity file path
PRGZ-01188: failed to resume job "{0}" because the specified '-pauseafter' phase "{1}" is already completed.: Cause: An attempt to resume the migrate database job was rejected because the specified '-pauseafter' phase already has the status completed.; Action: Specify a valid phase to '-pauseafter' and then retry the operation.
PRGZ-01189: Exporting Oracle Data Pump dump files to directory "{0}" on a file system which does not support O_DIRECT is not allowed.: Cause: An attempt to migrate a database using Oracle Data Pump was rejected because the specified directory cannot be used by a Data Pump Export job.; Action: Review MOS note 1330406.1. Either specify a directory on a file system which supports O_DIRECT, or alter the database filesystemio_option to 'none', and then retry the operation.
PRGZ-01190: OCI user "{0}" already has two OCI Auth Tokens.: Cause: An attempt to migrate a database using Oracle Data Pump was rejected because a new Auth Token cannot be created for the Oracle Cloud Infrastructure (OCI) user with the specified Oracle Cloud Identifier (OCID).; Action: Specify an existing Auth Token, or delete an unused Auth Token, or specify a different OCI user, and then retry the operation.
PRGZ-01191: Auth Token was not specified for OCI user "{0}".: Cause: An attempt to migrate a database using Oracle Data Pump was rejected because an Auth Token was not specified for the Oracle Cloud Infrastructure (OCI) user with the specified Oracle Cloud Identifier (OCID).; Action: Either specify an existing Auth Token, or specify that Oracle Zero Downtime Migration should create a new Auth Token, and then retry the operation.
PRGZ-01192: Tablespaces "{0}" do not exist in database "{1}".: Cause: An attempt to migrate a database using Oracle Data Pump was rejected because the indicated tablespaces do not exist in the specified database.; Action: Either remap tablespaces, or create the indicated tablespaces in the specified database, and then retry the operation.
PRGZ-01195: User action specified for phase {0} which does not support user actions.: Cause: The attempted operation was rejected because it was not supported for the indicated operation phase.; Action: Refer to the product documentation for the supported case and retry.
PRGZ-01196: node information not found to execute user action for phase "{0}": Cause: The attempted operation was rejected because node information to execute the indicated operation phase was not found.; Action: Reissue the command with necessary node information to execute the user action.
PRGZ-01197: Source database version {0} is not supported for non container database to pluggable database conversion.: Cause: Pre 12c database conversion into pluggable database was not supported.; Action: Ensure that the source database version is 12c or above and reissue the migration command.
PRGZ-01198: sourcedb or sourcesid option is missing for running logical migration: Cause: An attempt to migrate a database was rejected because sourcedb or sourcesid option was not specified.; Action: Specify the required information and resubmit the job.
PRGZ-01199: Oracle database parameter STREAMS_POOL_SIZE is currently not set for source database "{0}".: Cause: An attempt to migrate a database with zero downtime using Oracle DataPump was rejected because the Oracle database parameter STREAMS_POOL_SIZE was not set.; Action: Ensure the value of Oracle database parameter STREAMS_POOL_SIZE is set and then retry the operation.
PRGZ-01200: missing source database SSL authentication details to set up database link: Cause: An attempt to migrate a database with zero downtime using Oracle DataPump was rejected because the details to set up database link with Autonomous Database to source database using SSL (TCPS) authentication were not avaialable; Action: Ensure the source database is configured to use TCP/IP with SSL (TCPS) authentication and secure connection details are provided in the response file and reattempt the operation.
PRGZ-01201: Oracle Data Pump METADATA_FILTER option {0} is not supported for job mode {1}: Cause: The attempted operation was rejected because the indicated METADATA_FILTER is not supported in Zero Downtime Migration for the given Oracle Data Pump job mode.; Action: Refer to the product documentation for the supported case and retry.
PRGZ-01203: Warning: ignoring custom action {0} execution failure...: Cause: The indicated custom action execution failed and the failure was ignored due to custom action property.; Action: Refer to product documentation if the custom action execution error should not be ignored.
PRGZ-01204: custom action {0} execution failed: Cause: An attempt to migrate a database failed because the specified custom action failed to execute. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03100: SQL statement to disable block change tracking for database "{0}" failed.: Cause: An attempt to migrate a database with zero downtime failed because the statment to disable block change tracking failed for the specified database. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03102: keystore open failed for database "{0}"\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the operation to open the keystore failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03103: keystore close failed for database "{0}"\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the operation to close the keystore failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03104: failed to get Oracle base for home "{0}": Cause: An attempt to migrate a database with zero downtime failed because the operation to retrieve the Oracle base for the specified home failed.; Action: Ensure that the specified home exists and is a valid Oracle home.
PRGZ-03105: restoration of data files failed\n{0}: Cause: An attempt to migrate a database with zero downtime failed because the database files could not be restored. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03106: database files recovery failed\n{0}: Cause: An attempt to migrate a database with zero downtime failed because the database files could not be recovered. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03107: restoration of database control files failed\n{0}: Cause: An attempt to migrate a database with zero downtime failed because the database control files could not be restored. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03108: Oracle Transparent Data Encryption (TDE) keystore is not set up for database "{0}".: Cause: An attempt to migrate a database with zero downtime was rejected because the Oracle Transparent Data Encryption (TDE) keystore was not set up for the specified database.; Action: Set up Oracle Transparent Data Encryption (TDE) keystore and then retry the operation. Refer to Oracle Database Advanced Security Guide for more details regarding keystore administration.
PRGZ-03110: failed to open Oracle Transparent Data Encryption (TDE) keystore directory location "{0}" for database "{1}"\n{2}: Cause: An attempt to migrate a database with zero downtime failed because the indicated Oracle Transparent Data Encryption (TDE) keystore directory could not be opened. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03111: Oracle Transparent Data Encryption (TDE) keystore password not specified for database "{0}".: Cause: An attempt to migrate a database with zero downtime failed because a password-based Oracle Transparent Data Encryption (TDE) keystore was detected but the keystore password was not specified.; Action: Specify the Oracle Transparent Data Encryption (TDE) keystore password, and then retry the operation.
PRGZ-03112: Oracle Transparent Data Encryption (TDE) keystore master key is not configured for database "{0}".: Cause: An attempt to migrate a database with zero downtime failed because the Oracle Transparent Data Encryption (TDE) keystore master key was not detected.; Action: Configure the Oracle Transparent Data Encryption (TDE) keystore master key, and then retry the operation. Refer to the Oracle documentation for more details regarding keystore administration.
PRGZ-03113: Oracle Transparent Data Encryption (TDE) keystore is of type LOCAL_AUTOLOGIN for database "{0}".: Cause: An attempt to migrate a database with zero downtime failed because Oracle Transparent Data Encryption (TDE) keystore of type LOCAL_AUTOLOGIN was detected.; Action: Refer to Oracle Database Advanced Security Guide for more details regarding keystore administration.
PRGZ-03114: failed to duplicate database "{0}" to physical standby database: Cause: An attempt to migrate a database with zero downtime failed because the execution of the statement to duplicate the database from backup as PHYSICAL STANDBY failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03115: failed to remove database "{0}"\n{1}: Cause: An attempt to remove the database that was already configured failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03116: failed to start instance for database "{0}".\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the statement to start database instance from SPFILE failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03117: failed to execute SQL statement.\n{0}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the SQL statement failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03120: failed to clone target database '{0}' from ZDLRA '{1}'\n{2}: Cause: An attempt to migrate a database with zero downtime failed because the execution of Recovery Manager (RMAN) procedure to duplicate database from Zero Data Loss Recovery Appliance (ZDLRA) failed. Accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03122: failed to add instance for database "{0}"\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the execution of "srvctl add instance" failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03124: failed to add server pool for database "{0}"\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the execution of "srvctl add serverpool" as database owner failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03125: failed to obtain configuration of resource "{0}"\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the resource configuration could not be obtained. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03126: Target database unique name specified is identical to the source database unique name, and they must be different.: Cause: An attempt to migrate a database with zero downtime was rejected because the target database unique name was the same as the source database unique name, and the target must be given a different database unique name.; Action: Specify a different database unique name for the target, and then retry the operation.
PRGZ-03127: Target database unique name was not specified.: Cause: An attempt to migrate a database with zero downtime was rejected because the target database unique name was not specified.; Action: Retry the operation, specifying a target database unique name.
PRGZ-03128: failed to change owner to "{0}" for file "{1}"\n{2}: Cause: An attempt to migrate a database with zero downtime failed because the ownership of the indicated file could not be changed as indicated.; Action: Ensure that the directory of the indicated file has execute permission. Ensure that the ownership of the file can be modified, and then retry the operation.
PRGZ-03129: failed to copy file "{0}" to "{1}"\n{2}: Cause: An attempt to copy the indicated file to the indicated node failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03130: failed to establish connection to target listener from nodes {0}\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the source node couldn't reach the target node using 'tnsping'.; Action: Ensure that there is connectivity with the target node from the source node using 'tnsping' and then retry the operation.
PRGZ-03131: failed to establish connection to target listener from nodes {0} with the specified SSH tunnel port\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the source node couldn't reach the target node using 'tnsping' with the specified target SSH tunnel port.; Action: Ensure that either the provided target SSH tunnel port is correct or that the SSH tunnel was properly configured and then retry the operation.
PRGZ-03132: failed to start database "{0}".\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the statement to start database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03133: failed to query the snapshot control file location for database "{0}"\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the operation to query the indicated parameter from the indicated view for the specified database failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03134: failed to validate path "{0}"\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the specified path is incorrect or lacks permission to write.; Action: Ensure that the specified path is valid and then retry the operation.
PRGZ-03135: SQL statement to save pdb state for database "{0}" failed\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the query to save pdb state failed for the specified database. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03136: SQL statement to open pdb "{1}" with "{2}" mode for database "{0}" failed\n{3}: Cause: An attempt to migrate a database with zero downtime failed because the query to open indicated pluggable databases failed for the specified database. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03137: RMAN crosscheck for database "{0}" failed\n{3}: Cause: An attempt to migrate a database with zero downtime failed because RMAN crosscheck failed for the specified database. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03149: Query to retrieve the latest backup SCN for database "{0}" failed\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the query to retrieve the latest sequence change number (SCN) in the backup failed for the specified database. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03151: restoration of database files failed\n{0}: Cause: An attempt to migrate a database with zero downtime failed because the database files could not be restored. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03155: Failed to create database initialization file {0}\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the indicated database initialization file could not be created. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03156: Failed to open database initialization file {0}\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the indicated database initialization file could not be opened. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03163: Restoration and encryption of data files failed\n{0}: Cause: An attempt to migrate a database with zero downtime failed because the database files could not be restored and encrypted. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03166: Renaming of TEMP files and online redo log files failed\n{0}: Cause: An attempt to migrate a database with zero downtime failed because the TEMP files and online redo log files could not be renamed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03169: Database open with RESETLOGS for database {0} failed\n{1}: Cause: An attempt to migrate a database with zero downtime failed because an error was encountered during opening of the database with RESETLOGS. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03175: failed to shut down database {0}\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the indicated database could not be shut down. The accompanying messages provide detailed failure information.; Action: Ensure that the database is able to be shut down and retry the operation.
PRGZ-03176: a database connection cannot be established from target node {0} to source node {1}: Cause: An attempt to migrate a database with zero downtime failed because the indicated target cannot establish a connection to the source node and response file parameter SKIP_FALLBACK was set to FALSE.; Action: Ensure that there is connectivity from the target node to the source node using 'tnsping' and then retry the operation.
PRGZ-03177: Warning: no connection from target node to database at source node, redo logs will not be shipped to database at source node: Cause: The SKIP_FALLBACK option in the response file was set to TRUE.; Action: If fallback is desired, ensure that there is connectivity from the target node to the source node usnig 'tnsping' and set the SKIP_FALLBACK option to FALSE in the response file and retry the operation.
PRGZ-03181: Internal error: {0}: Cause: An internal error occurred. The included value is an internal identifier.; Action: Contact Oracle Support Services.
PRGZ-03182: failed to query the RMAN configuration for database "{0}"\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the operation to query the RMAN configuration for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03183: failed to move the file "{0}"\n{1}: Cause: An attempt to move the specified file failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03184: failed to remove the file "{0}"\n{1}: Cause: An attempt to remove the specified file failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03185: Transparent Data Encryption (TDE) keystore found in status "{2}" for pluggable database "{1}" in database "{0}". Keystore is not open.: Cause: An attempt to migrate a database with zero downtime failed because the Transparent Data Encryption (TDE) keystore was not open in the indicated pluggable database.; Action: Ensure that the keystore wallet is configured and is open in the indicated pluggable database. Refer to the Oracle documentation for more details regarding keystore administration.
PRGZ-03186: Transparent Data Encryption (TDE) keystore master key is not configured for pluggable database "{1}" in database "{0}".: Cause: An attempt to migrate a database with zero downtime failed because the Transparent Data Encryption (TDE) keystore master key was not detected in the indicated pluggable database.; Action: Configure the Transparent Data Encryption (TDE) keystore master key, and then retry the operation. Refer to the Oracle documentation for more details regarding keystore administration.
PRGZ-03187: Transparent Data Encryption (TDE) keystore found in status "{1}" for database "{0}". Keystore is not open.: Cause: An attempt to migrate a database with zero downtime failed because the Transparent Data Encryption (TDE) keystore was not open.; Action: Ensure that the keystore wallet is open. Refer to the Oracle documentation for more details regarding keystore administration.
PRGZ-03189: failed to connect to database "{0}" as sys user with the specified password\n{1}: Cause: An attempt to migrate a database with zero downtime failed, because the connection to the database with the specified; Action: Verify the password specified and then retry the operation.
PRGZ-03200: The name of a multitenant container database (CDB) was not specified.: Cause: An attempt to migrate a database with zero downtime was rejected because the name of a multitenant container database (CDB) was not specified.; Action: Retry the operation, specifying a CDB name.
PRGZ-03201: The specified name "{0}" of a multitenant container database (CDB) is identical to the target database name.: Cause: An attempt to migrate a database with zero downtime was rejected because the indicated CDB name was the same as the target database name, and the CDB name must be given a different database name.; Action: Specify a different CDB name, and then retry the operation.
PRGZ-03202: failed to modify db_unique_name to "{0}"\n{1}: Cause: An attempt to modify the database that was already configured failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03203: failed to remove the standby parameters in primary "{0}"\n{1}: Cause: An attempt to modify the database standby parameters failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03206: failed to start services for database "{0}".\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the database services failed to start. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03212: failed to drop database {0}.\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the database could not be dropped.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03213: failed to change mode to "{0}" for file "{1}"\n{2}: Cause: An attempt to migrate a database with zero downtime failed because the permissions of the indicated file could not be changed as indicated.; Action: Ensure that the directory of the indicated file has execute permission. Ensure that the ownership of the file can be modified, and then retry the operation.
PRGZ-03214: failed to restore the RMAN configuration for database "{0}"\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the operation to restore the RMAN configuration for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03215: failed to start database "{0}" instance on node "{1}".\n{2}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the statement to start database instance on the indicated node failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03216: failed to stop database "{0}" instance on node "{1}".\n{2}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the statement to stop database instance on the indicated node failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03217: Target database {0} conversion to cluster mode failed.: Cause: An attempt to migrate a database with zero downtime failed because the conversion of the indicated database to a cluster database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03219: failed to list the file "{0}"\n{1}: Cause: An attempt to list the specified file failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03220: failed to get the file "{0}"\n{1}: Cause: An attempt to get the specified file failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03221: failed to get list of Oracle Data Pump dump files for {0}: Cause: An attempt to get the specified file failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03222: failed to import the Oracle Data Pump dump files {0}\n{1}: Cause: An attempt to import the specified file failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03225: schema "{0}" not found in database {1}: Cause: An attempt to get the specified schema failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03226: failed to get schemas for database "{0}": Cause: An attempt to get the schemas for the specified database. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03227: failed to set up the credential wallet for database "{0}"\n{1}: Cause: An attempt to set up credential wallet for the specified database. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03230: failed to export the Oracle Data Pump dump files for schema {0}\n{1}: Cause: An attempt to export the indicated file failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03231: Oracle OCI CLI failed to execute\n{0}: Cause: failed to execute Oracle Cloud Infrastructure command line interface. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03232: Oracle OCI CLI failed to list\n{0}: Cause: Failed to execute Oracle Cloud Infrastructure command line interface to list object or bucket. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03233: Oracle OCI CLI failed to get object\n{0}: Cause: Failed to execute Oracle Cloud Infrastructure command line interface to download object. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03234: Oracle OCI CLI failed to put object\n{0}: Cause: Failed to execute Oracle Cloud Infrastructure command line interface to store object. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03237: failed to find the value for parameter "{0}": Cause: An attempt to retrieve the specified parameter failed.; Action: If the reported parameter is a response file parameter, then specify a value as expected for the parameter and then retry the operation. If the reported parameter is not a response file parameter, then an internal error occurred, contact Oracle Support Services.
PRGZ-03241: failed to access Oracle Cloud Identity Information"{0}"\n{1}: Cause: An error occurred while trying to access the specified Oracle Cloud Identity Information. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03242: failed to retrieve Oracle Cloud Identity Information"{0}"\n{1}: Cause: An error occurred while trying to retrieve the specified Oracle Cloud Identity Information. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03244: Backup of archive logs for database "{0}" failed.\n{1}: Cause: An attempt to backup the archive logs for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03247: Media recovery SCN {0} does not include backup start SCN {1}.: Cause: An attempt to backup the specified database failed because the latest available media recovery did not include the indicated SCN recorded at the startup of the backup. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve any indicated problems, and then retry the backup operation.
PRGZ-03254: backup of data and control files for database "{0}" failed\n{1}: Cause: An attempt to backup the data files for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03258: found data files not recovered until the recovery SCN: {0}.: Cause: An attempt to migrate a database with zero downtime failed because the indicated data files were not recovered until the latest recovery SCN.; Action: The indicated data files either need to be recovered manually or dropped before continuing.
PRGZ-03259: error forcing a checkpoint for database {0}\n {1}: Cause: An attempt to migrate a database with zero downtime failed because the command to force explicit checkpoint failed.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03263: incremental restore of data files failed\n{0}: Cause: An attempt to migrate a database with zero downtime failed because the incremental restore of database failed. The accompanying messages provide detailed failure information.; Action: Examine the accompanying messages, resolve the indicated issues, and then retry the operation.
PRGZ-03267: Backup of new data files added during backup for database "{0}" failed.\n{1}: Cause: An attempt to backup the new data files for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03269: cannot locate Oracle Transparent Data Encryption (TDE) keystore location {1} for database "{0}": Cause: An attempt to migrate a database with zero downtime was rejected because the Oracle Transparent Data Encryption (TDE) keystore could not be located for the specified database.; Action: Set up Oracle Transparent Data Encryption (TDE) keystore and then retry the operation. Refer to Oracle Database Advanced Security Guide for more details regarding keystore administration.
PRGZ-03273: failed to create network link {0}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the SQL statement to create network link failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03274: failed to move file {0} to Oracle Cloud secure storage: Cause: An attempt to migrate a database with zero downtime failed because the execution of the SQL statement move the Oracle Data pump logs from datapump directory to Oracle Cloud secure storage. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03275: failed to drop OSS access credential {0}: Cause: An attempt to migrate a database with zero downtime failed because the SQL statement to drop Oracle Cloud secure storage access failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03276: failed to create Oracle Cloud secure storage access credential {0}: Cause: An attempt to migrate a database with zero downtime failed because the SQL statement to setup Oracle Cloud secure storage access failed. The accompanying messages provided detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03277: failed to create a schema {0}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the SQL statement to create schema failed. The accompanying messages provided detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03278: failed to create Oracle Data Pump Directory {0}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the SQL statement failed. The accompanying messages provided detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03299: failed to grant DV_PATCH_ADMIN privilege to SYS in database {0}\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the SQL statement to grant DV_PATCH_ADMIN privileges failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03300: failed to revoke DV_PATCH_ADMIN privilege for SYS in database {0}\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the SQL statement to revoke DV_PATCH_ADMIN privileges failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03301: failed to check Oracle Database Vault for database {0}\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the SQL statement to check if Oracle Database Vault is configured failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03302: cannot locate Transparent Data Encryption (TDE) keystore location for database "{0}": Cause: An attempt to migrate a database with zero downtime was rejected because the Transparent Data Encryption (TDE) keystore could not be located for the specified database.; Action: Ensure that Transparent Data Encryption (TDE) keystore is set up and retry the operation. Refer to Oracle Database Advanced Security Guide for more details regarding keystore administration.
PRGZ-03303: cannot locate Transparent Data Encryption (TDE) keystore location for database "{0}": Cause: An attempt to migrate a database with zero downtime was rejected because the Transparent Data Encryption (TDE) keystore could not be located for the specified database.; Action: Ensure that Transparent Data Encryption (TDE) keystore is set up and retry the operation. Refer to Oracle Database Advanced Security Guide for more details regarding keystore administration.
PRGZ-03304: failed to access Oracle Cloud secure storage"{0}"\n{1}: Cause: An error occurred while trying to access the specified Oracle Cloud secure storage link. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03305: Oracle Cloud OSS pre-authenticated URL not defined: Cause: Oracle Cloud secure storage link was not defined.; Action: Review the Oracle documentation, specify the URL, and then retry the operation.
PRGZ-03311: Database "{0}" is not a multitenant container database.: Cause: An attempt to migrate a database with zero downtime was rejected because the specified database was not a multitenant container database.; Action: Ensure that the specified database is a multitenant container database.
PRGZ-03312: Pluggable database "{1}" not found in database "{0}".: Cause: An attempt to migrate a database with zero downtime was rejected because the indicated pluggable database was not found in the specified multitenant container database.; Action: Ensure that the indicated pluggable database is part of the specified multitenant container database, and then retry the operation.
PRGZ-03313: DBNEWID utility failed for database "{0}". \n{1}: Cause: An attempt to migrate a database with zero downtime was rejected because DBNEWID execution failed.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03325: error killing session for database {0}\n{1}: Cause: An attempt to migrate a database with zero downtime was rejected because session could not be aborted.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03327: Password file does not exist for database {0}.: Cause: An attempt to migrate a database with zero downtime was rejected because the indicated database password file required for cloning the database was not found.; Action: Create the Oracle Database password file, and then retry the operation.
PRGZ-03362: Invalid ACFS Path: "{0}" path "{1}" provided in the response file contains invalid characters: Cause: Provided ACFS path contains invalid characters.; Action: Provide a valid ACFS path.
PRGZ-03363: Failed to query column {1} from the view {2} for data base "{0}".: Cause: An attempt to migrate a database with zero downtime failed because the operation to query the specified database details failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03364: failed to remove service "{0}"\n{1}: Cause: An attempt to remove the database service failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03365: Target database storage path "{0}" of size "{1}" is less than the size required to migrate source database with "{0}" size "{2}": Cause: The target storage path size was too small compared to data, redo and recovery size of the source database.; Action: Allocate the target storage path with a size equal to or greater than the size of the source database and retry the operation.
PRGZ-03369: Backup of archive logs and control files for database "{0}" failed.\n{1}: Cause: An attempt to backup the archive logs and control files for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03371: Backup of data files for database "{0}" failed\n{1}: Cause: An attempt to backup the data files for the specified database failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03373: failed to remove directory "{0}"\n{1}: Cause: An attempt to remove the indicated directory failed.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03376: failed to switch data files to copy for database {0}\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the RMAN data file switch to copy failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03379: failed to run RMAN catalog for database {0}\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the RMAN catalog failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03383: failed to remove Data Guard configuration for database {1} from database {0}\n{2}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the SQL statement to remove Data Guard configuration failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03384: failed to drop standby log file group from database {0}\n{1}: Cause: An attempt to migrate a database with zero downtime failed because the execution of the SQL statement to remove standby log file group failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03387: initialization parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST is set: Cause: An attempt to migrate a database with zero downtime was rejected because the indicated database initialization parameter was found to be set.; Action: Reset and reconfigure the indicated parameter and then retry the operation.
PRGZ-03390: invalid Transparent Data Encryption (TDE) keystore password specified for database "{0}".: Cause: An attempt to migrate a database with zero downtime failed because a password-based Transparent Data Encryption (TDE) keystore was detected but the keystore password specified was invalid.; Action: Specify a valid Transparent Data Encryption (TDE) keystore password and then retry the operation.
PRGZ-03391: failed to access database {0} backup from ZDLRA '{1}': Cause: An attempt to migrate a database with zero downtime failed because the execution of Oracle Recovery Manager (RMAN) procedure to access backup from Zero Data Loss Recovery Appliance (ZDLRA) failed. Accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03392: ZDLRA access user information not supplied: Cause: An attempt to migrate a database with zero downtime was rejected because Zero Data Loss Recovery Appliance (ZDLRA) user detail was not specified.; Action: Specify the required information and resubmit the job.
PRGZ-03393: ZDLRA access password not supplied: Cause: An attempt to migrate a database with zero downtime was rejected because Zero Data Loss Recovery Appliance (ZDLRA) user password detail was not specified.; Action: Specify the required information and resubmit the job.
PRGZ-03397: phase: {1} is invalid for the job: {0}: Cause: An attempt to fetch the phase details failed because the specified phase was not valid for the given job.; Action: Specify a valid phase as listed in query job command and retry the operation with a phase that exists for the given job.
PRGZ-03402: failed to authenticate object store credentials. Invalid username or password: Cause: An attempt to authenticate input credentials failed.; Action: Verify the credentials and then retry the operation.
PRGZ-03420: failed to modify keystore entry "{0}" in wallet "{1}".\n"{2}": Cause: An attempt to migrate a database with zero downtime failed because indicated keystore entry could not be modified.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03421: failed to merge keystore "{0}" into "{1}" for database "{2}": Cause: An attempt to migrate a database with zero downtime failed because the operation to merge the indicated keystores failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03422: failed to create keystore "{0}" for database "{1}"\n{2}: Cause: An attempt to migrate a database with zero downtime failed because the operation to create the indicated keystore failed. The accompanying messages provide detailed failure information.; Action: Review the accompanying messages, resolve the indicated problems, and then retry the operation.
PRGZ-03502: failed to create Self Sign On (cwallet.sso) certificate for keystore location {0}: Cause: An attempt to migrate a database with zero downtime failed because a Self Sign On (cwallet.sso) certificate for the Transparent Data Encryption (TDE) keystore could not be created.; Action: Verify the indicated keystore location and retry the operation.
PRGZ-03503: WARNING: concurrent backup of database {0} to DISK is in progress, completed {1}%: Cause: An attempt to migrate a database with zero downtime failed because the execution of Oracle Recovery Manager (RMAN) procedure to backup is delayed due to ongoing concurrent backup to DISK.; Action: Verify if the ongoing concurrent database backup operation is required.
PRGZ-03504: parameter "{0}" with value "{1}" cannot be combined with parameter "{2}" with value "{3}": Cause: The indicated parameters set with incorrect value in the response file.; Action: Refer to the product documentation, correct the values and retry.
PRGZ-03508: WARNING: apply lag metrics not updated to standby {0}: Cause: An attempt to migrate a database with zero downtime failed because the execution of Oracle Managed Recovery Process metrics were not updated at the standby database.; Action: Ensure that the standby database is receiving data from the primary database as expected.
PRGZ-03510: Job ID {0} is not in ABORTED state.: Cause: Delete job operation failed for the specified job because it was not in the ABORTED state.; Action: Abort the job and retry the operation.
PRGZ-03511: Databse "{0}" is not primary.: Cause: An attempt to migrate a database with zero downtime was rejected because the database role is not primary.; Action: Ensure database role is configured as primary and then retry the operation.