Oracle Error Messages: 10/13/11

LFI-00111: No other flags allowed in fixed length format.

LFI-00111: No other flags allowed in fixed length format.

Cause: The function lfigfo() was called with an invalid File ID Descriptor. The valid File ID Descriptors are LFISTDIN, LFISTDOUT, and LFISTDERR.

Action: Check the call to lfigfo() to make sure it is correct.

LFI-00110: Unable to initialize the Buffer Manager.

LFI-00110: Unable to initialize the Buffer Manager.

Cause: The Buffer Manager initialization routine failed; probably because memory was exhausted.

Action: See the accompanying error messages for more information.

LFI-00109: Unable to open file (string((string(. string.

LFI-00109: Unable to open file (string((string(. string.

Cause: Either: the process does not have the proper access rights to open the file the file is already open

Action: Check to make sure the proper access permissions are assigned. If they are and the file still cannot be opened, then contact Oracle Worldwide Support.

LFI-00108: Open expect the file (string((string( to exist.

LFI-00108: Open expect the file (string((string( to exist.

Cause: The flags specified for the open indicate that the file the file to exist and it does not.

Action: Check to make sure that the options that were specified for the file are correct and that you expect that the file should exist. If so then find out why the file doesn t.

LFI-00107: Open does not expect the file (string((string( to exist.

LFI-00107: Open does not expect the file (string((string( to exist.

Cause: The flags specified for the open indicate that the file does not exist. However, the file does exist.

Action: Check to make sure that the options that were specified for the file are correct and that you do not expect that the file should exist. If so then find out why the file does exist.

LFI-00106: Path object holds more than one path.

LFI-00106: Path object holds more than one path.

Cause: The path object passed to lfippth() holds more than one path.

Action: Make sure that the path object used in lfippth() holds only one path.

LFI-00105: Unable to add path.

LFI-00105: Unable to add path.

Cause: One of the following might have caused the error: the current path might not be in the proper format the directory might not be in the proper format the name object might not have been initialized properly

Action: Check the format of the current path and the new directory; check that the name object was initialized properly.

LFI-00104: Read operation failed.

LFI-00104: Read operation failed.

Cause: The buffer read operation failed. Probably due to incorrect parameters or flags.

Action: Check syntax of the read command and retry the operation.

LFI-00103: Seek operation failed.

LFI-00103: Seek operation failed.

Cause: The buffer seek operation failed. Probably due to incorrect parameters or flags.

Action: Check syntax of the seek command and retry the operation.

LFI-00102: Unable to seek in sequentially accessed file.

LFI-00102: Unable to seek in sequentially accessed file.

Cause: The file was opened with the flag LFILFA_SEQ for sequential file operations. Use seek only on files that are opened with the LFILFA_RANDOM flag for random access.

Action: Check to see how the file is being opened and accessed and make the two operations consistent (that is, make them both operations either sequential or random).

LFI-00101: Write failed, file cannot be written to.

LFI-00101: Write failed, file cannot be written to.

Cause: The buffer write operation failed. Possibly due to incorrect parameters being passed in.

Action: Check the underlying error for more information.

LFI-00100: Unable to perform operation, file not opened in string.

LFI-00100: Unable to perform operation, file not opened in string.

Cause: The file has not been successfully opened at the time the operation is attempted.

Action: Check to make sure that the file exists (for read) or that the program has access to the write a file (for write). It is also possible that the file was just never opened

LFI-00008: SLTS s initializing or terminating mutex failed for string.

LFI-00008: SLTS s initializing or terminating mutex failed for string.

Cause: SLTS s call return failure in function %s .

Action: Contact the appropriate development group.

LFI-00007: NLSRTL s call failed. string.

LFI-00007: NLSRTL s call failed. string.

Cause: LX calls return failure

Action: Check if our parameters are correct. Contact the appropriate group immediately if we parameters are valid.

LFI-00006: Invalid parameter to function string.

LFI-00006: Invalid parameter to function string.

Cause: The function was called with an invalid parameter.

Action: Check the function call to make sure that the correct parameters are being passed.

LFI-00005: Free some memory failed in string.

LFI-00005: Free some memory failed in string.

Cause: A call to free some memory in function function name has failed.

Action: See the accompanying error messages for more information and contact Oracle Worldwide Support immediately.

LFI-00004: Call to string failed.

LFI-00004: Call to string failed.

Cause: A function call has failed. This error is a generic message to show that the exception has occurred in a particular function function name. This allows the client to know the trace runtime calling sequence by examining the exception stack.

Action: See the accompanying error messages for more information.

LFI-00003: Internal exception code. icode = (string(, (string(.

LFI-00003: Internal exception code. icode = (string(, (string(.

Cause: Unknown - indicated by parameters. The first %s gives the internal exception code; the second is for any other additional comments.

Action: Report to the appropriate development group

LFI-00002: Out of memory. string

LFI-00002: Out of memory. string

Cause: The File IO package failed in trying to dynamically allocate memory. function name is used for additional comments to indicate where, when and why the error occured.

Action: Perform whatever actions necessary to make more memory available to the executing program.

LRM-00123: invalid character number found in the input file

LRM-00123: invalid character number found in the input file

Cause: A character that is invalid was found in the input file.

Action: Specify an input file that contains only valid characters.

LRM-00122: value string for string must be between number and number

LRM-00122: value string for string must be between number and number

Cause: The value of the parameter is not within the legal range.

Action: Specify a value that is within the legal range.

LRM-00121: string is not an allowable value for string

LRM-00121: string is not an allowable value for string

Cause: The value is not a legal value for this parameter.

Action: Refer to the manual for allowable values.

LRM-00120: string is not a legal Oracle number for string

LRM-00120: string is not a legal Oracle number for string

Cause: The value is not a valid Oracle number.

Action: Refer to the manual for allowable Oracle number values.

LRM-00119: unable to obtain a valid value for string

LRM-00119: unable to obtain a valid value for string

Cause: No valid value was obtained for this parameter.

Action: Rerun the application and enter a valid value.

LRM-00118: syntax error at string at the end of input

LRM-00118: syntax error at string at the end of input

Cause: A syntax error was detected.

Action: Change the input so that the correct syntax is used.

LRM-00117: syntax error at string at the start of input

LRM-00117: syntax error at string at the start of input

Cause: A syntax error was detected.

Action: Change the input so that the correct syntax is used.

LRM-00116: syntax error at string following string

LRM-00116: syntax error at string following string

Cause: A syntax error was detected.

Action: Change the input so that the correct syntax is used.

LRM-00115: error when processing an environment variable

LRM-00115: error when processing an environment variable

Cause: A problem occurred when processing an environment variable.

Action: Examine the additional error messages and correct the problem.

LRM-00114: error when processing from command line

LRM-00114: error when processing from command line

Cause: A problem occurred when processing the command line.

Action: Examine the additional error messages and correct the problem.

LRM-00113: error when processing file string

LRM-00113: error when processing file string

Cause: A problem occurred when processing this file.

Action: Examine the additional error messages and correct the problem.

LRM-00112: multiple values not allowed for parameter string

LRM-00112: multiple values not allowed for parameter string

Cause: An attempt was made to specify multiple values for a parameter which can take only one value.

Action: Do not specify more than one value for this parameter.

LRM-00111: no closing quote for value string

LRM-00111: no closing quote for value string

Cause: A quoted string was started but not finished.

Action: Put a closing quote in the proper location.

LRM-00110: syntax error at string

LRM-00110: syntax error at string

Cause: A syntax error was detected.

Action: Change the input so that the correct syntax is used.

LRM-00109: could not open parameter file string

LRM-00109: could not open parameter file string

Cause: The parameter file does not exist.

Action: Create an appropriate parameter file.

LRM-00108: invalid positional parameter value string

LRM-00108: invalid positional parameter value string

Cause: An invalid positional parameter value has been entered.

Action: Remove the invalid positional parameter.

LRM-00107: parameter name abbreviation string is not unique

LRM-00107: parameter name abbreviation string is not unique

Cause: The given abbreviation was not unique.

Action: Use a longer abbreviation to make the parameter name unique.

LRM-00106: out of memory

LRM-00106: out of memory

Cause: The operating system has run out of memory.

Action: Take action to make more memory available to the program.

LRM-00105: string is not a legal Boolean for string

LRM-00105: string is not a legal Boolean for string

Cause: The value is not a valid Boolean.

Action: Refer to the manual for allowable Boolean values.

LRM-00104: string is not a legal integer for string

LRM-00104: string is not a legal integer for string

Cause: The value is not a valid integer.

Action: Specify only valid integers for this parameter.

LRM-00103: string contains an illegal integer radix for string

LRM-00103: string contains an illegal integer radix for string

Cause: An illegal integer radix specification was found.

Action: Only d , h , D , and H may be used as radix specifications.

LRM-00102: string is not in the legal range for string

LRM-00102: string is not in the legal range for string

Cause: The value of the parameter is not within the legal range.

Action: Refer to the manual for the allowable values for this parameter.

LRM-00101: unknown parameter name string

LRM-00101: unknown parameter name string

Cause: The parameter name was misspelled.

Action: Spell the parameter name correctly.

LRM-00100: internal error (number(

LRM-00100: internal error (number(

Cause: An internal error has occurred.

Action: Contact Oracle Support Services and report the error.

RMAN-20507: some targets are remote - aborting restore

RMAN-20507: some targets are remote - aborting restore

Cause: during the restore process, one or more backup files were unavailable locally for the restore operation.

Action: This message should be accompanied with the list of remote backup files. Recall these backups from remote location and retry the RESTORE command.

RMAN-20506: no backup of archivelog found

RMAN-20506: no backup of archivelog found

Cause: during the recover process, no backup was found from which the archivelogs could be restored.

Action: this message should be followed by a list of missing archivelogs. Please make the necessary archivelog backups available and try again.

RMAN-20505: create datafile during recovery

RMAN-20505: create datafile during recovery

Cause: applying of archived log caused a create datafile redo-entry to to terminate recovery.

Action: none. This message is never displayed. RMAN automatically detects this case and creates the datafile.

RMAN-20504: corruption list not found in recovery catalog

RMAN-20504: corruption list not found in recovery catalog

Cause: corruption list is empty

Action: make sure that one or more blocks are marked corrupted in v$copy_ corruption and v$backup_corruption and recovery catalog is up-to-date.

RMAN-20503: DELETE cannot delete expired objects - run CROSSCHECK or DELETE EXPIRED

RMAN-20503: DELETE cannot delete expired objects - run CROSSCHECK or DELETE EXPIRED

Cause: A DELETE command was run without EXPIRED option, but the object doesn t exist. This means the recovery catalog or control file is out of sync with reality.

Action: Run CROSSCHECK.

RMAN-20502: DELETE EXPIRED cannot delete objects that exist - run CROSSCHECK

RMAN-20502: DELETE EXPIRED cannot delete objects that exist - run CROSSCHECK

Cause: A DELETE EXPIRED command was run, but the object was actually found to exist. This means the recovery catalog or control file is out of sync with reality.

Action: Run CROSSCHECK.

RMAN-20501: redo logs from parent database incarnation cannot be applied

RMAN-20501: redo logs from parent database incarnation cannot be applied

Cause: A RESTORE or RECOVER of a datafile was requested, but recovery of the datafile would require applying redo logs that were generated before the most recent OPEN RESETLOGS.

Action: If a full backup or datafile copy from the current database incarnation exists, ensure that it is marked AVAILABLE, and that a channel of the correct device type is allocated. It may also be necessary to remove the FROM BACKUPSET or FROM DATAFILECOPY or FROM TAG operands if these have been specified.

RMAN-20401: script already exists

RMAN-20401: script already exists

Cause: a CREATE SCRIPT was issued, but a script with the specified name already exists.

Action: use a different name or use REPLACE SCRIPT.

RMAN-20311: ambiguous proxy copy handle

RMAN-20311: ambiguous proxy copy handle

Cause: more than one proxy copy in the recovery catalog matches the specified handle

Action: use the proxy copy key to uniquely specify the proxy copy

RMAN-20310: proxy copy not found in the recovery catalog

RMAN-20310: proxy copy not found in the recovery catalog

Cause: the specified proxy copy is not in the recovery catalog or it has been marked deleted

Action: check the proxy copy handle or key

RMAN-20299: DBMS_RCVMAN package not compatible with the recovery catalog

RMAN-20299: DBMS_RCVMAN package not compatible with the recovery catalog

Cause: The version of the recovery catalog tables does not work with this version of the DBMS_RCVMAN package.

Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version.

RMAN-20298: DBMS_RCVCAT package not compatible with the recovery catalog

RMAN-20298: DBMS_RCVCAT package not compatible with the recovery catalog

Cause: The version of the recovery catalog tables does not work with this version of the DBMS_RCVCAT package.

Action: Check that the recovery catalog packages and schema are installed correctly. The UPGRADE CATALOG command can be used to upgrade the recovery catalog tables and packages to the most current version.

RMAN-20280: too many device types

RMAN-20280: too many device types

Cause: more than 8 device types were allocated

Action: make sure that the job allocates at most 8 different device types

RMAN-20272: no parent backup found for the incremental backup

RMAN-20272: no parent backup found for the incremental backup

Cause: no available backup or copy that could be used as the parent of the incremental backup was found in the recovery catalog.

Action: take a level 0 backup or copy of the datafile first