PRGZ-1000 to PRGZ-3201

126 PRGZ-1000 to PRGZ-3201

PRGZ-1000: inaccessible file "{0}" for user "{1}": Cause: An attempt to upgrade a database with zero downtime failed because the specified file was inaccessible for the indicated user.; Action: Ensure that the indicated file and all of its parent directories have execute permissions for the indicated user, and then retry the command.
PRGZ-1001: 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-1002: 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-1004: 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-1008: 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-1009: 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-1012: 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-1013: 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-1015: 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-1016: 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-1017: 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-1018: 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-1117: 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-1118: 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-1119: 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-1125: 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-1126: 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-1128: 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-1129: 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-1130: 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-1131: 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-3100: 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-3102: 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-3103: 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-3104: unable 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-3105: 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-3106: 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-3107: 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-3108: 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 Administrator's Guide for more details regarding keystore administration.
PRGZ-3110: 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-3111: 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-3112: 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-3113: 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 Administrator's Guide for more details regarding keystore administration.
PRGZ-3114: 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-3115: 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-3116: 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-3117: 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-3120: 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-3122: 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-3124: 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-3125: 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-3126: 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-3127: 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-3128: 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-3129: 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-3130: 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-3131: 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-3132: 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-3133: 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-3134: 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-3135: 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-3136: 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-3137: 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-3149: 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-3151: 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-3155: 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-3156: 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-3163: 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-3166: 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-3169: 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-3200: 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-3201: 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.