SQL*Loader-00813: error dropping internal table: string

SQL*Loader-00813: error dropping internal table: string

Cause: An error was encountered trying to drop a temporary internal table. The internal table is used only when loading multiple tables from the same data file. The internal table is loaded once and the target tables are loaded from the internal table. The internal table may have been left from a previous build.

Action: none

SQL*Loader-00812: error creating internal table: string

SQL*Loader-00812: error creating internal table: string

Cause: An error was encountered trying to create a temporary internal table. The internal table is used only when loading multiple tables from the same data file. The internal table is loaded once and the target tables are loaded from the internal table.

Action: none

SQL*Loader-00811: error dropping external table: string

SQL*Loader-00811: error dropping external table: string

Cause: An error occurred when trying to drop an external table. Note that the table may have been left from a previous load.

Action: none

SQL*Loader-00810: error creating external table: string

SQL*Loader-00810: error creating external table: string

Cause: An attempt to create the external table sued for the load failed.

Action: See messages that follow for more information about the failure.

SQL*Loader-00809: error dropping sequence: string

SQL*Loader-00809: error dropping sequence: string

Cause: A sequence needed to be dropped either because SQL Loader found a sequence with the same name it is trying to create or because SQL Loader is cleaning up from sequences it created at the beginning of the load.

Action: See messages that follow this one for information about why the attampt to drop the sequence failed.

SQL*Loader-00808: error creating sequence: string

SQL*Loader-00808: error creating sequence: string

Cause: An attempt to create a sequence needed for the load failed.

Action: See messages that follow this one for information about the failure.

SQL*Loader-00807: error loading table

SQL*Loader-00807: error loading table

Cause: An INSERT statement used to load a table from an external table or a temporary internal table failed. The statement that failed is shown immediately preceding this mesage.

Action: See subsequent messages for more information about the error.

SQL*Loader-00806: unknown record format specified for data file

SQL*Loader-00806: unknown record format specified for data file

Cause: The osd string containing file processing options in the control file specified an unknown file processing option.

Action: Verify the correct options are specified for the platform being used.

SQL*Loader-00805: %s not supported by External Table

SQL*Loader-00805: %s not supported by External Table

Cause: The specified option is not supported by External Table Load.

Action: Remove the specified option or do not use External Table Load.

SQL*Loader-00804: SEQUENCES with intervals are not supported by External Table Load.

SQL*Loader-00804: SEQUENCES with intervals are not supported by External Table Load.

Cause: A sequence with an interval is specified and is not supported by External Table Load.

Action: Remove the interval from the sequence, or the the sequence itself, or do not use External Table Load.

SQL*Loader-00803: %s field type not supported by External Table

SQL*Loader-00803: %s field type not supported by External Table

Cause: The specified field type is not supported by External Table Load.

Action: Remove the specified field type or do not use External Table Load.

SQL*Loader-00802: numeric EXTERNAL with DEFAULTIF clause not supported by External Table

SQL*Loader-00802: numeric EXTERNAL with DEFAULTIF clause not supported by External Table

Cause: A numeric EXTERNAL type was specified with a DEFAULTIF clause and that is not supported by External Table Load.

Action: Remove the clause if possible or do not use External Table Load.

SQL*Loader-00801: all INTO TABLE clauses must have the same options (string)

SQL*Loader-00801: all INTO TABLE clauses must have the same options (string)

Cause: At least two INTO TABLE clauses have different options set.

Action: Set the options to be the same or do the loads separately.

SQL*Loader-00800: %s specified and ignored

SQL*Loader-00800: %s specified and ignored

Cause: An option was specified that is not supported by External Table load.

Action: Do not specify the unsupported option or do not use External Table load.

SQL*Loader-00713: Internal error calling SLTS layer: string failed with return code (number(.

SQL*Loader-00713: Internal error calling SLTS layer: string failed with return code (number(.

Cause: A nonsuccess status was returned by a call to the SLTS layer.

Action: Contact customer support.

SQL*Loader-00712: Internal error: bad address for big endian UTF16 conversion

SQL*Loader-00712: Internal error: bad address for big endian UTF16 conversion

Cause: Address for big endian UTF16 data not in a valid buffer.

Action: Contact customer support.

SQL*Loader-00711: Internal error: bad address for little endian UTF16 conversion

SQL*Loader-00711: Internal error: bad address for little endian UTF16 conversion

Cause: Address for little endian UTF16 data not in a valid buffer.

Action: Contact customer support.

SQL*Loader-00710: Internal error: direct path stream buffer not loaded

SQL*Loader-00710: Internal error: direct path stream buffer not loaded

Cause: A direct path stream buffer was built but not loaded.

Action: Contact customer support.

SQL*Loader-00709: Internal error calling SLTS layer: string failed

SQL*Loader-00709: Internal error calling SLTS layer: string failed

Cause: A nonsuccess status was returned by a call to the SLTS layer.

Action: Contact customer support.

SQL*Loader-00708: Internal error: unknown status number returned from sllf layer

SQL*Loader-00708: Internal error: unknown status number returned from sllf layer

Cause: An unknown status was returned by a call to the sllf layer.

Action: Contact customer support.

SQL*Loader-00706: Bad argument to ulerr (number(.

SQL*Loader-00706: Bad argument to ulerr (number(.

Cause: An internal error has occurred.

Action: Contact customer support.

SQL*Loader-00705: Internal error

SQL*Loader-00705: Internal error

Cause: An internal error has occurred.

Action: Contact customer support.

SQL*Loader-00704: Internal error: string (number(

SQL*Loader-00704: Internal error: string (number(

Cause: An internal error has occurred.

Action: Make a note of the message and the number, then contact customer support.

KUP-11007: conversion error loading table string.string

KUP-11007: conversion error loading table string.string

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

Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being loaded matches the definition of the table being unloaded.

KUP-11006: file truncated error in string

KUP-11006: file truncated error in string

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

Action: Verify unload operation completed successfully.

KUP-11005: error seeking in file: string

KUP-11005: error seeking in file: string

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

Action: Review the error message. Resolve the problem and retry the the operation. Contact Oracle Support Services if the problem cannot be resolved.

KUP-11004: requested version string not supported by ORACLE_DATAPUMP

KUP-11004: requested version string not supported by ORACLE_DATAPUMP

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.

Action: Specify a supported version and rerun the operation.

KUP-11003: bad data encountered while reading from file string

KUP-11003: bad data encountered while reading from file string

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.

Action: If the row containing the bad data should not be filtered out, then modify the definition of the external table so that the datatypes of the columns match the datatypes of the fields in the data file.

KUP-11002: unable to read data chunk string

KUP-11002: unable to read data chunk string

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

Action: Verify the files used for the load operation are correct.

KUP-11001: files not from the same unload operation

KUP-11001: files not from the same unload operation

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

Action: Verify the files used are from the same unload operation.

KUP-11000: file truncated error

KUP-11000: file truncated error

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

Action: Verify unload operation completed successfully.

KUP-04108: unable to reread file string

KUP-04108: unable to reread file string

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.

KUP-04106: precision for zoned decimal number is too large for string

KUP-04106: precision for zoned decimal number is too large for string

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.

KUP-04105: zoned decimal to number conversion caused overflow for string

KUP-04105: zoned decimal to number conversion caused overflow for string

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.

KUP-04104: zoned decimal field has bad values for string

KUP-04104: zoned decimal field has bad values for string

Cause: A zoned decimal number has an invalid format.

Action: Verify that the zoned decimal number is formatted correctly.

KUP-04103: error converting zoned decimal field to number for string

KUP-04103: error converting zoned decimal field to number for string

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

Action: Verify that the zoned decimal number is formatted correctly.

KUP-04102: record number discarded from file string

KUP-04102: record number discarded from file string

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.

Action: none

KUP-04101: record number rejected in file string

KUP-04101: record number rejected in file string

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.

Action: none

KUP-04100: record rejected in file string

KUP-04100: record rejected in file string

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.

Action: none

KUP-04091: little endian byte order mark found when big endian expected in string

KUP-04091: little endian byte order mark found when big endian expected in string

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.

Action: The file needs to be loaded separately. If a byte order was specified in the access parameters, make sure it is changed to be little endian.

KUP-04090: big endian byte order mark found when little endian expected in string

KUP-04090: big endian byte order mark found when little endian expected in string

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.

Action: The file needs to be loaded separately. If a byte order was specified in the access parameters, make sure it is changed to be big endian.

KUP-04089: column transform string is not the name of a table column

KUP-04089: column transform string is not the name of a table column

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

Action: Verify that the correct name was specified in the column transform.

KUP-04088: data sampling is not supported by this access driver

KUP-04088: data sampling is not supported by this access driver

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.

KUP-04085: duplicate directory object string and file string specified for unload

KUP-04085: duplicate directory object string and file string specified for unload

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.

Action: Issue the CREATE TABLE AS SELECT command again but make sure the combination of directory objects and filenames is unique.

KUP-04084: The ORACLE_DATAPUMP access driver does not support the ROWID column.

KUP-04084: The ORACLE_DATAPUMP access driver does not support the ROWID column.

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.

Action: Remove the ROWID from the query. If that is not possible, create a table in the database with the same columns as the external table, copy the data from the external table into the newly created table, and use that new table for the query.

KUP-04083: no directory object specified in LOBFILE clause for column string

KUP-04083: no directory object specified in LOBFILE clause for column string

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.

Action: Either specify a directory name, or the name of a data field containing the name of the directory object that contains the files.

KUP-04082: error converting field string for LOBFILE column string

KUP-04082: error converting field string for LOBFILE column string

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.

Action: Verify that the data file has the correct value for the fields. Also verify that the correct character set was specified for the data file.

KUP-04081: field string used in concatenation for column string is not a character type

KUP-04081: field string used in concatenation for column string is not a character type

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.

Action: Verify the correct field was used in the CONCAT clause. Also verify that the correct datatype is specified for the field in the field list.

KUP-04080: directory object string not found

KUP-04080: directory object string not found

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.

Action: none

KUP-04079: error fetching list of valid directories

KUP-04079: error fetching list of valid directories

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. As a workaround try specifing no log file, no discard files and no bad files.

KUP-04078: invalid file name specified: string

KUP-04078: invalid file name specified: string

Cause: Attempt to parse the file name failed.

Action: Specify a valid file name.

KUP-04077: unknown format specifier in file name string

KUP-04077: unknown format specifier in file name string

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 pecent signs. They will get replaces by a single percent sign in the resulting file name.

KUP-04076: file name cannot contain a path specification: string

KUP-04076: file name cannot contain a path specification: string

Cause: The name of a data file, log file, bad file or reject file contains a path specification.

Action: Use the name of a directory object to indicate where the file should be stored.

KUP-04075: no read access to directory object string

KUP-04075: no read access to directory object string

Cause: The user does not have read access to the directory object used for a data file.

Action: none

KUP-04074: no write access to directory object string

KUP-04074: no write access to directory object string

Cause: The user does not have write access to the directory object used for a log, bad or reject file.

Action: none

KUP-04073: record ignored because all referenced fields are null for a record

KUP-04073: record ignored because all referenced fields are null for a record

Cause: A record was rejected because all fields in the data file referenced by the query were NULL.

Action: none

KUP-04072: error writing to file string

KUP-04072: error writing to file string

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.

KUP-04071: record discarded from file string

KUP-04071: record discarded from file string

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.

Action: none

KUP-04070: field string referenced by column transform string not found

KUP-04070: field string referenced by column transform string not found

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

Action: Verify that the column transform clause is specified correctly. Also verify that the field definitions for the data file are correct.

KUP-04069: error fetching data for external table

KUP-04069: error fetching data for external table

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

Action: See messages the precede this one for more information.