00620-00649: Formatting

These are errors in data described by free-format (TERMINATED, ENCLOSED) statements in the control file. Format errors occur when the data does not meet format specifications and might cause the loading of incorrect data into the database. A format error causes the record to be written to the bad file because an attempt to insert data failed.

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-621 field in datafile exceeded maximum specified length

Cause:	Delimited data was specified with a maximum length, and the data value exceeded that length.

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

SQL*Loader-622 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-623 logical record ended -- second enclosure character not present

Cause:	The logical end of record occurred before a second enclosure delimiter was found.

Action:	Supply the missing delimiter.

SQL*Loader-624 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-625 multi-byte character error in control file

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

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

SQL*Loader-640 variable length field was truncated

Cause:	The end of the logical record was encountered before the end of a variable length field. The length of each variable-length field is embedded in the field, so SQL*Loader knows that more data should have been present.

Action:	Check the data for inadvertent truncation and verify the control file specifications against the log file -- the field may be starting in the wrong place.

SQL*Loader-641 invalid zoned decimal nibble

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

Action:	Check the 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-642 relative start position > 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.