Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8 Error Messages Release 8.0 A54625_01 |
|
The messages listed in this chapter are displayed with the prefix LFI and are generated by the CORE utility in the Oracle Server. These messages indicate a problem with BFILE usage and will usually appear with an Oracle Server (ORA-XXXXX) error message. If you cannot pinpoint the problem after reading the LFI and ORA errors, record the errors and contact Oracle Worldwide Support.
This chapter presents the messages, the likely cause(s) of the event(s) generating each message, and recommended corrective action.
Cause: The File I/O package failed in trying to dynamically allocate memory. function name is used for additional comments to indicate where, when, and why the error occurred.
Action: Perform whatever actions necessary to make more memory available to the executing program.
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.
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.
Cause: The function was called with an invalid parameter.
Action: Check the function call to ensure that the correct parameters are being passed.
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).
Cause: The buffer seek operation failed. Probably due to incorrect parameters or flags.
Action: Check syntax of the seek command and retry the operation.
Cause: The buffer read operation failed. Probably due to incorrect parameters or flags.
Action: Check syntax of the read command and retry the operation.
Cause: One of the following might have caused the error:
Action: Check the format of the current path and the new directory; check that the name object was initialized properly.
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.
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.
Cause: The flags specified for the open indicate that the file exists. However, the file does not exist.
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.
Cause: Either:
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.
Cause: The Buffer Manager initialization routine failed; probably because memory was exhausted.
Action: See the accompanying error messages for more information.
Cause: Probably do to the buffer flush failing.
Action: See the accompanying error messages for more information.
Cause: The file close operation failed.
Action: See the accompanying error messages for more information.
Cause: The root filename that was given to lfimknam() is not in a format that this platform can process.
Action: Check the format of the filename and retry the operation.
Cause: Both the LFILFA_SEQ (sequential) and LFILFA_RANDOM (random) flags were specified during the file object creation. This is not allowed. Only one of the two can be specified.
Action: Choose how you wish to access the file. If you choose random you can still access sequentially by not using the repositioning functions.
Cause: Neither LFILFA_SEQ (sequential) or LFILFA_RANDOM (random) were specified during file object creation.
Action: The default is sequential but this should be explicitly set.
Cause: The LFILFA_RANDOM flag was specified on a file that was not organized into fixed-length records. Random access is allowed only on fixed-length record files.
Action: Determine if the organization of your data needs to be in variable-length records and if you need to have random access to the file. If both conditions are true then you might need to buffer the entire file or enough of it to remove your need for random access. Another option is to close and rescan the file although this is not the optimal solution.
Cause: Both LFILRF_FIXED (fixed) and LFILRF_VAR (variable) were specified during file object creation. Only one of the two is allowed for a given file.
Action: Determine how the file is organized and choose the option that matches.
Cause: Neither LFILRF_FIXED (fixed) and LFILRF_VAR (variable) were specified for record format. One of the two must be specified for each file.
Action: The default is LFILRF_VAR, but this should be explicitly set during file object creation.
Cause: The file object was created without an open type (that is, LFILOPTY_INPUT, LFILOPTY_OUTPUT, etc.).
Action: Decide how the file should be accessed and specify one of the open types.
Cause: Unable to perform an LFI operation on a file object for the given reason.
Action: Take the appropriate corrective measure. For example if a file is supposed to be opened before the operation can be performed, client code will need to open the file first.
Cause: Unable to perform an LFI operation on a name object for the given reason.
Action: Take the appropriate corrective measure.
Cause: The file does not exist.
Action: Check to make sure the file exists and retry the operation.
Cause: The buffer that was passed is not large enough.
Action: Allocate a larger buffer and retry the operation.
Cause: The file does not exist.
Action: Check to make sure the file exists and retry the operation.
Cause: The file being read from may no longer be open.
Action: See the accompanying error messages for more information.
Cause: The buffer manager is probably unable to read from the underlying file.
Action: See the accompanying error messages for more information.
Cause: An error condition arises in calling an OSD function. This message occurs if calls to malloc or free functions failed.
Action: Contact Oracle Worldwide Support.
Cause: The function fseek() returned an error condition.
Action: Contact Oracle Worldwide Support.
Cause: The function fclose() returned an error condition.
Action: Contact Oracle Worldwide Support.
Cause: Call to fopen() failed.
Action: Contact Oracle Worldwide Support.
Cause: Call to fread() failed.
Action: Contact Oracle Worldwide Support.
Action: Contact Oracle Worldwide Support.
Cause: The ftell() function returned an error.
Action: Contact Oracle Worldwide Support.
Cause: The lseek() function returned an error.
Action: Contact Oracle Worldwide Support.
