Cause: An error was encountered while attempting to initialize the XAD package.

Cause: The parser detected a syntax 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.

Cause: An internal XAD error occurred.

Cause: A fatal error has occurred.

Cause: An error was signalled during parsing of the access parameters.

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.

Cause: An illegal punctuation character was encountered.

Cause: This is probably caused by failure to supply the closing quote for a quoted string.

Cause: An input character that is neither an alpha, digit, or punctuation was encountered.

Cause: A quoted string longer than 2000 bytes was encountered.

Cause: A token longer than 1000 bytes was encountered

Cause: a line longer than 500 bytes was encountered

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

Cause: Error in specifying position for the specified field in the access parameters."

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.

Cause: The position of field was specified with a relative start and an absolute end.

Cause: The number of bytes specified by the relative end position for the field does not match the number of bytes in the datatype.

Cause: Error attempting to retrieve information for the character set.

Cause: A byte range specified a start position that comes after the end position.

Cause: An error occurred while trying to obtain column parameters.

Cause: An error occurred while trying to obtain column name.

Cause: An error occurred while trying to obtain database column type.

Cause: An error occurred while trying to obtain database column size.

Cause: An error occurred while trying to obtain database column precision.

Cause: An error occurred while trying to obtain database column scale.

Cause: An error occurred while trying to obtain a datetime column precision value."

Cause: An error occurred while trying to obtain database column precision.

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: The date mask for the specified column is invalid.

Cause: A LOBFILE clause was specified for the field, but no directory object was specified. When no directory object is specified, then the default directory specified for the external table is used, but no default directory was specified.

Cause: An empty delimiter string was specified for a record delimiter.

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: The string value for a TERMINATED BY or ENCLOSED BY clause is longer than the maximum number of bytes allowed. If the character set of the data file is different than the character set of the database, the string will be converted to the character set of the data file. If the length of the converted string is too large, then this error will also be returned.

Cause: The string value for a TERMINATED BY or ENCLOSED BY clause for the columns is longer than the maximum number of bytes allowed. If the character set of the data file is different than the character set of the database, the string will be converted to the character set of the data file. If the length of the converted string is too large, then this error will also be returned.

Cause: The comma-delimited value (CSV) format files did not have all delimited fields. CSV format files must have all delimited fields so that the access driver can process the fields.

Cause: The data files with a FIELD NAMES record did not have all delimited fields. Data files with a FIELD NAMES record must have all delimited fields so that the access driver can process the field names.

Cause: The field had both NULLIF and NO NULLIF specified. You must specify one or the other.

Cause: The ALL FIELDS OVERRIDE THESE clause was specified and there was a field name in the field list in the access parameters that did not match the name of a column in the table definition. Only names that match the name of columns in the table may be specified in the field list.

Cause: The access parameter contained an invalid value for the parameter specified in the error message.

Cause: LOCAL can only be specified with TIMESTAMP, not with TIME.

Cause: Multiple date format masks were specified for the listed datetime or interval data type at the table level for the listed table.

Cause: The date format mask for listed datetime type for the specified table was invalid.

Cause: error occured while attempting to format a KUP message.

Cause: Error converting a date format string into an internal representation.

Cause: An unexpected error occurred while preparing the file.

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.

Cause: An error occurred while retrieving the number of bytes in the specified file.

Cause: An error occurred while closing the specified file.

Cause: An error occurred while reading the specified file.

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.

Cause: A record in a VAR file has an length field with either no numeric characters in it or with non numeric characters in it.

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.

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.

Cause: This can happen when specifying either absolute or relative positioning for a field.

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.

Cause: This can happen when specifying either absolute or relative positioning for a field.

Cause: The character field in the record is larger than the maximum length specified.

Cause: The check of the filename failed. These checks are platform specific, but they can include verifying that there are no hard links in the file path, the file is not a soft link, the file specification includes a parent reference ("../" on Unix), or the file was modified between the time the check was made and the file was opened.

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.

Cause: An attempt to convert a character string to 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: The field in the data file that was supposed to contain the name of a LOB file was empty.

Cause: An internal error occurred while parsing a field.

Cause: The beginning enclosure was not found for a field that is enclosed by delimiters.

Cause: The terminator for the field is missing.

Cause: an unexpected error condition was detected.

Cause: An error occurred while trying to find path containing the file.

Cause: The file was not found in the directory specified

Cause: 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.

Cause: An attempt to position a file to an absolute file offset failed.

Cause: An OCI call returned a status that cannot be handled.

Cause: An error occurred while trying to extract a record from the data source.

Cause: An unexpected or unhandled error occurred while getting a record from the data source

Cause: Informational message displayed whenever the WHEN clause has been satisfied. If a DISCARD file has been specified for the operation, the record will be written to that file.

Cause: An error occurred while trying to allocate memory. This is likely caused by insufficient memory.

Cause: an error occurred while trying to convert the data from the data file into the type of a column in the external table.

Cause: an error occurred while trying to convert the data from the data file into the type of a column in the external table.

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.

Cause: The specified column was in the list of fields in the data file and in the list of column transforms. The column should be in one list or the other, but not both.

Cause: An OCI error occurred while processing the granule.

Cause: An OCI error occurred while processing the granule.

Cause: An unrecoverable error occurred during processing.

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.

Cause: The LOBFILE transform for the named column referenced a field for either the directory object portion or the name portion of the LOBFILE. However, that field did not exist anywhere in the definition of the data file.

Cause: The column being loaded from a LOBFILE specified the directory object containing the LOBFILE through another field in the data file. In this case, the LOBFILE clause in the access parameters must specify a list of all directory objects that will be used for this field. This error occurs because a field contains the name of a directory object that is not in this list.

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.

Cause: An attempt to open the log file failed.

Cause: An unexpected error occurred while initializing access to an external table.

Cause: An error occured while opening or reading a LOBFILE for a column in a row.

Cause: An error occurred while attempting to retrieve information about a data source.

Cause: An attempt to create an internal object failed.

Cause: An attempt to fetch information about an internal object failed.

Cause: An error occurred while atempting to fetch data from an external table.

Cause: The column transform for the named column references a field that did not exist anywhere in the definition of the data file.

Cause: Informational message displayed whenever the WHEN clause has been satisfied. If a DISCARD file has been specified for the operation, the record will be written to that file. The record number in the source data file is not known because multiple servers are loading from the file.

Cause: An error occurred while attempting to write to the named file.

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 contains a path specification.

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.

Cause: Attempt to parse the file name failed.

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.

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: The specified field was part of a concatenation of strings used to create the value for the names column. However, the field was not of a character datatype. Only character fields may be used as part of concatenating fields.

Cause: The LOBFILE column had either its directory object name or filename specified by a field in the data file and that field needed to be converted to the server's character set before it could be used. This message indicates that an attempt to convert the field failed.

Cause: There was no directory object specified for the LOB files used to populate the named column and no default directory was specified for the external table.

Cause: A query of an external table of type ORACLE_DATAPUMP tried to reference the ROWID column. The ORACLE_DATAPUMP access driver does not support ROWIDs.

Cause: A CREATE TABLE AS SELECT statement was executed for an external table of type ORACLE_DATAPUMP and the same directory object and filename combination was specified multiple times.

Cause: The length of a filename is longer than the maximum length supported by Oracle on the server platform.

Cause: Execute access to the directory object used for a preprocessor file was not granted.

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.

Cause: The specified column was in the list of column transforms but a column by that name does not exist in the table

Cause: A big endian byte order mark was found at the beginning of the specified file and either the access parameters specified the data was in little endian order or the byte order mark for a previous file was little endian.

Cause: A little endian byte order mark was found at the beginning of the specified file and either the access parameters specified the data was in big endian order or the byte order mark for a previous file was big endian.

Cause: An error occurred while attempting to enable auditing for the specified directory object.

Cause: An error occurred while processing the FIELD NAMES record for the data file.

Cause: The Database Vault option did not permit the execution a program from an Oracle directory object.

Cause: The specified preprocessor command encountered an error during execution.

Cause: The specified column was in the list of lobfile column transforms but the PREPROCESSOR option was also specfied. The PREPROCESSOR option does not work in conjuction with lobfile column transforms.

Cause: The RECORDS clause was part of the external table access parameters but no record format type was provided.

Cause: The field name for the listed field number in the FIELD NAMES record was empty.

Cause: One or more field names was not listed in the FIELD NAMES record. However, it was listed in the access parameter list for the external table.

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: Informational message displayed whenever the WHEN clause has been satisfied. If a DISCARD file has been specified for the operation, the record will be written to that file.

Cause: An error occurred converting a zoned decimal number to an Oracle number.

Cause: A zoned decimal number has an invalid format.

Cause: A zoned decimal number could not be converted to an Oracle number because the number is too big for an oracle number.

Cause: The precision of a zoned decimal number is larger than the precision that can be stored in an Oracle number.

Cause: A substring was specified for a field that which is not a character datatype. Only character fields may be used when specifying the substring transform.

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.

Cause: The default directory or a directory object specified for an input data file or an output dump, log, bad or discard file contains an invalid path name.

Cause: The field name exceeded the maximum of 30 characters.

Cause: The listed field name in the FIELD NAMES record of the data file was not found in the access parameter field list or in the table columns. The next error message, if any, lists the name of the data file where the error was found.

Cause: This message provides information about the previous messages.

Cause: An error occured while trying to open a directory to look for files that match a wild card specification.

Cause: An error occured while trying to retrieve the count of files matching a wild card specification in the directory

Cause: An error occured while trying to retrieve the names of files matching a wild card specification in the directory

Cause: An error occured while trying to finish a search for files that match a wild card specification the directory. matching a wild card specification in the directory

Cause: CSV is being used with a shift based chararcter set.

Cause: One or more file specifications including wild cards were specified in the LOCATION clause, but none of the files matched any of the specifications.

Cause: No matching files were found for the LOCATION clause specification listed in the previous error message.

Cause: Intra source concurrency can only be used when parallel select has been requested.

Cause: Intra source concurrency cannot be used with RECNUM fields.

Cause: Intra source concurrency cannot be used with terminators where replicated substrings in the terminator could cause ambiguity during record parsing.\n\n"

Cause: Intra source concurrency cannot be used with the PREPROCESSOR option.

Cause: Intra source concurrency cannot be used with the DELIMITED record format if the characterset is neither fixed width or UTF8.

Cause: Intra source concurrency cannot be used with the VARIABLE record format.

Cause: Intra source concurrency cannot be used with the CSV record format that has embedded record delimiters/terminators.

Cause: A truncated file was used for the load operation.

Cause: Files used for the load operation were not from the same unload operation.

Cause: A read or seek to this data chunk was not possible. This chunk may not have existed.

Cause: There was a datatype conversion error while attempting to convert the data in the data file to match the datatype of a column in the external table. The message that follows this one displays the name of the column and the start of the data for the column that could not be converted. The row containing the bad data is rejected and not included as a row in the external table.

Cause: This database version (defaulted to COMPATIBLE if not user-specified) was not supported by ORACLE_DATAPUMP external table access driver. Note: Database versions before 9.2 were not supported.

Cause: An attempt to seek to the specified position in file failed.

Cause: A truncated or incomplete file was used for the load operation.

Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.

Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.

Cause: A conversion error occurred while loading data into a table. The message shows values for the field in the row that had the conversion error.

Cause: None of the files in the LOCATION clause can be opened for a fetch on an external table.

Cause: This file could not be used for this load operation. See the following message for more information.

Cause: The specified file could not be used for this unload because that would mean overwriting an existing file.

Cause: The specified file could not be used for this operation because the internal number in the header was not valid.

Cause: The specified file could not be used for this operation because the internal metadata stored in this file does not match the metadata stored in the first file piece set.

Cause: An error has occurred in a stream unload or load operation.

Cause: The specified file could not be used for this fetch because its database version was not compatible with the database version in the other files in the LOCATION clause.

Cause: The file was not found.

Cause: This file did not have the correct file format. It could not be used for an external table fetch operation.

Cause: A file could not be used for this fetch. See the following message for more information.

Cause: The header may be corrupted.

Cause: A dump file was specified for a load operation whose version number is incompatible with the dump file version currently produced by the Oracle server on the system. Usually this message indicates that the dump file was produced by a newer version of the Oracle server.

Cause: The file name specified for a dump or log file was invalid or null.

Cause: The default directory or a directory object specified for a dump or log file contained an invalid path name or was null.

Cause: An attempt was made to access a temporary external table that was created by Data Pump to be used internally during the execution of an export or import job.