KUP-04068: internal error fetching attribute string

KUP-04068: internal error fetching attribute string

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

Action: Contact Oracle support.

KUP-04067: internal error allocating handle type string

KUP-04067: internal error allocating handle type string

Cause: An attempt to create an internal object failed.

Action: Contact Oracle support.

KUP-04066: error initializing access to external table source

KUP-04066: error initializing access to external table source

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.

KUP-04065: error processing LOBFILE for field string

KUP-04065: error processing LOBFILE for field string

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

Action: See message in log file for more information about the error.

KUP-04064: fatal error during initialization

KUP-04064: fatal error during initialization

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

Action: Contact Oracle support.

KUP-04063: unable to open log file string OS error string

KUP-04063: unable to open log file string OS error string

Cause: An attempt to open the log file failed.

Action: Specify a different log file or use NO LOGFILE to disable logging.

KUP-04062: no data source specified

KUP-04062: no data source specified

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.

KUP-04061: directory object string specified for LOBFILE column string is not valid

KUP-04061: directory object string specified for LOBFILE column string is not valid

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.

Action: Verify that the data file contains the correct directory object and verify that the list of valid directory objects in the LOBFILE clause for this column is complete.

KUP-04060: field string referenced by lobfile column string not found

KUP-04060: field string referenced by lobfile column string not found

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.

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

KUP-04059: found EOF in length portion of VARIABLE record in file string

KUP-04059: found EOF in length portion of VARIABLE record in file string

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.

KUP-04058: unrecoverable error occurred, operation aborted.

KUP-04058: unrecoverable error occurred, operation aborted.

Cause: An unrecoverable error occurred during processing.

Action: See preceding error messages for more information.

KUP-04057: internal error: OCI error while fetching record.

KUP-04057: internal error: OCI error while fetching record.

Cause: An OCI error occurred while processing the granule.

Action: Contact Oracle support.

KUP-04056: internal error: OCI error while fetching record: number

KUP-04056: internal error: OCI error while fetching record: number

Cause: An OCI error occurred while processing the granule.

Action: Contact Oracle support.

KUP-04055: column string is both a field in the data file and a column transform

KUP-04055: column string is both a field in the data file and a column transform

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.

Action: Determine whether the value for the field in the data file or the value for the field in the column transform should be loaded in to the table. If the value for the data file is to be loaded, then remove the column transform. If the value for the column transform is to be loaded, then rename the field in the data file so that it does not match the name of a field in the table.

KUP-04054: internal error: invalid bad row number identified for bad column number

KUP-04054: internal error: invalid bad row number identified for bad column number

Cause: This is an internal error.

Action: Contact Oracle support.

KUP-04053: record number number

KUP-04053: record number number

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.

Action: none

KUP-04052: error processing column string in a row for datafile string

KUP-04052: error processing column string in a row for datafile string

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.

KUP-04051: error processing column string in row number for datafile string

KUP-04051: error processing column string in row number for datafile string

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.

KUP-04050: error while attempting to allocate number bytes of memory

KUP-04050: error while attempting to allocate number bytes of memory

Cause: d by insufficient memory.

Action: Reconnect to the instance and retry the operation.

KUP-04049: record number discarded from file string

KUP-04049: 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-04048: internal error parsing record from external data source

KUP-04048: internal error parsing record from external data source

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

Action: Contact Oracle support.

KUP-04047: error parsing record from external data source

KUP-04047: error parsing record from external data source

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

Action: Look in the log file for more messages about the error.

KUP-04045: unexpected OCI status string

KUP-04045: unexpected OCI status string

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

Action: Contact Oracle support.

KUP-04044: error positioning file string

KUP-04044: error positioning file string

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

Action: See messages that follow for more information.

KUP-04043: table column not found in external source: string

KUP-04043: table column not found in external source: string

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.

KUP-04041: error generating full file name for string in string

KUP-04041: error generating full file name for string in string

Cause: Unexpected error occurred while trying to form a file name.

Action: none

KUP-04040: file string in string not found

KUP-04040: file string in string not found

Cause: The file was not found in the directory specified

Action: Verify the correct file and directory names were specified.

KUP-04039: unexpected error while trying to find file string in string

KUP-04039: unexpected error while trying to find file string in string

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.

KUP-04038: internal error: string

KUP-04038: internal error: string

Cause: an unexpected error condition was detected.

Action: contact Oracle customer support

KUP-04037: terminator not found

KUP-04037: terminator not found

Cause: The terminator for the field is missing.

Action: Verify that the records are formatted correctly.

KUP-04035: beginning enclosing delimiter not found

KUP-04035: beginning enclosing delimiter not found

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.

KUP-04032: internal error string while parsing field string:

KUP-04032: internal error string while parsing field string:

Cause: An internal error occurred while parsing a field.

Action: Contact Oracle support.

KUP-04031: empty filename specified for LOB file in column string

KUP-04031: empty filename specified for LOB file in column string

Cause: The field in the data file that was supposed to contain the name of a LOB file was empty.

Action: Correct the data so that it contains a valid file name.

KUP-04029: numeric field overflowed

KUP-04029: numeric field overflowed

Cause: An attempt to convert a character string to number failed because the value of the number in the string was too large.

Action: none

KUP-04028: conversion of character length to a number failed

KUP-04028: conversion of character length to a number failed

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 datatypes specified for the fields are correct.

KUP-04026: field too long for datatype

KUP-04026: field too long for datatype

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.

KUP-04025: field extends beyond end of record

KUP-04025: field extends beyond end of record

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.

SQL*Loader-00435: invalid constant value string for nested table column string

SQL*Loader-00435: invalid constant value string for nested table column string

Cause: A constant value was specified for the SETID of a nested table column. An error occured while translating the character constant into a SETID.

Action: Make sure the constant string contains valid hexadecimal characters and that there are 32 hexadecimal characters.

SQL*Loader-00434: Can not load LOB or XML in a nested table along with the parent table.

SQL*Loader-00434: Can not load LOB or XML in a nested table along with the parent table.

Cause: Loading LOBs and XML data within a nested table at the same time as the parent table is not supported.

Action: Load the nested table with the LOB or XML column separately from the parent table.

SQL*Loader-00433: no attributes found for column object string in table string

SQL*Loader-00433: no attributes found for column object string in table string

Cause: No attributes are to be loaded for a column object named in the control file. This can happen if all fields in the definition for the column object in the control are designated as FILLER fields.

Action: Either specify attributes to load for the column object or remove the column object from the control file.

SQL*Loader-00432: converted data too large

SQL*Loader-00432: converted data too large

Cause: This message is preceded by a message identifying a row and column. It is displayed when there is insufficient room to convert the data from the datatype in the input file to the datatype for the column in the database.

Action: Modify the data so that it fits in the database field.

SQL*Loader-00431: illegal NULLIF or DEFAULTIF clause specified for nested table column string

SQL*Loader-00431: illegal NULLIF or DEFAULTIF clause specified for nested table column string

Cause: Rows in a nested table cannot be set to NULL. SQLLDR displays this error when a NULLIF clause was specified for the element that defines the row that make up a nested table. SQLLDR also displays this error if a DEFAULTIF clause is specified for an element that is a named type, since SQLLDR will set a named type to NULL if the DEFAULTIF evaluates to TRUE.

Action: none

SQL*Loader-00430: NULL nested table element is not allowed

SQL*Loader-00430: NULL nested table element is not allowed

Cause: A row in a nested table was set to NULL. Nested tables cannot contain NULL fields.

Action: Correct the data so that there are no NULL rows in the nested table.

SQL*Loader-00429: insufficient number of elements found for varray

SQL*Loader-00429: insufficient number of elements found for varray

Cause: The COUNT directive was specified for a varray, but the number of elements found is less than the number specified by the COUNT directive.

Action: Correct the data so that the count and the number of elements agree.

non-LOB scalar data fields. SQL*Loader-00428: count for field string not stored in character or integer field

non-LOB scalar data fields. SQL*Loader-00428: count for field string not stored in character or integer field

Cause: The count clause for a field references another field, but the referenced field is not a character or integer datatype.

Action: Modify the count field so that it reference a a data field that has the count in an integere or character format.

SQL*Loader-00427: a field condition references a non-scalar field or a LOB field string

SQL*Loader-00427: a field condition references a non-scalar field or a LOB field string

Cause: The field condition is referencing a field which is either a nested table, varray, column object, LOB or BILE field. These fields with these typescannot be references by other field.

Action: Correct the NULLIF, DEFAULTIF, or WHEN clauses to reference only

SQL*Loader-00425: column string makes illegal reference to collection field string

SQL*Loader-00425: column string makes illegal reference to collection field string

Cause: A clause, such as NULLIF or BFILE clause, for the column refers to a field declared inside of a collection.

Action: Move the data containing the value for a SID or OID clause outside of the collection definition.

SQL*Loader-00424: table string makes illegal reference to collection field string

SQL*Loader-00424: table string makes illegal reference to collection field string

Cause: A WHEN, OID or SID clause for the table refers to a field declared inside of a collection.

Action: Move the data containing the value for a SID or OID clause outside of the collection definition.

SQL*Loader-00423: element count is greater than maximum allowed for the column

SQL*Loader-00423: element count is greater than maximum allowed for the column

Cause: When building a varray from the data file, SQL*Loader encountered more varray elements than are allowed for the column.

Action: The previous error messages contain the name of the column and the row number containing the bad data.

SQL*Loader-00422: constant element count of number for column string is greater than maximum, number

SQL*Loader-00422: constant element count of number for column string is greater than maximum, number

Cause: The number of elements specified for a varray column in a table is greater than the maximum number of elements allowed for the type of the varray column.

Action: Increase the number of elements allowed for the type or remove unwanted elements from the data file.

SQL*Loader-00421: error converting data

SQL*Loader-00421: error converting data

Cause: This message can be displayed as one of the reasons for rejecting a row. The sqlldr utility was attempting to convert data for the column from its datatype in the data file to the datatype for the column in the database. This message should be followed with another message describing the conversion error.

Action: Correct the data in the data file so that it can be converted.

SQL*Loader-00420: unsupported datatype conversion requested for column string in table string

SQL*Loader-00420: unsupported datatype conversion requested for column string in table string

Cause: The colummn needs to have it s data converted to another datatype before loading the data. The required conversion cannot be done by sqlldr.

Action: Verify that the correct datatype was specified for the column.

SQL*Loader-00419: input datatype for column string is not supported when loading varrays

SQL*Loader-00419: input datatype for column string is not supported when loading varrays

Cause: The datatype in the SQL*Loader control file for the column is cannot be used to load data in a varray.

Action: Use a different datatype.

SQL*Loader-00418: Bad datafile datatype for column string

SQL*Loader-00418: Bad datafile datatype for column string

Cause: The datatype in the data file specified for the column cannot be used to load the column. This message is often displayed for columns that need to be loaded with special features. For example, BFILE columns can only be loaded via the BFILE directive in the control file; same goes for REF fields. in the SQL*Loader control file. Similarly, REF columns can only be loaded with theREF datatype in the SQL*Loader control file.

Action: Determine the datatype of the column in the database check the documentation for the correct mechanisms to use to load columns of that type.

SQL*Loader-00703: Internal error: argument number

SQL*Loader-00703: Internal error: argument number

Cause: An internal error has occurred.

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

SQL*Loader-00702: Internal error - string

SQL*Loader-00702: Internal error - string

Cause: An internal error has occurred.

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

SQL*Loader-00700: Out of memory while performing essential allocations (number(

SQL*Loader-00700: Out of memory while performing essential allocations (number(

Cause: SQL*Loader could not allocate the memory it needs.

Action: Check the operating system and process memory. Increase memory available to SQL*Loader, if possible. If using direct path, try lowering the columnarrayrows option (see log file for current default value).

SQL*Loader-00655: cannot load object-relational XML attribute using direct path

SQL*Loader-00655: cannot load object-relational XML attribute using direct path

Cause: The table being loaded contains a column object which contains an XML attribute with a storage type of object-relational. This type of attribute cannot be loaded with direct path.

Action: Perform the load with conventional path mode.

SQL*Loader-00654: Variable length field exceeds maximum length.

SQL*Loader-00654: Variable length field exceeds maximum length.

Cause: A variable length field (with a leading length subfield) exceeded its maximum allowable length. The maximum length is either the length specified in the SQL*Loader control file, or, the default if not specified (4kb).

Action: Shorten the field and its length.

SQL*Loader-00653: XML data set to NULL in column string, row number, table string

SQL*Loader-00653: XML data set to NULL in column string, row number, table string

Cause: Encountered errors (e.g. parsing errors in LOBFILE) while loading LOBs into an XML column. The row will remain in the table and its XML column will be initialized to null. Loading of other records will continue.

Action: Correct the data file (see accompanying messages) and reload.