PRGZ-01000 to PRGZ-03129

126 PRGZ-01000 to PRGZ-03129

PRGZ-01000: 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-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-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: 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-03105: restoration of database files failed\n{0}: Cause: An attempt to migrate a database with zero downtime failed because the database files coult 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 Administrator's 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 Administrator's 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.