Oracle Error Messages: 10/16/11

LFI-00130: Input option specified on output only file.

LFI-00130: Input option specified on output only file.

Cause: The file was opened as output only but one of the input mode options (LFILRF_READ_NL or LFILRF_FORCE_NL) or was specified.

Action: Check to see how you intend to open this file and make the necessary changes.

LFI-00129: Invalid option string were specified on an input only file.

LFI-00129: Invalid option string were specified on an input only file.

Cause: The file was opened as input only but the output mode option LFILRF_ WR_ASIS or delete option LFLOPTY_DELETE was specified.

Action: Check to see how you intend to open this file and make the necessary changes.

LFI-00128: Carriage Control is only valid for Standard file objects.

LFI-00128: Carriage Control is only valid for Standard file objects.

Cause: The Carriage Control option is only valid for the standard file objects (LFISTDIN, LFISTDOUT, LFISTDERR). You may not specify this option for any other type of file.

Action: Choose between LFILRF_FIXED and LFILRF_VAR for the record format.

RMAN-20211: FROM TIME is before RESETLOGS time

RMAN-20211: FROM TIME is before RESETLOGS time

Cause: FROM TIME cannot be less than the database creation time or RESETLOGS time.

Action: Check the FROM TIME. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.

RMAN-20209: duplicate datafile name

RMAN-20209: duplicate datafile name

Cause: Two datafiles have the same name

Action: this is an internal error

RMAN-20208: UNTIL CHANGE is before RESETLOGS change

RMAN-20208: UNTIL CHANGE is before RESETLOGS change

Cause: UNTIL CHANGE cannot be less than the database RESETLOGS change.

Action: Check the UNTIL CHANGE. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.

RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time

RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS time

Cause: UNTIL TIME and RECOVERY WINDOW cannot be less than the database creation time or RESETLOGS time.

Action: Check the UNTIL TIME or RECOVERY WINDOW. If the database needs to be restored to an old incarnation, use the RESET DATABASE TO INCARNATION command.

RMAN-20206: log sequence not found in the repository

RMAN-20206: log sequence not found in the repository

Cause: The specified log sequence does not exists in log history of the current database incarnation

Action: check the thread# and sequence#

RMAN-20205: incomplete UNTIL clause

RMAN-20205: incomplete UNTIL clause

Cause: The sequence# was NULL

Action: this is an internal error

RMAN-20204: translation not started

RMAN-20204: translation not started

Cause: getDatafile procedure was called before translateTablespace

Action: this is an internal error

RMAN-20203: translation in progress

RMAN-20203: translation in progress

Cause: this procedure can not be called when name translation is in progress

Action: this is an internal error

RMAN-20202: tablespace not found in the recovery catalog

RMAN-20202: tablespace not found in the recovery catalog

Cause: the specified tablespace is not found in the recovery catalog

Action: make sure that the tablespace name is correct and that the recovery catalog is up-to-date

RMAN-20201: datafile not found in the recovery catalog

RMAN-20201: datafile not found in the recovery catalog

Cause: The specified datafile is not found in the recovery catalog

Action: make sure that the datafile name is correct and that the recovery catalog is up-to-date

RMAN-20039: format requires character when duplexing

RMAN-20039: format requires character when duplexing

Cause: SET_DUPLEX=ON was specified, but %c was not part of the format.

Action: Include %c in format, or use %U.

RMAN-20034: resync not needed

RMAN-20034: resync not needed

Cause: the control file has not changed since the previous resync

Action: nothing since the recovery catalog is in sync

RMAN-20033: control file sequence# too low

RMAN-20033: control file sequence# too low

Cause: the control file sequence is less than the one of the previous resync

Action: make sure that the right control file is used

RMAN-20032: checkpoint change# too low

RMAN-20032: checkpoint change# too low

Cause: the checkpoint change# is less than the one of the previous resync or the checkpoint change# is null

Action: make sure that the right control file is used

RMAN-20031: resync not started

RMAN-20031: resync not started

Cause: this procedure can only be called in a resync

Action: This is an internal error

RMAN-20030: resync in progress

RMAN-20030: resync in progress

Cause: this procedure can not be called while a resync is in progress

Action: This is an internal error

RMAN-20029: cannot make a snapshot control file

RMAN-20029: cannot make a snapshot control file

Cause: another operation that needs the snapshot control file is in progress

Action: try again later if necessary

RMAN-20011: target database incarnation is not current in recovery catalog

RMAN-20011: target database incarnation is not current in recovery catalog

Cause: the database incarnation that matches the resetlogs change# and time of the mounted target database control file is not the current incarnation of the database

Action: If reset database to incarnation lamp;lt;lamp;nbsp;keylamp;gt; was used to make an old incarnation current then restore the target database from a backup that matches the incarnation and mount it. You will need to do startup nomount before you can restore the control file using RMAN. Otherwise use reset database to incarnation lamp;lt;lamp;nbsp;keylamp;gt; make the intended incarnation current in the recovery catalog.

RMAN-20010: database incarnation not found

RMAN-20010: database incarnation not found

Cause: database incarnation does not match any database incarnation in the recovery catalog

Action: specify a valid database incarnation key

RMAN-20009: database incarnation already registered

RMAN-20009: database incarnation already registered

Cause: this incarnation is already registered in the recovery catalog

Action: No action is required.

RMAN-20006: target database name is missing

RMAN-20006: target database name is missing

Cause: target database instance is not started or db_name initialization parameter is not set

Action: startup the instance and make sure that db_name parameter is set

RMAN-20005: target database name is ambiguous

RMAN-20005: target database name is ambiguous

Cause: two or more databases in the recovery catalog match this name

Action: none

RMAN-20004: target database name does not match name in recovery catalog

RMAN-20004: target database name does not match name in recovery catalog

Cause: name of the target database doesn t match the one stored in the recovery catalog

Action: This is an internal error, call support.

RMAN-20003: target database incarnation not found in recovery catalog

RMAN-20003: target database incarnation not found in recovery catalog

Cause: resetlogs change# and or or time of the target database doesn t match any database incarnation in the recovery catalog.

Action: if target database was opened with resetlogs option then use reset database to register the new incarnation.

RMAN-20002: target database already registered in recovery catalog

RMAN-20002: target database already registered in recovery catalog

Cause: target database is already registered in the recovery catalog

Action: if the target database is really registered, there is no need to register it again. Note that the recovery catalog enforces that all databases have a unique DBID. If the new database was created by copying files from an existing database, it will have the same DBID as the original database and cannot be registered in the same recovery catalog.

RMAN-20001: target database not found in recovery catalog

RMAN-20001: target database not found in recovery catalog

Cause: target database is not found in the recovery catalog

Action: make sure that the target database is registered in the recovery recovery catalog

RMAN-20000: abnormal termination of job step

RMAN-20000: abnormal termination of job step

Cause: A job step encountered an error and could not recover. This error should be followed by other errors indicating the cause of the problem.

Action: Check the accompanying error.

RMAN-12020: error on step filtered for normal output string

RMAN-12020: error on step filtered for normal output string

Cause: This message is added when stacking errors for failed jobs after channel failover was performed. It will be filtered from normal output.

Action: No action is required.

RMAN-12018: channel string disabled, job failed on it will be run on another channel

RMAN-12018: channel string disabled, job failed on it will be run on another channel

Cause: This is an informational message displayed whenever a retriable error occurs for the job and there are channels available to run this step.

Action: No action is required.

RMAN-12017: could not locate pieces of backupset key string

RMAN-12017: could not locate pieces of backupset key string

Cause: No copies of the specified backupset key can be accessed on any of the allocated channels.

Action: Allocate additional channels on other nodes of the cluster, or, if the backup pieces have been deleted, use the CROSSCHECK BACKUP command to correct the recovery catalog entries.

RMAN-12016: using channel string

RMAN-12016: using channel string

Cause: This is an informational message only.

Action: No action is required.

RMAN-12015: configuration for string channel number is ignored

RMAN-12015: configuration for string channel number is ignored

Cause: This is an informational message only. Parallelism for the device is less than associated channel number.

Action: To use this configuration increase parallelism for this device. To clear this configuration use CONFIGURE CHANNEL... CLEAR command.

RMAN-12014: multiple records for default channel configuration for string found in catalog

RMAN-12014: multiple records for default channel configuration for string found in catalog

Cause: configuration for the channel is not consistent.

Action: re-run CONFIGURE CHANNEL command to configure the channel.

RMAN-12013: multiple records for string channel number found in catalog

RMAN-12013: multiple records for string channel number found in catalog

Cause: configuration for the channel is not consistent.

Action: re-run CONFIGURE CHANNEL command to configure this channel.

RMAN-12012: multiple records for string parallelism found in catalog

RMAN-12012: multiple records for string parallelism found in catalog

Cause: configuration for device parallelism is not consistent.

Action: re-run CONFIGURE PARALLELISM command for device to set parallelism.

RMAN-12011: multiple records for default device type found in catalog

RMAN-12011: multiple records for default device type found in catalog

Cause: configuration for default device type not consistent.

Action: re-run CONFIGURE DEFAULT DEVICE TYPE command to set device type.

RMAN-12010: automatic channel allocation initialization failed

RMAN-12010: automatic channel allocation initialization failed

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-12009: command aborted because some backup pieces could not be located

RMAN-12009: command aborted because some backup pieces could not be located

Cause: Same as 7008.

Action: Refer to 7008.

RMAN-12008: could not locate backup piece string

RMAN-12008: could not locate backup piece string

Cause: There was at least 1 backup set that could not be accessed by any of the allocated channels.

Action: Allocate additional channels on other nodes of the cluster

RMAN-12007: cannot allocate more than number channels

RMAN-12007: cannot allocate more than number channels

Cause: The maximum number of RMAN channels has been exceeded. Note that one channel is reserved for RMAN.

Action: Allocate fewer channels. Contact Oracle if you have a need for more channels in a single job.

RMAN-12005: error during channel cleanup

RMAN-12005: error during channel cleanup

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-12001: could not open channel string

RMAN-12001: could not open channel string

Cause: An ALLOCATE CHANNEL command could not be processed.

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

RMAN-12000: execution layer initialization failed

RMAN-12000: execution layer initialization failed

Cause: This message should be accompanied by other error message(s) indicating the cause of the error.

Action: Check the accompanying errors.

RMAN-11006: WARNING: test recovery results: string

RMAN-11006: WARNING: test recovery results: string

Cause: User called recover database with the test option

Action: None required

RMAN-11005: conflicting media information for piece string

RMAN-11005: conflicting media information for piece string

Cause: While restoring the specified backup piece, RMAN received conflicting information about the physical location of the piece from the Media Management software. This can cause poor restore performance.

Action: If RMAN does not parallelize the restore from all of the available channels, then you should contact the Media Management vendor.

RMAN-11004: format requires %%c when duplexing

RMAN-11004: format requires %%c when duplexing

Cause: SET_DUPLEX=ON was specified, but %c was not part of the format.

Action: Include %c in format, or use %U.

RMAN-11003: failure during parse or execution of SQL statement: string

RMAN-11003: failure during parse or execution of SQL statement: string

Cause: This is an informational message only.

Action: No action is required.

RMAN-11002: could not open a cursor to the target database

RMAN-11002: could not open a cursor to the target database

Cause: This is an informational message only.

Action: No action is required.

RMAN-11001: Oracle Error: string

RMAN-11001: Oracle Error: string

Cause: This is an informational message only.

Action: No action is required.

RMAN-11000: message number number not found in recovery manager message file

RMAN-11000: message number number not found in recovery manager message file

Cause: Recovery manager message file is out of date.

Action: Make sure that the recovery manager error message file is current and installed in the correct location.

RMAN-10041: Could not re-create polling channel context following failure.

RMAN-10041: Could not re-create polling channel context following failure.

Cause: The RPC polling context, which is required to test for RPC completion, failed and Recovery Manager could not re-create this channel. This message should be accompanied by other error messages indicating the cause of the error.

Action: If other error messages indicate a condition that can be corrected, do so, otherwise contact Oracle.

RMAN-10040: asynchronous support not detected, RMAN will run synchronously

RMAN-10040: asynchronous support not detected, RMAN will run synchronously

Cause: The database connection does not support asynchronous operation, so RMAN will not multi-task work among multiple channels. Multiple channels can still be allocated, but they will not run work concurrently.

Action: Use a connection type that supports asynchronous operations.

RMAN-10039: error encountered while polling for RPC completion on channel string

RMAN-10039: error encountered while polling for RPC completion on channel string

Cause: This error should be accompanied by other errors giving the cause of the polling error.

Action: Check the accompanying errors.

RMAN-10038: database session for channel string terminated unexpectedly

RMAN-10038: database session for channel string terminated unexpectedly

Cause: The database connection for the specified channel no longer exists. Either the session was terminated by some external means or the channel terminated because of an internal error.

Action: Check for an oracle trace file for detailed information on why the session terminated.