Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
This chapter lists messages generated by the external tables feature. For more information about the external tables feature, refer to Oracle9i Database Utilities.
Cause: An attempt to load parser package returned an error indication.
Action: This message should be accompanied by other error messages indicating the cause of the error.
Cause: An error was encountered while attempting to initialize the XAD package.
Action: This message should be accompanied by other error messages indicating the cause of the error.
Cause: The parser detected a syntax error.
Action: This message should be accompanied by other error messages indicating the cause of the error.
Cause: An integer field was specified with an invalid length. The only supported lengths for binary integer fields are 1, 2, 4, and 8.
Cause: An unknown escape sequence was specified to the parser. An escape sequence is a backslash followed by a character.
Action: Consult the documentation for a list of allowable control characters.
Cause: An internal XAD error occurred.
Action: Contact Oracle Support Services.
Cause: A fatal error has occurred.
Action: This message should be accompanied by other error messages indicating the cause of the error.
Cause: An error was signalled during parsing of the access parameters.
Action: This message should be accompanied by other error messages indicating the cause of the error.
Cause: This is an informational message indicating the line and column where a syntax error was detected.
Cause: This is an informational message indicating the identifier token that caused a syntax error.
Cause: The kupxx.msb file is not the correct version.
Action: Check that the installation was done correctly.
Cause: An illegal punctuation character was encountered.
Action: Remove the illegal character.
Cause: This is probably caused by failure to supply the closing quote for a quoted string.
Action: Correct the input.
Cause: An input character that is neither an alpha, digit, or punctuation was encountered.
Action: Remove the offending character.
Cause: A quoted string longer than 2000 bytes was encountered.
Action: This may be caused by a missing closing quote. If so, then add the missing quote. Otherwise, shorten the string.
Cause: A token longer than 1000 bytes was encountered.
Action: Tokens must be separated by whitespace or punctuation. Either add the missing whitespace or punctuation, or shorten the token.
Cause: A line longer than 500 bytes was encountered.
Action: Break the line up into shorter lines.
Cause: This message should be accompanied by other error messages indicating the cause of the error.
Action: Check the accompanying errors.
Cause: Error in specifying position for the specified field in the access parameters.
Action: Check that the specified end position is greater than the specified start position.
Cause: The number of bytes occupied by the field as specified by the starting offset and ending offset of the field is not the same as the number of bytes specified for the datatype of the field.
Action: Verify that the specified absolute begin/end positions match the length of the field.
Cause: The position of field was specified with a relative start and an absolute end.
Action: Use relative end with relative start.
Cause: The number of bytes specified by the relative end position for the field does not match the number of bytes in the datatype.
Action: Correct either the datatype length or the relative end position.
Cause: Error attempting to retrieve information for the character set.
Action: Verify that the character set name is valid.
Cause: A byte range specified a start position that comes after the end position.
Action: Verify the start and end positions are correctly specified.
Cause: An error occurred while trying to obtain column parameters.
Action: Contact Oracle Support Services.
Cause: An error occurred while trying to obtain column name.
Action: Contact Oracle Support Services.
Cause: An error occurred while trying to obtain database column type.
Action: Contact Oracle Support Services.
Cause: An error occurred while trying to obtain database column size.
Action: Contact Oracle Support Services.
Cause: An error occurred while trying to obtain database column precision.
Action: Contact Oracle Support Services.
Cause: An error occurred while trying to obtain database column scale.
Action: Contact Oracle Support Services.
Cause: An error occurred while trying to obtain a datetime column precision value.
Action: Contact Oracle Support Services.
Cause: An error occurred while trying to obtain database column precision.
Action: Contact Oracle Support Services.
Cause: A record format of FIXED was specified with a length of 0.
Cause: A record format of VARIABLE was specified with a length of 0.
Cause: An empty delimiter string was specified for a record delimiter.
Action: Specify the string used to delimiter records.
Cause: A WHEN, NULLIF, or DEFAULTIF clause referenced a field that doesn't exist in the data file.
Cause: The field specified in the data source that contains the name of the lob file for the record could not be identified.
Cause: Error converting a date format string into an internal representation.
Action: Verify that the date format strings specified in the access parameters are valid.
Cause: An unexpected error occurred while preparing the file.
Action: Contact Oracle Support Services.
Cause: An error occurred while attempting to open the specified file. This message should be followed by another message with more information about the error.
Action: See the error that follows to determine the action to be taken.
Cause: An error occurred while retrieving the number of bytes in the specified file.
Action: See the error that follows to determine the action to be taken.
Cause: An error occurred while closing the specified file.
Action: See the error that follows to determine the action to be taken.
Cause: An error occurred while reading the specified file.
Action: See the error that follows to determine the action to be taken.
Cause: A file operation succeeded.
Action: No action required.
Cause: An operation on a file failed. The file is named in the message preceeding this one.
Action: See the subsequent message for more information about the error.
Cause: The end of file was reached for a file. The file is named in the message preceding this one.
Action: See the message that follows this one for more information.
Cause: Acess to a file was denied. The file is named in the message preceding this one.
Action: See the message that follows for more information. Verify that the correct files are being used and that the appropriate access is allowed to those files.
Cause: An internal error caused a data structure associated with the file to become corrupt.
Action: Contact Oracle Support Services.
Cause: A file operation failed because a file does not exist. The message preceding this message contains the name of the file.
Action: Verify that the correct file name was specified.
Cause: An operation on a file failed because the file system is full. The message preceding this one contains the name of the file.
Action: Free space on the file system or move the file to a different file system.
Cause: Size of a file is too large.
Action: Break the file up into smaller files.
Cause: Internal SLF component was unable to complete an operation because of a system error.
Action: The message displayed before this message describes the operation that was being performed when the error occurred.
Cause: An invalid parameter was passed in a call to the internal SLF component.
Action: Contact Oracle Support Services.
Cause: Internal SLF component encountered an internal error.
Action: Contact Oracle Support Services.
Cause: Internal SLF component returned an unknown error code.
Action: Contact Oracle Support Services.
Cause: An error occurred. This message contains the message associated with this error that was returned by the operating system. The message displayed before this one should indicate the operation that failed.
Cause: An incomplete record was found at the end of the file.
Action: Verify the file is not corrupt or missing data.
Cause: A record in a VAR file has a length field containing either no numeric characters or non-numeric characters.
Action: Verify that the records in the file have the correct specified length.
Cause: a record in the data source was longer than the maximum data size supported. The number reported is the maximum supported size of a record.
Cause: There was an error trying to find the contents of the specified field in a record.
Action: This message should be followed by another message containing more specific information about the cause of the error.
Cause: The position of the start of a field is before the start of a record. This can occur if a negative number is used to indicate the relative start of a field.
Action: Verify that the definition of the layout of fields in the data file is correct.
Cause: This can happen when specifying either absolute or relative positioning for a field.
Action: Verify that the definition of the layout of fields in the data file is correct. If it is valid for fields at the end of the record to be missing, then use the MISSING FIELD VALUES ARE NULL clause in the access parameters.
Cause: The end of the field comes after the start of the field. This can happen if the field is defined with a relative start position and an absolute end position.
Action: Verify that the definition of the layout of fields in the data file is correct.
Cause: This can happen when specifying either absolute or relative positioning for a field.
Action: Verify that the definition of the layout of fields in the data file is correct.
Cause: The character field in the record is larger than the maximum length specified.
Action: Make sure the definition of the layout of the fields in the data file is correct. Also make sure the correct maximum size was specified for a character datatype.
Cause: The character length portion of the field could not be converted to a number. This message is followed by another message with information on why the conversion failed.
Action: Make sure the data is correct. Also verify the specified datatypes for the fields are correct.
Cause: An attempt to convert a character string to a number failed because the value of the number in the string was too large.
Cause: An attempt to convert a character string to a number failed because non-numeric characters were found.
Cause: An internal error occurred while parsing a field.
Action: Contact Oracle Support Services.
Cause: The beginning enclosure was not found for a field that is enclosed by delimiters.
Action: Verify that the data is correct. Also verify that the correct enclosing delimiters were specified and whether the enclosing delimiter should be optional.
Action: Verify that the data is correct. Also verify that the correct enclosing delimiters were specified.
Cause: The terminator for the field is missing.
Action: Verify that the records are formatted correctly.
Cause: an unexpected error condition was detected.
Action: contact Oracle Support Services.
Cause: An error occurred while trying to find path containing the file.
Action: This message should be followed by another message with more information about the error.
Cause: The file was not found in the specified directory.
Action: Verify that the correct file and directory names were specified.
Cause: An unexpected error occurred while trying to form a file name.
Cause: A column in the external table was not found in the access parameters that define the contents of the data source.
Action: Verify that the external table is defined correctly and that the abstract parameters are also correct.
Cause: An attempt to position a file to an absolute file offset failed.
Action: See messages that follow for more information.
Cause: An OCI call returned a status that cannot be handled.
Action: Contact Oracle Support Services.
Cause: An error occurred while trying to extract a record from the data source.
Action: Examine the log file for more messages about the error.
Cause: An unexpected or unhandled error occurred while getting a record from the data source.
Action: Contact Oracle Support Services.
Cause: This is an informational message displayed whenever the WHEN clause has been satisfied. If a DISCARD file has been specified for the operation, then the record will be written to that file.
Action: No action required.
Cause: An error occurred while trying to allocate memory. This is likely caused by insufficient memory.
Action: Reconnect to the instance and retry the operation.
Cause: An error occurred while trying to convert the data from the data file into the type of a column in the external table.
Action: See messages that follow for more details.
Cause: An error occurred while trying to convert the data from the data file into the type of a column in the external table.
Action: See messages that follow for more details.
Cause: This message identifies a record number in a file for a record that had an error. The message preceding this one contains information about the error and the name of the file.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: An OCI error occurred while processing the granule.
Action: Contact Oracle Support Services.
Cause: An OCI error occurred while processing the granule.
Action: Contact Oracle Support Services.
Cause: An unrecoverable error occurred during processing.
Action: See preceding error messages for more information.
Cause: The record parser was looking for the size portion of a file a record format of VARIABLE. It found EOF before finding all the bytes for the length.
Action: Correct the corruption in the file.
Cause: No location for the data source of the external table was specified when the external table was created. An empty string is not valid.
Action: Specify the name of the data source in the LOCATION clause when creating an external table.
Cause: An attempt to open the log file failed.
Action: Specify a different log file or use NO LOGFILE to disable logging.
Cause: An unexpected error occurred while initializing access to an external table.
Action: Contact Oracle Support Services.
Cause: An error occurred while attempting to retrieve information about a data source.
Action: See messages preceding this one for more information about the error.
Cause: An attempt to create an internal object failed.
Action: Contact Oracle Support Services.
Cause: An attempt to fetch information about an internal object failed.
Action: Contact Oracle Support Services.
Cause: An error occurred while atempting to fetch data from an external table.
Action: See messages preceding this one for more information about the error.
Cause: This is an informational message displayed whenever the WHEN clause has been satisfied. If a DISCARD file has been specified for the operation, then the record will be written to that file. The record number in the source data file was not known because multiple servers are loading from the file.
Cause: An error occurred while attempting to write to the named file.
Action: See messages that follow this message for more information about the error.
Cause: A record was rejected because all fields in the data file referenced by the query were NULL.
Cause: The user does not have write access to the directory object used for a log, bad, or reject file.
Cause: The user does not have read access to the directory object used for a data file.
Cause: The name of a data file, log file, bad file, or reject file contained a path specification.
Action: Use the name of a directory object to indicate where the file should be stored.
Cause: A format specifier is a percent sign followed by a character. The percent sign and character are replaced by a value depending on the character. This error occurs when the character following the percent sign is not defined to have a value.
Action: See the documentation for information on valid format specifiers. If the file to be opened needs to have a percent sign in its name, then use two percent signs. They will get replaced by a single percent sign in the resulting file name.
Cause: An attempt to parse the file name failed.
Action: Specify a valid file name.
Cause: An attempt to retrieve a list of valid directories that can be used by the user to open files failed. See messages that follow for more information.
Action: Contact Oracle Support Services. As a workaround, try specifying no log file, no discard files, and no bad files.
Cause: The directory object specified for an input file or a log, bad or discard file, does not exist in the database or the user has no privileges to access this directory.
Cause: A query of an external table requested a sample of the data returned. The access driver for the external table does not support sampling.
Action: Do not try to use sampling for this external table.
Cause: A big endian byte order mark was found at the beginning of the specified file. Either the access parameters specified that the data was in little endian order or the byte order mark for a previous file was little endian.
Action: The file needs to be loaded separately. If a byte order was specified in the access parameters, then make sure it is changed to big endian.
Cause: A little endian byte order mark was found at the beginning of the specified file. Either the access parameters specified that the data was in big endian order or the byte order mark for a previous file was big endian.
Action: The file needs to be loaded separately. If a byte order was specified in the access parameters, then make sure it is changed to little endian.
Cause: A record in the data file was not loaded into the table because of an error while finding fields in the record. See the previous error for more information. The record will be written to the BAD file, if one is being used. The record number in the source data file is not known because multiple servers are loading from the file.
Cause: A record in the data file was not loaded into the table because of an error while finding fields in the record. See the previous error for more information. The record will be written to the BAD file, if one is being used.
Cause: This is an informational message displayed whenever the WHEN clause has been satisfied. If a DISCARD file has been specified for the operation, then the record will be written to that file.
Cause: An error occurred converting a zoned decimal number to an Oracle number.
Action: Verify that the zoned decimal number is formatted correctly.
Cause: A zoned decimal number has an invalid format.
Action: Verify that the zoned decimal number is formatted correctly.
Cause: A zoned decimal number could not be converted to an Oracle number because the number is too big for an oracle number.
Action: Verify that the zoned decimal number is formatted correctly.
Cause: The precision of a zoned decimal number is larger than the precision that can be stored in an Oracle number.
Action: Verify that the zoned decimal number is formatted correctly.
Cause: The query that is executing requires that a data source for an external table be read multiple times. However, the data source is a sequential device that cannot be reread. Examples of this type of data source is a tape or pipe.
Action: There are a few ways around this problem. One is to rewrite the query so that the external table is referenced only once. Another option is to move the data source to a rereadable device such as a disk file. A third option is to load the data for the external table into a temporary table and change the query to reference the temporary table.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
