SQL*Loader-00652: Invalid zoned decimal byte.

SQL*Loader-00652: Invalid zoned decimal byte.

Cause: Each byte of a zoned decimal field must have a valid value based on the character set encoding used. ASCII-based zoned decimals must follow the formats specified in the VAX Architecture Reference Manual. EBCDIC-based zoned decimals must follow the formats specified in the ESA or 390 Principles of Operations, version 8.1.

Action: Check the SQL*Loader control file s specifications against the log file to ensure that the field location was specified correctly. Check the contents of the field.

SQL*Loader-00651: error skipping lob for column string, row number, table string

SQL*Loader-00651: error skipping lob for column string, row number, table string

Cause: Encountered errors (e.g. parsing errors in LOBFILE) while skipping LOBs.

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

SQL*Loader-00650: incomplete lob data written for column string, row number, table string

SQL*Loader-00650: incomplete lob data written for column string, row number, table string

Cause: Encountered errors (e.g. parsing errors in LOBFILE) while loading LOBs using direct path. The row will remain in the table and its LOB column may not be complete. Loading of other records will continue.

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

SQL*Loader-00649: Quoted string missing closing quote

SQL*Loader-00649: Quoted string missing closing quote

Cause: A quoted string in the control file is missing a closing quote.

Action: Insert the closing quote as appropriate.

SQL*Loader-00647: Integer to number conversion error

SQL*Loader-00647: Integer to number conversion error

Cause: An error occurred while attempting to convert an integer to an Oracle number format.

Action: Verify that the integer field in the data file is a valid integer. If the INTEGER(N) syntax was used, then verify that the length specified is valid.

SQL*Loader-00646: lob set to EMPTY in column string, row number, table string

SQL*Loader-00646: lob set to EMPTY in column string, row number, table string

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

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

SQL*Loader-00645: error converting character length field to a number

SQL*Loader-00645: error converting character length field to a number

Cause: An error occurred while attempting to convert the characters containing the count portion of a VARCHARC or VARRAWC field.

Action: Verify that the count portion for the column has the correct value.

SQL*Loader-00644: end of logical record found when reading length of varying length field

SQL*Loader-00644: end of logical record found when reading length of varying length field

Cause: While attempting to read the length portion of a varying length field, then end of the logical record was reached.

Action: Verify that the SQL*Loader control file describes the data correctly and that the data in the data file matches the description in the SQL*Loader control file

SQL*Loader-00643: error executing INSERT statement for table string

SQL*Loader-00643: error executing INSERT statement for table string

Cause: A fatal error occured while attempting to insert data into the table.

Action: Refer to the messages that follow for more information. If you specified SQL stings for any of your columns, verify that strings are correct. Specifcally, check for balanced parenthesis and correct use of quotation marks. Another format error

SQL*Loader-00642: Relative start position lamp;gt; absolute field end position.

SQL*Loader-00642: Relative start position lamp;gt; absolute field end position.

Cause: A field specified as POSITION(*+n:y) had its relative start occur after the absolute position y.

Action: Check that a delimiter is not missing and that the values of n and y are correct.

SQL*Loader-00641: Invalid packed decimal nibble.

SQL*Loader-00641: Invalid packed decimal nibble.

Cause: Each byte in a packed decimal field contains two 4-bit nibbles. Each nibble must have a valid value.

Action: Check the SQL*Loader control file s specifications against the log file to ensure that the field location was specified correctly. Check the contents of the field.

SQL*Loader-00628: Character set conversion error.

SQL*Loader-00628: Character set conversion error.

Cause: A character set conversion error occurred.

Action: Contact Oracle support. Check NLSRTL installation. Provide a reproduceable test case.

SQL*Loader-00627: Character set conversion graph not available.

SQL*Loader-00627: Character set conversion graph not available.

Cause: A conversion from the datafile character set to the client character failed due to the conversion graph not being available.

Action: Contact Oracle support. Check NLSRTL installation.

SQL*Loader-00626: Character set conversion buffer overflow.

SQL*Loader-00626: Character set conversion buffer overflow.

Cause: A conversion from the datafile character set to the client character set required more space than that allocated for the conversion buffer. The size of the conversion buffer is limited by the maximum size of a varchar2 column.

Action: The input record is rejected. The data will not fit into the column.

SQL*Loader-00625: Multibyte character error in control file.

SQL*Loader-00625: Multibyte character error in control file.

Cause: Incomplete multi-byte character strings were found in the SQL*Loader control file.

Action: Edit the SQL*Loader control file to check that all multi-byte character data is valid.

SQL*Loader-00624: no terminator found after TERMINATED and ENCLOSED field

SQL*Loader-00624: no terminator found after TERMINATED and ENCLOSED field

Cause: No termination delimiter was found after the enclosed field ended.

Action: Supply the missing termination delimiter.

SQL*Loader-00623: second enclosure string not present

SQL*Loader-00623: second enclosure string not present

Cause: The logical end of record or the end of a LOBFILE was reached before a second enclosure delimiter was found.

Action: Correct the data file to include the missing delimiter.

SQL*Loader-00622: Column not found before end of logical record (use TRAILING NULLCOLS)

SQL*Loader-00622: Column not found before end of logical record (use TRAILING NULLCOLS)

Cause: The logical record ended before all specified fields were found.

Action: If the missing fields should be loaded as null, use the TRAILING NULLCOLS clause. Otherwise, correct the data.

SQL*Loader-00621: Field in data file exceeds maximum length

SQL*Loader-00621: Field in data file exceeds maximum length

Cause: A field exceeded its maximum allowable length. The maximum length is either the length specified in the SQL*Loader control file, or, for delimitable fields without a length specified, the default maximum length (255 bytes).

Action: Check for missing delimiters and or or shorten the field.

SQL*Loader-00620: Initial enclosure character not found

SQL*Loader-00620: Initial enclosure character not found

Cause: A mandatory initial enclosure delimiter was not present. Either it is missing on the current field or the previous field is missing an identical closing delimiter.

Action: Supply the missing delimiters.

SQL*Loader-00609: value used for ROWS parameter changed from number to number

SQL*Loader-00609: value used for ROWS parameter changed from number to number

Cause: SQL Loader adjusted the value it was using for the ROWS parameter to the new value reported. This is an informational message and not an error. SQL Loader will adjust the value of the ROWS parameter if the amount of memory specified by BINDSIZE is not large enough to hold data for the number of rows specified. SQL Loader will also change the value of the ROWS parameter for conventional path loads if the value is larger than 65534. Conventional path load can load at most 65534 rows at a time.

Action: If the limit of 65534 rows for conventional path load is not being reached, then try increasing the value of BINDSIZE.

SQL*Loader-00608: subpartition not empty for INSERT option; table string, subpartition string

SQL*Loader-00608: subpartition not empty for INSERT option; table string, subpartition string

Cause: An attempt was made to use the INSERT option on a non-empty subpartition.

Action: Empty the subpartition, or use the REPLACE or TRUNCATE option.

SQL*Loader-00607: partition not empty for INSERT option; table string, partition string

SQL*Loader-00607: partition not empty for INSERT option; table string, partition string

Cause: An attempt was made to use the INSERT option on a non-empty partition.

Action: Empty the partition, or use the REPLACE or TRUNCATE option.

SQL*Loader-00606: Object string in INTO TABLE clause is not a local table

SQL*Loader-00606: Object string in INTO TABLE clause is not a local table

Cause: The synonym specified in the INTO TABLE clause in the SQL*Loader control file specifies a remote object via a database link. Only a synonym for an existing local table can be specified in the INTO TABLE clause.

Action: Ensure that a local table name or a synonym for a local table is fully specified in the INTO TABLE clause. The table must already exist.

SQL*Loader-00604: Error occurred on an attempt to commit

SQL*Loader-00604: Error occurred on an attempt to commit

Cause: An error occurred while trying to commit changes to the database.

Action: Look at the message listed below this one in the log file for more information.

SQL*Loader-00603: Maximum length number of column string is too big for bind array

SQL*Loader-00603: Maximum length number of column string is too big for bind array

Cause: The named column cannot be put in a contiguous piece of memory on the system.

Action: Specify a shorter data column.

SQL*Loader-00602: Maximum converted length number of column string is too big for bind array

SQL*Loader-00602: Maximum converted length number of column string is too big for bind array

Cause: The named column cannot undergo the specified character set conversion and still be placed in a contiguous piece of memory on the system.

Action: Specify a shorter data column or eliminate the conversion.

SQL*Loader-00601: For INSERT option, table must be empty. Error on table string

SQL*Loader-00601: For INSERT option, table must be empty. Error on table string

Cause: A non-empty table is being loaded with the INSERT option.

Action: Use the REPLACE keyword to empty the old table and store the new data in its place. Use the APPEND keyword to leave the table s contents intact and add the new data to it.

SQL*Loader-00600: Bind size of number bytes increased to number bytes to hold 1 row.

SQL*Loader-00600: Bind size of number bytes increased to number bytes to hold 1 row.

Cause: The space needed to contain a single row is longer than the specified bind size. The value used for the bind size will be increased to handle the larger size

Action: No action is required. This message will go away if the new value in the error message is specified for the bind size.

SQL*Loader-00569: READSIZE parameter exceeds maximum value string for platform

SQL*Loader-00569: READSIZE parameter exceeds maximum value string for platform

Cause: The value specified for the READSIZE parameter on the SQL Loader command line was larger than the maximum size allowed on the platform executing the SQL Loader command

Action: Decrease the size of the READSIZE parameter to be less than the maximum size allowed on the platform.

SQL*Loader-00568: error writing to file

SQL*Loader-00568: error writing to file

Cause: Unexpected error occured while writing to a file. This message is followed by another message with more information about the error.

Action: none

SQL*Loader-00567: unable to derive file name

SQL*Loader-00567: unable to derive file name

Cause: An error occured while attempting to build a name for a data file, bad file, discard file or log file.

Action: Instead of relying on SQL Loader to build these file names, try specifying full file specifications for these files in the control file or on the SQL Loader command line.

SQL*Loader-00566: partial record found at end of datafile

SQL*Loader-00566: partial record found at end of datafile

Cause: An incomplete record was found at the end of file.

Action: Make sure the last record in the datafile is complete and has the correct terminating character(s).

SQL*Loader-00565: unexpected error during skip .

SQL*Loader-00565: unexpected error during skip .

Cause: an unexpected error occured while attempting to skip records.

Action: This message should be followed by another message giving more specific information about the error

SQL*Loader-00564: illegal hexadecimal literal specified for record delimiter

SQL*Loader-00564: illegal hexadecimal literal specified for record delimiter

Cause: A hexadecimal literal that contains the record delimiter for the file does not contain a valid hexadecimal string.

Action: Verify that the correct hexadecimal value was specified in the processing options for the file.

SQL*Loader-00563: bad length for VAR record

SQL*Loader-00563: bad length for VAR record

Cause: The length protion of a VAR record contains non-numeric data.

Action: Fix the data in the file.

SQL*Loader-00562: record too big

SQL*Loader-00562: record too big

Cause: A record in the file is larder than the read buffer.

Action: Verify that the file is not corrupt. If not, try specifying a larger size for the read buffer.

SQL*Loader-00561: end of file

SQL*Loader-00561: end of file

Cause: End of file reached.

Action: none

SQL*Loader-00560: error reading file

SQL*Loader-00560: error reading file

Cause: An error occurred while reading the file.

Action: Make sure the file is still accessible.

SQL*Loader-00559: error closing file

SQL*Loader-00559: error closing file

Cause: An error occured while closing the file.

Action: Contact customer support.

SQL*Loader-00558: attempt to use SKIP parameter with linked-in loader

SQL*Loader-00558: attempt to use SKIP parameter with linked-in loader

Cause: SKIP parameter was specified with a linked-in file processor.

Action: Do not use the SKIP parameter in this case.

SQL*Loader-00557: unable to allocate memory

SQL*Loader-00557: unable to allocate memory

Cause: An attempt to allocate some memory to track I or O for the file failed.

Action: Contact customer support.

SQL*Loader-00556: unable to allocate read buffer

SQL*Loader-00556: unable to allocate read buffer

Cause: Attempt to allocate the read buffer failed.

Action: If possible, try specifying a smaller size for the read buffer.

SQL*Loader-00555: unrecognized processing option

SQL*Loader-00555: unrecognized processing option

Cause: The processing option specified for the file cannot be processed.

Action: Verify that the processing options specified for the file contain legal syntax for the platform where SQL*Loader is running.

SQL*Loader-00554: error opening file

SQL*Loader-00554: error opening file

Cause: An error occurred while trying to open the file. No further information is available.

Action: Verify that the file is accessible.

SQL*Loader-00553: file not found

SQL*Loader-00553: file not found

Cause: The specified file cannot be found.

Action: verify that the correct name exists and whether the file is in the intended location.

SQL*Loader-00552: insufficient privilege to open file

SQL*Loader-00552: insufficient privilege to open file

Cause: SQL*Loader does not have the previleges required to open the file.

Action: Verify that the correct file was specified and that the file has the appropriate permissions.

SQL*Loader-00551: internal error: error initializing slf

SQL*Loader-00551: internal error: error initializing slf

Cause: An internal error occured while trying to initialize the file I or O component.

Action: Call customer support.

SQL*Loader-00533: OCI return status: unknown, value is number

SQL*Loader-00533: OCI return status: unknown, value is number

Cause: An unknown status was returned by an OCI call.

Action: See surrounding messages for more information.

SQL*Loader-00532: OCI return status: continue

SQL*Loader-00532: OCI return status: continue

Cause: The message describes the status code returned by an OCI call.

Action: See surrounding messages for more information.

SQL*Loader-00531: OCI return status: still executing

SQL*Loader-00531: OCI return status: still executing

Cause: The message describes the status code returned by an OCI call.

Action: See surrounding messages for more information.

SQL*Loader-00530: OCI return status: need data

SQL*Loader-00530: OCI return status: need data

Cause: The message describes the status code returned by an OCI call.

Action: See surrounding messages for more information.

SQL*Loader-00529: OCI return status: invalid handle

SQL*Loader-00529: OCI return status: invalid handle

Cause: The message describes the status code returned by an OCI call.

Action: See surrounding messages for more information.

SQL*Loader-00528: OCI return status: error

SQL*Loader-00528: OCI return status: error

Cause: The message describes the status code returned by an OCI call.

Action: See surrounding messages for more information.

SQL*Loader-00527: OCI return status: no data

SQL*Loader-00527: OCI return status: no data

Cause: The message describes the status code returned by an OCI call.

Action: See surrounding messages for more information.

SQL*Loader-00526: OCI return status: success with info

SQL*Loader-00526: OCI return status: success with info

Cause: The message describes the status code returned by an OCI call.

Action: See surrounding messages for more information.

SQL*Loader-00525: OCI return status: success

SQL*Loader-00525: OCI return status: success

Cause: The message describes the status code returned by an OCI call.

Action: See surrounding messages for more information.

SQL*Loader-00524: partial record found at end of datafile (string)

SQL*Loader-00524: partial record found at end of datafile (string)

Cause: An incomplete record was found at the end of the indicated datafile.

Action: Make sure the last record in the datafile is complete and has the correct terminating character(s). Also, if fixed-length records are in use, verify that no record exceeds the platform-specific length for a single record.

SQL*Loader-00523: error number writing to file (string)

SQL*Loader-00523: error number writing to file (string)

Cause: Could not write to specified file.

Action: Check the following: the file actually resides in the specified location you have write privileges on the file you have sufficient disk space you have not exceeded your disk quota If all of these conditions are satisfied, then retry the operation.

SQL*Loader-00522: lfiopn failed for file (string)

SQL*Loader-00522: lfiopn failed for file (string)

Cause: LFI failed to open the file.

Action: Check for any possible operating system errors and or or potential memory problems.