RMAN-05042: Error during import of metadata

RMAN-05042: Error during import of metadata

Cause: Import of metadata received an error from datapump.

Action: This message is accompanied by other error message(s) indicating the cause of the error.

RMAN-05041: Error during export of metadata

RMAN-05041: Error during export of metadata

Cause: Export of metadata received an error from datapump.

Action: This message is accompanied by other error message(s) indicating the cause of the error.

RMAN-05040: List of tablespaces that have been dropped from the target database:

RMAN-05040: List of tablespaces that have been dropped from the target database:

Cause: One or more tablespaces in the recovery set were not found in the controlfile of the target database.

Action: None. Informational message.

RMAN-05035: archive logs generated after SCN string not found in repository

RMAN-05035: archive logs generated after SCN string not found in repository

Cause: The repository did not have a record of archived logs containing the redo generated after the specified SCN.

Action: None. To avoid this message, perform a log switch if the database is in open mode.

RMAN-05034: Recovery must be done beyond SCN string to clear data files fuzziness

RMAN-05034: Recovery must be done beyond SCN string to clear data files fuzziness

Cause: The above SCN identifies the minimum SCN beyond which the media recovery must be performed on the specific data files to clear the media recovery fuzziness for all data files.

Action: None. This is an informational message displayed for PREVIEW option of the RESTORE command.

RMAN-05033: Media recovery start SCN is string

RMAN-05033: Media recovery start SCN is string

Cause: The above SCN would be starting media recovery SCN, if the specified files are restored.

Action: None. This is an informational message displayed for PREVIEW option of the RESTORE command.

RMAN-05032: data file string will be created automatically during restore operation

RMAN-05032: data file string will be created automatically during restore operation

Cause: The specified data file did not have an available backup.

Action: None. This is an informational message displayed for VALIDATE or PREVIEW option of the RESTORE command.

RMAN-05031: cannot specify UNDO TABLESPACES clause for normal recovery

RMAN-05031: cannot specify UNDO TABLESPACES clause for normal recovery

Cause: The UNDO TABLESPACES clause was specified for a normal recovery. It is only allowed for tablespace point in time recovery.

Action: Remove the UNDO TABLESPACES clause and re-run the RECOVER command.

RMAN-05030: CLONE clause cannot be used with Tablespace Point-in-Time Recovery

RMAN-05030: CLONE clause cannot be used with Tablespace Point-in-Time Recovery

Cause: The CLONE clause was specified for a Tablespace Point-in-Time Recovery (TSPITR).

Action: Remove the CLONE clause.

RMAN-05029: UNDO TABLESPACE clause is only valid for Tablespace Point-in-Time Recovery

RMAN-05029: UNDO TABLESPACE clause is only valid for Tablespace Point-in-Time Recovery

Cause: The UNDO TABLESPACE clause was specified for non-Tablespace Point-in-Time Recovery (TSPITR).

Action: Remove the UNDO TABLESPACE clause.

RMAN-05028: tablespace string

RMAN-05028: tablespace string

Cause: Accompanying message to 5026.

Action: See action of message 5026.

RMAN-05027: List of tablespaces expected to have UNDO segments

RMAN-05027: List of tablespaces expected to have UNDO segments

Cause: Accompanying message to 5026.

Action: See action of message 5026.

RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point in time

RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point in time

Cause: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified point-in-time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACES clause of the RECOVER command to specify the correct set of tablespaces.

Action: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified point-in-time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACES clause of the RECOVER command to specify the correct set of tablespaces.

RMAN-05025: tablespace string

RMAN-05025: tablespace string

Cause: Accompanying message to 5015.

Action: See action of message 5015.

RMAN-05024: List of tablespaces presumed to have UNDO segments

RMAN-05024: List of tablespaces presumed to have UNDO segments

Cause: Accompanying message to 5015.

Action: See action of message 5015.

RMAN-05023: TABLESPACE DESTINATION required

RMAN-05023: TABLESPACE DESTINATION required

Cause: A required TABLESPACE DESTINATION was not specified.

Action: Specify a TABLESPACE DESTINATION and retry the operation.

RMAN-05022: TRANSPORT TABLESPACE may not be used with user-managed auxiliary instance

RMAN-05022: TRANSPORT TABLESPACE may not be used with user-managed auxiliary instance

Cause: A user-managed auxiliary instance was specified.

Action: Retry the operation with an RMAN-managed auxiliary instance.

RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control file

RMAN-05021: this configuration cannot be changed for a BACKUP or STANDBY control file

Cause: The user attempted to modify the configuration which cannot be changed for a BACKUP or STANDBY control file while the mounted control file was either BACKUP or STANDBY. The following configurations can be changed only when connected to primary database instance that has CURRENT or CREATED control file type mounted: CONFIGURE RETENTION POLICY CONFIGURE EXCLUDE CONFIGURE ARCHIVELOG DELETION POLICY

Action: Connect to primary database instance and execute the command.

RMAN-05020: cannot specify AUXILIARY DESTINATION option for normal recovery

RMAN-05020: cannot specify AUXILIARY DESTINATION option for normal recovery

Cause: The AUXILIARY DESTINATION option was specified for a normal recovery. It is only allowed for tablespace point in time recovery.

Action: Remove the AUXILIARY DESTINATION option and re-run the RECOVER command.

RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile number

RMAN-05019: WARNING: no channel of required type allocated to recover copy of datafile number

Cause: A RECOVER COPY command could not proceed because incremental backup sets exist on a device type that has not been allocated.

Action: Use the LIST command to determine which device type is needed, then allocate a channel of that type.

RMAN-05018: some datafile copies cannot be recovered, aborting the RECOVER command

RMAN-05018: some datafile copies cannot be recovered, aborting the RECOVER command

Cause: This error message can follow one or more RMAN-5017 or RMAN-5019 error messages.

Action: See RMAN-5017 or RMAN-5019 error messages documentation for more information.

RMAN-05017: no copy of datafile number found to recover

RMAN-05017: no copy of datafile number found to recover

Cause: A RECOVER COPY command was not able to proceed because no copy of indicated file was found to recover. Possible causes include the following: 1. no copy of indicated file exists on disk that satisfy the criteria specified in the user s recover operands. 2. copy of indicated datafile exists on disk but no incremental backup was found to apply to the datafile copy.

Action: One of the following: 1. Use or correct TAG specification to recover a different datafile copy. 2. Use BACKUP FOR RECOVER OF COPY command to create necessary incremental backup or copy.

RMAN-05016: failover to previous backup

RMAN-05016: failover to previous backup

Cause: This is an informational message to indicate the RMAN could not successfully restore the files using the specified backups. An attempt was made to restore the datafiles or archivelogs or control file or SPFILE using a previous existing backup.

Action: See accompanying additional error messages indicating the cause of the failover.

RMAN-05015: WARNING: not enough information in recovery catalog for specified point in time recovery

RMAN-05015: WARNING: not enough information in recovery catalog for specified point in time recovery

Cause: The recovery catalog did not have information about the tablespaces with undo segements at the specified point-in-time. This happened because the current recovery catatog was not in use at the specified point-in-time. A list of tablespaces with undo segments was supplied.

Action: RMAN assumes that the current set of tablespaces with undo segments is the same set that was in use at the specified point-in-time. If the set of tablespaces with undo segments changes, the recovery fails. If recovery fails, use the optional UNDO TABLESPACES clause of the RECOVER command to specify the correct set of tablespaces.

RMAN-05014: tablespaces with undo segments were not found in recovery catalog

RMAN-05014: tablespaces with undo segments were not found in recovery catalog

Cause: The recovery catalog did not have information about tablespaces with undo segments.

Action: Manually specify the tablespaces with undo segments in the optional UNDO TABLESPACES clause of the RECOVER command.

RMAN-05013: auxiliary control filename string conflicts with a file used by the target database

RMAN-05013: auxiliary control filename string conflicts with a file used by the target database

Cause: RMAN is attempting to use the specified control filename for TSPITR as a restore destination in the auxiliary database, but this name is already in use by the target database.

Action: Set control_files parameter in the auxiliary instance to a name that does not conflict with a filename in use by the target database.

RMAN-05012: trying to start the Oracle instance without parameter files ...

RMAN-05012: trying to start the Oracle instance without parameter files ...

Cause: The instance could not be started because no default parameter file (either PFILE or SPFILE) could be found. The instance will be started in restricted mode with default parameters.

Action: None -this is an informational message.

RMAN-05011: auxiliary instance must be in nomount state for TSPITR

RMAN-05011: auxiliary instance must be in nomount state for TSPITR

Cause: The Auxiliary instance was not in nomount state.

Action: Open the auxiliary instance in nomount state.

RMAN-05010: target database must be opened in READ WRITE mode for TSPITR

RMAN-05010: target database must be opened in READ WRITE mode for TSPITR

Cause: The target database was not opened in read write mode.

Action: Open the database in read write mode.

RMAN-05009: Block Media Recovery requires Enterprise Edition

RMAN-05009: Block Media Recovery requires Enterprise Edition

Cause: The BLOCKRECOVER command was specified.

Action: Remove the BLOCKRECOVER command.

RMAN-05008: SET NEWNAME TO NEW not allowed (datafile string)

RMAN-05008: SET NEWNAME TO NEW not allowed (datafile string)

Cause: SET NEWNAME ... TO NEW is not allowed with TSPITR.

Action: Set the new name to a specific file name and retry.

RMAN-05007: no channel allocated

RMAN-05007: no channel allocated

Cause: A command was entered that requires a channel, and no channel is allocated.

Action: Use ALLOCATE CHANNEL before using the command

RMAN-05006: cannot recover clone standby single tablespaces

RMAN-05006: cannot recover clone standby single tablespaces

Cause: Standby recover can only be performed for the whole database.

Action: Change the tablespace list to a database specification.

RMAN-05005: point-in-time recovery is not allowed for re-created tablespace string

RMAN-05005: point-in-time recovery is not allowed for re-created tablespace string

Cause: The requested tablespace has been re-created and is not allowed in point-in-time recovery.

Action: Remove the indicated tablespace from the recovery set and retry the operation.

RMAN-05004: target database log mode is NOARCHIVELOG

RMAN-05004: target database log mode is NOARCHIVELOG

Cause: An attempt was made to apply TSPITR to a database that is in NOARCHIVELOG mode.

Action: If all required archive log files are available to TSPITR, alter the target database log mode to ARCHIVELOG and retry the TSPITR operation. Otherwise, TSPITR cannot be applied to this database.

RMAN-05003: point-in-time recovery is not allowed for tablespace string

RMAN-05003: point-in-time recovery is not allowed for tablespace string

Cause: The SYSTEM tablespace or a tablespace containing rollback segments is not allowed in point-in-time recovery.

Action: Remove the indicated tablespace from the recovery set and retry the operation.

RMAN-05002: aborting point-in-time tablespace recovery

RMAN-05002: aborting point-in-time tablespace recovery

Cause: Previously encountered error(s) were issued which require corrective action.

Action: Resolve the error conditions, and then re-issue the RECOVER command.

RMAN-05001: auxiliary filename string conflicts with a file used by the target database

RMAN-05001: auxiliary filename string conflicts with a file used by the target database

Cause: RMAN is attempting to use the specified filename as a restore destination in the auxiliary database, but this name is already in use by the target database.

Action: Use the CONFIGURE AUXNAME command to specify a name for the datafile that does not conflict with a filename in use by the target db.

RMAN-05000: CONFIGURE AUXNAME required for datafile string

RMAN-05000: CONFIGURE AUXNAME required for datafile string

Cause: Either: -) The control file mounted by the auxiliary database does not have an entry for this datafile, therefore filename conversion is not possible. -) A COPY DATAFILE TO AUXNAME command was issued, but no auxname was set for this datafile.

Action: Use the CONFIGURE AUXNAME command to specify a filename that the auxiliary database can use as a restore destination.

RMAN-04033: cannot open auxiliary parameter file string

RMAN-04033: cannot open auxiliary parameter file string

Cause: An auxiliary parameter file was specified with SET AUXILIARY INSTANCE PARAMETER FILE command but the specified file cannot be found.

Action: Set the parameter file to an existen file or retry the command without setting AUXILIARY INSTANCE PARAMETER FILE.

RMAN-04032: using contents of file string

RMAN-04032: using contents of file string

Cause: The specified file was included as part of the auxiliary database parameter file. This is an informational message.

Action: No action is required.

RMAN-04031: initialization parameters used for automatic instance: string

RMAN-04031: initialization parameters used for automatic instance: string

Cause: This is an informational message only.

Action: No action is required.

RMAN-04027: unable to write to a temporary file: string

RMAN-04027: unable to write to a temporary file: string

Cause: Writing to a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar).

Action: Verify and free some system resources memory and try again.

RMAN-04026: unable to open a temporary file: string

RMAN-04026: unable to open a temporary file: string

Cause: Opening of a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar).

Action: Verify and free some system resources memory and try again.

RMAN-04025: unable to generate a temporary file

RMAN-04025: unable to generate a temporary file

Cause: Creation of a temporary file failed. If could be that the system does not have enough resources (disk space, memory or similar).

Action: Verify and free some system resources memory and try again.

RMAN-04024: starting Oracle instance without parameter file for retrival of spfile

RMAN-04024: starting Oracle instance without parameter file for retrival of spfile

Cause: The instance could not be started because no default parameter file (either PFILE or SPFILE) could be found. The instance will be started in restricted mode with default parameters.

Action: None -this is an informational message.

RMAN-04022: target database mount id string does not match channel s mount id string

RMAN-04022: target database mount id string does not match channel s mount id string

Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database.

Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command.

RMAN-04021: target database DBID string does not match channel s DBID string

RMAN-04021: target database DBID string does not match channel s DBID string

Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database.

Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command.

RMAN-04020: target database name string does not match channel s name: string

RMAN-04020: target database name string does not match channel s name: string

Cause: The CONNECT clause in the ALLOCATE command has resulted in a connection to a database which is not the same as the one used to connect to the target database.

Action: Verify that the CONNECT string connects to the same database as the one specified in the TARGET connection for the CONNECT command.

RMAN-04017: startup error description: string

RMAN-04017: startup error description: string

Cause: of failure.

Action: No action is required.

RMAN-04016: could not get OCI error handle

RMAN-04016: could not get OCI error handle

Cause: An error was received while initializing the OCI layer.

Action: This error should not normally happen. Contact Oracle Customer Support.

RMAN-04015: error setting target database character set to string

RMAN-04015: error setting target database character set to string

Cause: An error was received while setting the session character set in the target database.

Action: This error should not normally happen. Contact Oracle Customer Support.

RMAN-04014: startup failed: string

RMAN-04014: startup failed: string

Cause: The database failed to startup.

Action: The cause of the failure is included in the error message. Correct the cause of the failure and retry the startup command.

RMAN-04013: must connect before startup

RMAN-04013: must connect before startup

Cause: A STARTUP command was attempted before connecting to the database.

Action: Connect to database before attempting STARTUP command.

RMAN-04012: auxiliary database Password:

RMAN-04012: auxiliary database Password:

Cause: No password was provided for the auxiliary database.

Action: Provide auxiliary database password.

RMAN-04011: recovery catalog database Password:

RMAN-04011: recovery catalog database Password:

Cause: No password was provided for the recovery catalog database.

Action: Provide recovery catalog database password.

RMAN-04010: target database Password:

RMAN-04010: target database Password:

Cause: No password was provided for the target database.

Action: Provide target database password.

RMAN-04009: WARNING from auxiliary database: string

RMAN-04009: WARNING from auxiliary database: string

Cause: Non fatal Oracle error signaled by auxiliary database. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-04008: WARNING from target database: string

RMAN-04008: WARNING from target database: string

Cause: Non fatal Oracle error signaled by target database. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-04007: WARNING from recovery catalog database: string

RMAN-04007: WARNING from recovery catalog database: string

Cause: Non fatal Oracle error signaled by catalog database. This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.