SAND CDBMS Error Messages Guide
Ndlm Error Messages

 

This document lists and describes the errors that can be returned when using the SAND CDBMS Data Loader utility (ndlm) to import or export data to or from a SAND database. The error messages are divided into three categories:

Most of the entries describe the conditions that might generate the specified error, as well as possible resolutions to the problem.

 

Messages and Prompts

n row(s) loaded into table 'table-name'
ndlm displays this message at the conclusion of the data import process, just after the message indicating the number of records that were read from the data input file. This message indicates the number of records that were successfully written to the database (which is equal to the difference between the number of records read by ndlm and the number of records rejected by ndlm).

n row(s) not loaded, see file 'file-name'
This message is displayed at the conclusion of the data import process if errors occurred which resulted in the rejection of one or more records. It indicates the total number of rejected records and the name of the file to which they were written.

n row(s) read from file 'file-name'
This message is displayed at the conclusion of the data import process, and indicates the number of rows that were read from the data input file.

n row(s) rejected by PICTURE
ndlm displays this message during a load operation to indicate the number of rows that did not satisfy the filter conditions in the PIC clause. In the case of an import, these rejected records are saved to a file named input-file-name.pct (where input-file-name is the name of the source data file).

n row(s) rejected by SKIPIF
ndlm displays this message during a load operation to indicate the number of rows that satisfied the filter conditions in the SKIPIF clause. These skipped records are saved to a user-specified file, or if no file name was provided in the SKIPIF clause, to a file called specification-file-name.skp (where specification-file-name is the name of the load specification file).

n row(s) skipped in file 'file-name' due to empty line
ndlm displays this message during an import operation to indicate the number of empty rows skipped in the specified data file.

n rows selected
ndlm displays this message during an export operation to indicate the number of rows returned by the SELECT statement in the export specification file.

a SELECTed column was not specified in the record spec
This message is displayed when an EXPORT operation SELECT statement specifies a column that is not defined in the RECORD section. Each column referenced in the SELECT statement must have a corresponding field definition in the record specification area.

Cannot load into a table that has ENABLED constraints other than not null
This error is returned if the Parallel Loader attempts to load into a table on which one or more PRIMARY KEY, FOREIGN KEY, UNIQUE, and/or CHECK constraints are defined and enabled. A table cannot be loaded into when it has such constraints active (the NOT NULL constraint is the sole exception to this restriction). Before attempting the load operation again, use the SQL ALTER TABLE command to disable or remove the relevant constraints on the table.

Data Formatted Correctly ? Y/N
This prompt is issued during the import preview which displays the target columns for an import operation and the corresponding import data values from the first three records in the input file. Respond affirmatively to proceed with the import, or negatively to abort.

Error reading row n in 'file-name'
ndlm displays this message whenever an error occurs in reading a particular row from the data input file during import.

EXECSQL error with row n
This message is displayed when a specification file executing the EXECSQL command contains an erroneous SQL statement. This message will also display the error message returned from the database server and the SQL statement with the error.

'FIELDNAMESINFILE:' parameter required in CSVFORMAT() when loading from standard input.
This message is displayed when attempting to load CSV data from the standard input stream (stdin), if the first line of data does not contain the field names and the NUMBEROFFIELDS parameter is not specified in the CSVFORMAT section of the script. The NUMBEROFFIELDS parameter is required in this situation, so the load operation will be disallowed until the specification script is corrected.

Insufficient resources - DATA segment size limit is: n
This message is displayed because the operating system's data segment maximum size (n) is too low for ndlm to operate. The data segment size must be set to at least 1,048,576 KB. This can be accomplished with the ulimit -d system command.

Insufficient resources - number of file descriptors limit is: n
This message is displayed because the operating system's maximum number of file descriptors (n) is too low for ndlm to operate. The maximum number of file descriptors must be set to at least 256. This can be accomplished with the ulimit -n system command.

Inverting all columns at timestamp
This message is displayed at the beginning of the second phase (that is, index phase) of an import operation. It indicates the date and time that ndlm begins to index all of the columns loaded into the table in the first phase of the load.

Last output row = n
ndlm displays this message at the conclusion of an export operation indicating the number of rows written to the export file.

Multiple reading threads (-j > 1) not permitted when reading from a pipe; reverting to a single reading thread.
Multi-threaded reading cannot be performed with pipes, so ndlm will automatically switch to single-threaded reading if the -j parameter is set to a value greater than 1.

Multiple reading threads (-j > 1) not permitted when reading from CSV files; reverting to a single reading thread.
Multi-threaded reading cannot be performed with CSV files, so ndlm will automatically switch to single-threaded reading if the -j parameter is set to a value greater than 1.

Output n rows
This message is displayed by ndlm after each "chunk" of data has been written to the export file. This permits visual feedback of the export progress. You can roughly gauge the pace of the export from this display.

Row n doesn't have an impact on the database
This message is displayed during an EXECSQL operation, if an UPDATE/DELETE/INSERT Boolean condition evaluates to false for a value in the specified update file. That is, the target table is not altered by the SQL statement for the row containing the field value.

See 'file-name' for import session information
ndlm displays this final message at the conclusion of an import or export operation. It indicates the name of the file to which error and other log information has been written.

Skipping n bytes
This message is displayed whenever the -i invocation option or the IGNORE processing option is specified. The message provides confirmation of the number of bytes skipped before importing data.

Skipping n rows
This message is displayed whenever either the -s invocation option or the SKIP processing option is specified. The message provides confirmation of the number of rows skipped before importing data.

See 'file-name' for import session information
ndlm displays this final message at the conclusion of an import or export operation. It indicates the name of the file to which error and other log information has been written.

Output n rows
This message is displayed by ndlm after each "chunk" of data has been written to the export file. This permits visual feedback of the export progress. You can roughly gauge the pace of the export from this display.

 

Load-Time Errors and Warnings


ERROR 30101: IMPORT file 'file-name' not found
This error message is issued by ndlm when it cannot locate the file containing the data to be imported. Make sure that the file name specified on the first line of the import specification file is preceded by an "at" sign (@). Also, if the file is not located in the current working directory, make certain that the file name specification contains the correct path specification.

ERROR 30102: seek error on back scan
This error message indicates that an error was returned from the shell, indicating that a file I/O error occurred when ndlm tried to locate the last complete line in a variable length file.

ERROR 30103: SELECT statement exceeds available buffer space
This error is returned by ndlm during export when the size of a SELECT statement exceeds 16 KB.

ERROR 30104: no SELECT statement in the specification file
This error message is issued by ndlm when the SELECT statement could not be located in the export specification file. If the SELECT statement is indeed in the file, this error may be the result of improperly placed braces ( {} ).

ERROR 30105: SYNTAX ERROR in the specification file
This error message is issued by ndlm when a syntax error is found in the import or export specification file. Such an error is generally caused by missing or unbalanced syntax such as a missing keyword, a missing "at" sign ( @ ), or unbalanced braces or square brackets.

ERROR 30106: 'field-name' field description has multiple lengths [line x]
This error message is issued by ndlm when multiple field lengths are specified for the indicated field. This usually occurs when both an asterisk (*) and an integer are specified within a field-format, or when two separate "unescaped" integers are contained in a single field-format.

ERROR 30107: input file not record delimited
This error message is issued when ndlm does not detect the expected delimiter (usually, \r\n on the Windows platform, \n in UNIX) between records in the input file. Note that this returned if the delimiter character is incorrectly typed in the RECORD section of the load specification file (for example, if forward-slashes are used instead of back-slashes).

ERROR 30108: out of memory
This error message is returned when the operating system fails to meet a request for memory. ndlm uses memory for internal buffers and needs approximately 1 MB in addition to what the program itself occupies. If the error occurred on a UNIX platform, consult the Server Administration Guide for information about increasing user limits for the execution environment.

ERROR 30109: column 'column-name' not mapped to a field [line x]
This error message is issued by ndlm when the indicated column is not assigned to a field-label in the map specification part of an import specification file. It must be assigned to a field that is defined in the record specification part of the import specification file.

ERROR 30110: cannot create EXPORT file 'file-name'
This message is issued by ndlm if it cannot create the specified export data file. Make sure that you have sufficient directory access privileges before re-executing ndlm. Also, ensure that the specified export file does not have a name longer than 255 characters (including dot and extension), and does not contain illegal characters.

ERROR 30111: early end of file
This message is issued by ndlm when it encounters an end-of-file within the number of bytes specified for the -i or IGNORE processing option. An example would be a request to ignore n+1 bytes in an n-byte file.

ERROR 30112: processing interrupted
This message is issued by ndlm when a negative response (that is, 'N') is entered at the Data Formatted Correctly? prompt that follows the import preview.

ERROR 30113: disk full!!!
This message is issued when the disk on which the database file resides becomes full during import, or when the disk to which the export file is being written becomes full during export. Make the appropriate space adjustments before re-executing the import or export.

ERROR 30114: field specifier error: x ( or field specifier, length <= zero; or column in select statement not specified in record spec)
One of these messages is issued when an error is encountered while parsing the specification file. There are four different variations of this message depending upon the value of x: i) a selected column is not represented in the record specification, ii) a column has no specified length, iii) a column has too great a length, and iv) no delimiter is specified for a variable length field (indicated by an asterisk). Diagnoses of these problems can be found by looking at explanations of the following messages respectively: 30109, 30126, 30116, and 30105.

ERROR 30115: input data mismatch
Issued when an input file record format is inconsistent with the record specification description contained in the import specification file. This frequently occurs when the record specification indicates that there is an end-of-line terminating each record (that is, \r\n on the Windows platform, \n in UNIX), and there is no end-of-line found after the last record in the input file.

ERROR 30116: input data longer than the field MAXIMUM (4056)
Issued when character data in a variable-length field exceeds 4056 characters. This is the maximum permissible number of characters for a variable-length character column in SAND CDBMS SQL. The offending record is rejected and written to the input-file.BAD file, where input-file is the name of the input data file identified in the import specification file.

ERROR 30117: export record definition not record delimited
This error is returned when the export record definition does not include a end-of-line terminator (that is, \r\n on the Windows platform, \n in UNIX) indicating the end of a record. Note that the end-of-line terminator is required when transporting data to another instance of ndlm through a named pipe.

ERROR 30118: early end of buffer
This message is returned when ndlm scans a flat file and exhausts the current buffered segment before encountering a field terminator. This is most likely to occur when a scan for the delimiter character in a variable length field does not find the delimiter.

ERROR 30119: cannot open file 'file-name'
ndlm cannot open the indicated file. Make sure that you have sufficient access privileges and that the file is not damaged. Also, ensure that the timing file or log file (specified with, respectively, the -t or -e ndlm invocation flags) does not have a name longer than 255 characters (including dot and extension).

ERROR 30120: IMPORT datafile record length specified as zero
Returned when the specification file for an EXPORT operation contains no record definitions in the RECORD section.

ERROR 30121: argument is not a valid x option
The indicated option is not a valid ndlm invocation option. (Refer to the SAND CDBMS Tools Reference Guide for a description of all legal ndlm invocation options.)

ERROR 30122: flag option must have a filename argument
Issued when either of the invocation options -e or -t is specified without a file name argument. Refer to the SAND CDBMS Tools Reference Guide for a description of these two invocation options.)

ERROR 30123: -V option cannot be used with -B option
This error message is issued by ndlm when the invocation options -b and -v are specified in the same invocation (-v instructs ndlm to issue a prompt, and -b instructs ndlm to suppress prompts).

ERROR 30126: no length has been specified for <field-label or column-name>
Issued when the field-format for the indicated field-label or column in the import or export specification file fails to specify a field length. Either an integer indicating a specific length, or an asterisk (*) indicating variable length, must be specified.

ERROR 30127: 'flag-value' is not a valid number for option-flag option
Issued when an invocation or processing option is encountered which specifies an invalid numerical argument.

WARNING 30128: input record n: width (x) of field field-name is too long - column width is defined as y
or
WARNING 30128: input record n: width is too long
Issued when ndlm, in processing a record from the input file, finds that the data contained in a particular field exceeds the defined length of the target database column. ndlm will truncate the data rather than rejecting the record.

ERROR 30129: unexpected error during FETCH
This error message is returned by SAND CDBMS during an export operation. It indicates that an error has occurred in the FETCH command which returns data from the server to ndlm. This generally indicates an error at the server; the export operation should be re-executed.

ERROR 30130: 'x' is not a valid field/table/column name
This error message is issued by ndlm because the indicated name is an invalid field name, table name, or column name. This might be caused by an illegal field name, a field name in the map specification that does not appear in the record specification, a table name that does not exist in the specified database, or a column name that does not belong to the specified table.

ERROR 30131: Nothing to import (or export). Too many rows skipped!
This message is issued by ndlm prior to an import or export when the -s invocation option (or SKIP processing option) specifies that more rows be skipped than exist in the input data file (import), or than are returned by the export SELECT statement.

ERROR 30132: fatal error in IGNORE bytes option
This error message is issued when ndlm attempts to IGNORE the specified number of bytes, and the operating system returns an error. This usually indicates file damage or file system corruption.

ERROR 30136: attempt to load unprintable character
Returned when ndlm was invoked with the -z 0 option flag and a specified data file contains an unprintable character in one of the input fields. The -z 0 option instructs ndlm to reject any rows in the data load that contain an unprintable character; the rejected rows are written to the specification-file-name.BAD file. Specify the -z 1 option to have ndlm replace each unprintable character with an ASCII space character. Include -z 2 in the ndlm invocation, or else omit the -z option entirely, if you wish to load data as is into a SAND database, even if they contain unprintable characters.

ERROR 30138: IMPORT/EXPORT file name missing from the specification file
Issued when the import or export file (as defined by specification file syntax) is not found. Make sure that the file name is specified accurately and prefixed by the "at" sign ( @ ).

ERROR 30139: mapping error between fields specified and columns selected
This error message is issued by ndlm during an export operation when there is a problem mapping fields in the RECORD section with columns in the SELECT statement. One of three possible secondary messages is included, specifying the exact nature of the problem:

Number of fields specified exceeds number of columns selected
There are more fields in the RECORD section than columns referenced in the SELECT statement, so one or more fields are not used.

Selected columns contain duplicates
The SELECT statement projection list includes multiple references to the same column.

Field specified doesn't map to selected columns
A field in the RECORD section is not specified as a column in the corresponding ordinal position in the SELECT statement projection list.

WARNING 30140: x already defined, duplicate ignored
This warning message is issued by ndlm when duplicate invocation options or processing options are entered in the ndlm invocation or specification file. Only the first instance is used; duplicates are ignored.

WARNING 30141: missing parameter for x, option ignored
This warning message indicates that an invocation or processing option which requires an argument was specified without the argument, and will therefore be ignored. Refer to the SAND CDBMS Data Loader (ndlm) chapter in the SAND CDBMS Tools Reference Guide for a description of legal ndlm options and arguments.

WARNING 30142: Found n error(s) during IMPORT. Keep going? Yes/No
This warning message is issued by ndlm when the number of errors incurred reaches the number specified with the -m invocation option or the MAXERR processing option. Respond affirmatively to continue importing, or negatively to abort the import.

WARNING 30143: User specified zero rows to process. Program Terminating.
Issued when the argument specified with the -p invocation option or the PROCESS processing option is zero (0).

WARNING 30144: field width of x does not match column width of y
This message is issued by ndlm during an export operation when the width of a column and the width of the corresponding field do not match. Processing continues, but the exported field may be truncated.

ERROR 30145: [input record n:] UNIQUE violation
Issued when a UNIQUE column or table constraint is violated during import. The offending record is rejected and written to the input-file.BAD file, where input-file is the name of the input data file that is identified in the import specification file.

ERROR 30146: [input record n:] NULL violation
This error message is returned by SAND CDBMS when a NOT NULL column constraint is violated during import. The offending record is rejected and written to the input-file.BAD file, where input-file is the name of the input data file that is identified in the import specification file.

ERROR 30147: [input record n:] incompatible datatype
This error message is returned by SAND CDBMS when the data value to be imported has a data type that cannot be accommodated by the data type of the target database column. This usually occurs during inadvertent attempts to import character data into numeric columns. There are, however, other mismatch possibilities (refer to the SAND CDBMS SQL Reference Guide for more information on data types and compatibility). The offending record is rejected and written to the input-file.BAD file, where input-file is the name of the input data file that is identified in the import specification file.

ERROR 30148: [input record n:] numeric truncation error
This error message is returned by SAND CDBMS when a numeric value is assigned to a column whose data type is INTEGER, DECIMAL, or FLOAT (including REAL and DOUBLE PRECISION) and the declared precision is insufficient to accommodate all of the digits of the assigned value. The offending record is rejected and written to the input-file.BAD file, where input-file is the name of the input data file that is identified in the import specification file.

ERROR 30149: [input record n:] integer outside range
This error message is returned by SAND CDBMS when a value outside the range -32,767 <= n <= 32,767 is assigned to a column defined as SMALLINT, or when a value outside the range -2,147,483,647 <= n <= 2,147,483,647 is assigned to a column defined as INTEGER. The offending record is rejected and written to the input-file.BAD file, where input-file is the name of the input data file that is identified in the import specification file.

ERROR 30150: [input record n:] string truncation error
This message is returned when an asynchronous load operation inserts a string value that is wider than the destination column. The inserted value is truncated on the right side to fit the size of the column.

ERROR 30151: attempt to load invalid character
Returned when the input data contains a character that cannot be loaded by ndlm. For example, the nul character (ASCII code 00) will generate this error. Ensure that the source data do not contain unprintable or invalid characters.

ERROR 30152: writing to named pipe. Client connection was closed
An error occurred while writing to a a named pipe. The client process shut down unexpectedly, or there was a network error preventing communication with the client. Consult the system/network administrator for help with troubleshooting this error.

ERROR 30153: [input record n:] DATE/TIME value is invalid
Returned when attempting to load an invalid value into a DATE or TIME column. Note that a DATE value must be in one of the following formats:

where mm is month, DD is day, and yyyy is year.

A TIME value must be in one of the following formats:

where hh is hour, mm is the minutes, and ss is the seconds.

WARNING 30154: maximum # of errors reached, stopping load
Returned when the number of errors specified with the -m flag is reached.

WARNING 30155: defaulting -k option to 32 threads
Returned when an invalid number is used for the -k option. A user-specified -k value must be between 0 and 32.

WARNING 30156: missing specified flat file "file-name" skipped
Returned when multiple flat files are referenced in the specification file, and at least one of them could not be found.

ERROR 30157: maximum reading threads exceeded. n specified, only one allowed in standard mode
Returned when attempting to execute the standard loader with the -j option enabled. The -j flag (for setting the number of reading threads) can be used only with the Parallel Loader.

ERROR 30158: null violation, row x, column y (col-name)
This error message is returned by SAND CDBMS when a NOT NULL column constraint is violated during import. The offending record is rejected and written to the input-file.BAD file, where input-file is the name of the input data file that is identified in the import specification file.

ERROR 30159: bad data type conversion, row x, column y (col-name)
This error message is returned by SAND CDBMS when the data value to be imported has a data type that cannot be accommodated by the data type of the target database column. This usually occurs during inadvertent attempts to import character data into numeric columns. There are, however, other mismatch possibilities (refer to the SAND CDBMS SQL Reference Guide for more information on data types and compatibility). The offending record is rejected and written to the input-file.BAD file, where input-file is the name of the input data file that is identified in the import specification file.

ERROR 30160: numeric truncation, row x, column y (col-name)
This error message is returned by SAND CDBMS when a numeric value is assigned to a column whose data type is INTEGER, DECIMAL, or FLOAT (including REAL and DOUBLE PRECISION) and the declared precision is insufficient to accommodate all of the digits of the assigned value. The offending record is rejected and written to the input-file.BAD file, where input-file is the name of the input data file that is identified in the import specification file.

ERROR 30161: integer outside range, row x, column y (col-name)
This error message is returned by SAND CDBMS when a value outside the range -32,767 <= n <= 32,767 is assigned to a column defined as SMALLINT, or when a value outside the range -2,147,483,647 <= n <= 2,147,483,647 is assigned to a column defined as INTEGER. The offending record is rejected and written to the input-file.BAD file, where input-file is the name of the input data file that is identified in the import specification file.

ERROR 30162: character truncation, row x, column y (col-name)
This message is returned when an asynchronous load operation inserts a string value that is wider than the destination column. The inserted value is truncated on the right side to fit the size of the column.

ERROR 30163: SCT file already exists
Returned when the load script SCTFILE parameter specifies a file that already exists. To prevent accidental loss of metadata, ndlm will not overwrite an existing SCT File; it will have to be renamed or moved, or the SCTFILE value will have to be changed, before the IMPORT operation begins.

ERROR 30164: IMPORT file specifies no columns to load
Returned when the IMPORT specification script does not specify any columns to load. The specification script is considered to be incomplete in this case.

WARNING 30165: numeric truncation during export, row n, column x
Returned when a fixed length output field is defined in the export specification script, and it is not large enough to store an exported numeric value. The export operation is not interrupted when this occurs; the value is exported, but is truncated to fit the defined field.

WARNING 30166: missing specified SCT file file-name, skipped
Returned when an SCT File referenced in the load specification script could not be found. The load operation will skip the missing SCT File, and continue to process the other SCT Files specified in the script, if applicable.

ERROR 30167: No valid TEMPDRIVE path was found or access denied: path
Returned when the TEMPDRIVE parameter in the NUCLEUS environment variable has been set to paths that do not exist, or the user does not possess the permissions required to access the directories. Ensure that the correct temporary drives are specified by the TEMPDRIVE parameter, and that clients have been given the necessary permissions on them.

WARNING 30168: loading with no target

WARNING 30169: One or more TEMPDRIVE paths do not exist
One or more of the paths specified for the TEMPDRIVE parameter in the NUCLEUS environment variable are invalid. This will not interrupt a load operation, unless all of the temporary drives are invalid. Verify that the correct TEMPDRIVE paths are set.

ERROR 30170: Too many rows for SCT file
The operation attempted to load more rows than the maximum permitted for a single SCT File (231 or 2,147,483,648). The job will have to be partitioned and multiple SCT Files created.

WARNING 30171: no records selected, stopping SCT file creation
The defining SELECT statement in an SCTEXPORT or ODBCIMPORT operation has produced an empty result set. No SCT File is created in this situation.

ERROR 30172: input buffer is too small for the number of reading threads specified: -j n
The input buffer size (set with the -f option) cannot support the specified number of reading threads. Retry the loader operation either with a lower number of reading threads or with the input buffer set to a higher value; or else do not set the input buffer manually, but rather allow ndlm to determine the buffer size automatically.

ERROR 30173: Too many rows for one load
The operation attempted to load more rows than the maximum permitted for a single load operation (231 or 2,147,483,648). The specification script and source data will have to be partitioned, and the load will have to be performed over multiple sessions.

ERROR 30174: Imported/exported number of bytes exceeds licensed amount

ERROR 30175: Unsupported collation for SCT file
This error is returned during an SCTEXPORT or ODBCIMPORT operation intended to create an SCT File, when one or more character columns in the source table are defined with an unsupported collation. At present, only BINARY collation is permitted for SCT Files.

ERROR 30176: General loader error
A general error occurred during data processing. A number of different situations can produce this error. Examine the diagnostic message that accompanies this error for information about the source of the error.

ERROR 30177: COMMIT failed
The database server failed to execute a COMMIT command during the loader operation.

ERROR 30178: ROLLBACK failed
The database server failed to execute a ROLLBACK command during the loader operation.

ERROR 30180: -k option required to create the SCT file
A loader operation to create an SCT File was initiated in standard mode, instead of Parallel Loader mode (ndlm -k). SCT Files can only be generated using the Parallel Loader. Retry the operation, invoking ndlm with the -k parameter to activate the Parallel Loader and set the number of processing threads.

WARNING 30181: numeric value rounding in column col-name from scale x to scale y
This warning is returned during a load operation if the DECIMAL scale in the target column is less than the scale in the source column. The values will be loaded, but the scale of the data will be rounded to fit the target column.

 

Load Specification Script Errors

Note:
Where applicable, the file name and line number where the error was found will also be returned with the error message.


NDLERROR 0001. MAXERR statement has been defined more than once.
Returned when the MAXERR option is specified two or more times. A MAXERR statement can appear only once in the specification file.

NDLERROR 0002. ERRINC statement has been defined more than once.
Returned when the ERRINC option is specified two or more times. An ERRINC statement can appear only once in the specification file.

NDLERROR 0003. PROCESS statement has been defined more than once.
Returned when the PROCESS option is specified two or more times. A PROCESS statement can appear only once in the specification file.

NDLERROR 0006. IGNORE statement has been defined more than once.
Returned when the IGNORE option is specified two or more times. An IGNORE statement can appear only once in the specification file.

NDLERROR 0007. SKIP statement has been defined more than once.
Returned when the SKIP option is specified two or more times. A SKIP statement can appear only once in the specification file.

NDLERROR 0008. NULL statement has been defined more than once.
Returned when the NULL option is specified two or more times. A NULL statement can appear only once in the specification file.

NDLERROR 0009. Invalid file name: 'file-name'.
Returned when a specified data file name is considered invalid by the operating system. A data file name must adhere to the naming rules of the operating system where it is saved. On a Windows platform, the file name must be less than 256 characters in length, and may not contain any of the following symbols:

\ ? | > < : / * "

On a UNIX system, the file name must be less than 256 characters in length. Almost any character can be used in a UNIX file name, but it is recommended that names be limited to alphabetic characters, numbers, periods ( . ), underscores ( _ ), and dashes ( - ).

NDLERROR 0010. Field 'field-name' has been defined more then once.
There are two or more fields with the same name in the record specification section. Each field must have a unique name.

NDLERROR 0011. Invalid picture specification on field 'field-name'.
Returned when a PIC clause contains an invalid formatting string. Refer to "Verifying and Filtering Data Using the PIC Clause" in the SAND CDBMS Data Loader (ndlm) chapter of the SAND CDBMS Tools Reference Guide for a full description of the PIC clause.

NDLERROR 0013. Missing field specification: 'field-name'
Returned when an undefined field is referenced in a variable definition. Ensure that all referenced fields are defined in the record specification section.

NDLERROR 0014. Invalid field length specification: 'field-name'.
Returned when a field definition contains an invalid field length specification. The field length specification must be one of the following:

NDLERROR 0015. Field 'field-name' is referencing an undefined field.
Occurs when a field specification references (‘remaps’) another field that has not been defined. Ensure that all referenced fields are defined, and that each referenced field is defined before the field that remaps it in the record specification section.

NDLERROR 0016. Illegal remapping of field 'field-name'.
Returned when a record definition contains an invalid field remapping. For instance, a field cannot remap itself:

field1 (field1:1:2)

Ensure that each field remapping references a valid field before attempting the load operation again.

NDLERROR 0017. Column 'column-name' has been defined more than once.
A column in the map specification section is defined more than once. Each column included in the load operation must have a single definition.

NDLERROR 0018. Column 'column-name' is referencing an undefined field 'field-name'.
This error is returned when an undefined field appears in the map specification section. Ensure that all the fields referenced in the map specification section have a corresponding field definition in the RECORD section. If field-name is in fact a variable name, note that variables are referenced by prefixing the variable name with “%”; that is, %variable-name. Omitting the “%” will result in this error message.

or

NDLERROR 0018. Undefined field 'field-name' found in SKIPIF clause.
This error is returned when an undefined field appears in a SKIPIF statement. Ensure that all the fields referenced in the SKIPIF statement have a corresponding field definition in the RECORD section. If field-name is in fact a variable name, note that variables are referenced by prefixing the variable name with “%”; that is, %variable-name. Omitting the “%” will result in this error message.

NDLERROR 0019. Invalid file name found in SKIPIF: filename
Returned when a specified SKIPIF file name is considered invalid by the operating system. The SKIPIF file name must adhere to the naming rules of the operating system where it is saved. On a Windows platform, the file name must be less than 256 characters in length, and may not contain any of the following symbols:

\ ? | > < : / * "

On a UNIX system, the file name must be less than 256 characters in length. Almost any character can be used in a UNIX file name, but it is recommended that names be limited to alphabetic characters, numbers, periods ( . ), underscores ( _ ), and dashes ( - ).

NDLERROR 0020. Invalid position value in 'field-name' (must be >= 1 and <= 8192).
Returned when a RECORD section field mapping (or remapping) specifies a start position value that does not fall within the acceptable range. A field (re)mapping position value must be between 1 and 8192 inclusive.

NDLERROR 0021. Invalid length value in 'field-name' (must be >= 1 and <= 8192).
Returned when a RECORD section field mapping (or remapping) specifies a length value that does not fall within the acceptable range. A field (re)mapping length value must be between 1 and 8192 inclusive.

NDLERROR 0022. Invalid field mapping specification: 'field-name'.
Returned when an invalid field remapping appears in the record specification area. Field remapping, where a field or part of a field is used as the source for another field (thus creating “sub-fields”), is defined using the following syntax:

( reference-field-name : position : length )

where reference-field-name is the name of the field being remapped, position is the starting position of the sub-field within the referenced field, and length is the length of the sub-field (in characters).

NDLERROR 0023. Unable to open rejected rows file: 'file-name'
Returned when ndlm could not open, create, or write to a file containing the rows rejected during the load operation. The rejected rows file is called input-file.BAD, where input-file is the name of the data file containing the rows that were rejected. The rejected rows file is saved in the same directory as the specification file. This error might occur if the user executing ndlm does not possess the appropriate access permissions on the rejected rows file (if it already exists) or the directory where it is stored. The error might also occur if the rejected rows file has been locked by another process. Ensure that write permission is granted on the relevant files and directories, and that no other process is using the rejected rows file, before attempting the load operation again.

NDLERROR 0024. Invalid position reference for field 'field-name'.
Returned when a field definition includes a NULLIF or MISSINGIF clause that uses the field mapping format. For instance:

field1 (1:5) NULLIF (1:2) == 'ab'

The field mapping format cannot be used with the NULLIF and MISSINGIF clauses. If you wish to use a subset of a field in these clauses, use the LEFT(), RIGHT(), or MID() functions to return the substring.

or

NDLERROR 0024. Invalid position reference in SKIPIF.
Returned when the SKIPIF clause uses the field mapping format. For instance:

SKIPIF (20:4) == 'xxxx' @test.skp

The field mapping format cannot be used in the SKIPIF clause. Reference fields by name. If you wish to use a subset of a field in this clause, use the LEFT(), RIGHT(), or MID() functions to return the substring.

NDLERROR 0025. Error found in SQL INSERT.
There was a syntax error in the EXECSQL INSERT statement. Ensure that the INSERT statement is correct, and then re-attempt the load operation.

NDLERROR 0026. Error found in SQL DELETE.
There was a syntax error in the EXECSQL DELETE statement. Ensure that the DELETE statement is correct, and then re-attempt the load operation.

NDLERROR 0027. Error found in SQL UPDATE.
There was a syntax error in the EXECSQL UPDATE statement. Ensure that the UPDATE statement is correct, and then re-attempt the load operation.

NDLERROR 0028. Unclosed comment.
Returned when a start of comment indicator ( /* ) appears without an end of comment indicator ( */ ). Ensure that all comments are “closed”.

or

NDLERROR 0028. Token is too large.
Returned when a script element, such as an SQL command or an ODBC connection string, exceeds 256 KB (262,144 characters). Ensure that each individual NDL script element is not longer than 262,144 characters, as this is the maximum size that can be processed by ndlm.

or

NDLERROR 0028. Invalid SQL statement 'x'.
Returned when an EXPORT or EXECSQL command contains an erroneous SQL statement. Usually, this means that the SQL statement is missing a terminating semicolon ( ; ).

or

NDLERROR 0028. Invalid token 'x'.
An invalid NDL script element appears in the specification file at the indicated line. Make the necessary corrections, and then re-attempt the load operation.

NDLERROR 0029. Illegal expression type found. Expected <type>.
Returned when an expression evaluates to a data type that is not expected where the expression is used. Ensure that the expression is correct, and that the correct data type is produced. If necessary, “cast” values to the expected data types. For example, INT(value1) will produce an int value (provided that value1 is composed entirely of numeric characters) .

NDLERROR 0030. Unknown program error during the parsing.
An unspecified error occurred while ndlm read the specification file. Re-attempt the data load. If the problem persists, contact a SAND support representative.

NDLERROR 0031. Invalid pipe name: 'pipe-name'.
Returned when a specified pipe name is considered invalid by the operating system. A pipe name must adhere to the naming rules of the operating system where it is used. On a Windows platform, the pipe name must be less than 256 characters in length, and must not contain any of the following symbols:

\ ? | > < : / * "

On a UNIX system, the pipe name must be less than 256 characters in length. Almost any character can be used in a UNIX pipe name, but it is recommended that names be limited to alphabetic characters, numbers, periods ( . ), underscores ( _ ), and dashes ( - ).

NDLERROR 0032. ODBC driver connection error.
An ODBCIMPORT operation could not be performed. Proper operation of ODBC depends upon the ODBC drivers. On the Windows side, problems sometimes occur if these drivers have DLL files with mismatched versions or missing DLL files. If necessary, reinstall or update the ODBC drivers.

This error may also indicate a problem with shared network connections. In this case, consult your network administrator for help with troubleshooting this problem.

NDLERROR 0033. Field 'field-name' already declared.
Occurs when a field is declared more then once in a TYPE clause. Each field must have a unique name and can be declared only once.

NDLERROR 0034. Variable 'variable-name' already defined.
Occurs when a variable is defined more than once. Each variable must have a unique name and can be defined only once.

NDLERROR 0035. Wrong number of arguments in 'function-name' function call. Must be at least x.
Occurs when a function is called with the incorrect number of arguments. The number of arguments passed to the function is less than the minimum number of arguments required by the function.

or

NDLERROR 0035. Wrong number of arguments in 'function-name' function call. Must be maximum x.
Occurs when a function is called with the incorrect number of arguments. The number of arguments passed to the function exceeds the maximum number of arguments permitted by the function.

NDLERROR 0036. Invalid expression.
Signals a general expression error. Ensure that the expression is correctly formed, and then re-attempt the load operation.

NDLERROR 0037. Variable 'variable-name' is recursively referenced.
Occurs when a variable references itself in the variable declaration section. For example:

VAR
{
V1 (%V1)
}

NDLERROR 0038. Variable 'variable-name' is referenced but not defined.
Occurs when a variable is referenced in an expression, but is not defined in the VAR section. This error may also be returned if a variable references another variable that is not yet defined in the variable declaration list. For example:

VAR
{
V1 (%V2 + 'world')
V2 ('hello ')
}

V2 must be defined prior to V1 in order for the definition of V1 to be valid.

NDLERROR 0039. Data type <data-type1> can't be assigned to column "column-name". Expected <data-type>.
Occurs when the data type of the expression is not compatible with that of the column to which it is assigned. Consult the SAND CDBMS SQL Reference Guide for further information about compatible data types.

NDLERROR 0040. Unknown function found: 'function-name'.
Occurs when an identifier that is not recognized as a function is used as a function name. Consult the NDL++ Scripting Functions chapter of the SAND CDBMS Tools Reference Guide for a description of the valid NDL functions.

NDLERROR 0041. Illegal data type <data-type1> for argument number x in 'function-name' function. 'function-name' requires <datatype> not <data-type1>.
The wrong data type was passed to a function. Ensure that the correct values are being passed to the function. If necessary, “cast” the value to the data type expected by the function. For example:

TRUNC( FLOAT(field1) )

If the value is numeric and the function expects a string, use the STR() function to convert the value. For example:

STR(123)

or

NDLERROR 0041. Illegal arguments in call of function 'function-name' found.
Returned when there is a general error involving the arguments in a function call. Ensure that the correct data types and number of parameters are being sent to the function.

or

NDLERROR 0041. Invalid operator for data type(s). <data type list> not operable by '<function-name or operator-type>'.
Returned when attempting an arithmetic operation involving a string value. Arithmetic expressions are limited to the int and float data types.

NDLERROR 0048. Unexpected script-element in file 'file-name' at line x.
An NDL script element was found in an inappropriate location in the specification file. A script element can be one of the following:

identifier x
integer constant x
float constant x
string x
field delimiters x
file name x
picture specification x
NULL string x
SQL command x
"MAXERR" keyword
"ERRINC" keyword
"SELFREF" keyword
"IGNORE" keyword
"PROCESS" keyword
"RECORD" keyword
"IMPORT" keyword
"EXPORT" keyword
"EXECSQL" keyword
"SKIP" keyword
"SKIPIF" keyword
"TABLE" keyword
"PIC" keyword
"NULL" keyword
"NULLIF" keyword
"MISSINGIF" keyword
"SQL" keyword
"UPSERT" keyword
"ALTERNATESQL" keyword
"ELSE" keyword
"INSERT" keyword
"DELETE" keyword
"UPDATE" keyword
"*"
"{"
"}"
"( "
")"
":"
"~"
"!"
"=="
"!= "
" < "
" <= "
" > "
" >= "
" && "
" || "
End-of-file (EOF)

NDLERROR 0049. Missing directive in file 'file-name' at line x found script-element.
Indicates that an IMPORT, EXPORT, or EXECSQL command keyword was not found at the required position.

NDLERROR 0050. Illegal directive in file 'file-name' at line x found script-element.
Indicates that some other character string was found instead of an IMPORT, EXPORT, or EXECSQL command keyword at the required position.

NDLERROR 0051. Missing file specification in file 'file-name' at line x found script-element.
Indicates that the file name for the input file was not specified, or the file name was not preceded by the '@' symbol.

NDLERROR 0052. Missing value or command specification in file 'file-name' at line x found script-element.
Indicates that a PROCESS or SKIP keyword was not followed by a parameter value.

NDLERROR 0053. Illegal command specification in file 'file-name' at line x found script-element.
Returned when the record specification section is omitted, or a function is called from an inappropriate location in the script. Ensure that there is a record specification section; this is a required element of the specification file.

NDLERROR 0054. Missing section specifier in file 'file-name' at line x found script-element.
Indicates that an opening section delimiter ( { ) was found without a corresponding section name.

NDLERROR 0055. Missing section opening delimiter in file 'file-name' at line x found script-element.
Indicates that a section name was found without a corresponding opening delimiter ( { ).

NDLERROR 0056. Invalid field specifier in file 'file-name' at line x found script-element.
Indicates that no valid field identifier was found after the opening section delimiter.

NDLERROR 0057. Missing field specifier in file 'file-name' at line x found script-element.
Indicates that a reserved word was found after the opening section delimiter.

NDLERROR 0058. Missing field definition in file 'file-name' at line x found script-element.
Indicates that a field in the RECORD specification lacks a defined field format. Complete the field definition at the cited line number, and then re-attempt the load operation.

NDLERROR 0059. Invalid field definition in file 'file-name' at line x found script-element.
Indicates an error in a field-length specification. Note that variable length fields require at least one trailing delimiter.

NDLERROR 0061. Illegal clause in file 'file-name' at line x found script-element.
Indicates that an unexpected script element appears after a field definition. The following elements will generate this error message if they follow a complete field definition:

NDLERROR 0062. Illegal expression in file 'file-name' at line x found script-element.
Indicates that an expression is incorrectly formed, or absent altogether in a location where it is expected. Ensure that the expression exists and is valid, and then re-attempt the ndlm operation.

NDLERROR 0063. Missing section closing delimiter in file 'file-name' at line x found script-element.
Indicates that a section is missing its closing delimiter ( } ).

NDLERROR 0064. Missing table specification in file 'file-name' at line x found script-element.
The destination table for the load is not provided, or is not in the expected location. Ensure that the table name appears in the script before the delimited map specification area as follows:

[schema-name.]table-name
{
<map specification>
}

NDLERROR 0065. Null value too long, must be <= 256.
Returned when the NULL option is included in the script with a string value more than 256 characters in length. The null indicator string must be 256 characters or less.

NDLERROR 0066. Delimiter string too long, must be <= 256.
Returned when a field delimiter string in the record specification section is more than 256 characters in length. Field delimiters must be 256 characters or less.

NDLERROR 0067. Field name too long, must be <= 256.
Returned when a field name in the record specification section is more than 256 characters in length. Field names must be 256 characters or less.

NDLERROR 0068. Picture specification too long, must be <= 256.
Returned when a PIC clause formatting string is more than 256 characters in length. PIC clause formatting strings must be 256 characters or less.

NDLERROR 0069. File name too long, must be <= 260.
Returned when the specification file contains a SKIPIF, DSNFILE, or export file name that is 256 or more characters. Specified file names must be 255 or fewer characters (including the dot and extension) in length.

NDLERROR 0070. Column name too long, must be <= 256.
Returned when a referenced column name is more than 256 characters in length. Note that SAND database column names have a maximum length of 128 characters.

NDLERROR 0071. Character constant too long, must be <= 1024.
Returned when a character constant longer than 1024 characters in length appears in the specification file. If a string longer than 1024 characters is required, define multiple variables in the VAR section, each a subset of the full string. Another variable can then be defined using the concatenation of these substring variables, for example:

VAR
{
VAR1 'substring1'
VAR2 'substring2'
VAR3 'substring3'
VARSTRING (%VAR1 + %VAR2 + %VAR3)
}

The “VARSTRING” variable can be referenced wherever the full string is required. For instance:

table1
{
col1 %VARSTRING
}

NDLERROR 0072. Table name too long, must be <= 256.
Returned when a referenced table name is more than 256 characters in length. Note that SAND database table names have a maximum length of 128 characters.

NDLERROR 0080 Error reading information from the first row in CSV file.
Returned when there is a problem with the optional CSV header row. Possible issues include the following:

NDLERROR 0083. Maximum number of fields/columns exceeded. Current limit is 4096.
Returned if the number of fields or columns specified in the load specification script is greater than the maximum of 4096.

NDLERROR 0084. Number of fields specified in NUMBEROFFIELDS does not match number of fields in the first row in CSV file.
Returned if the number of fields specified for the NUMBEROFFIELDS parameter in the CSVFORMAT section of the load specification script differs from the actual number of fields in the CSV file. Since the NUMBEROFFIELDS parameter is intended for error-checking, this discrepancy will halt the load operation. Before retrying the load operation, verify that the correct CSV file is being specified. If necessary, change the value of NUMBEROFFIELDS, or else disable field error-checking by either setting NUMBEROFFIELDS to 0 or removing that parameter from the script.

NDLERROR 0096. Invalid position value in (pos:len). position (must be >= 1).
Occurs when a starting position less than 1 is specified in a field mapping declaration. This error would be returned in response to the following example:

(-10:3)

NDLERROR 0097. Invalid length value in (pos:len). length (must be >= 1 && <= 4056).
Occurs when an invalid length is specified for a field mapping declaration. The length value must be between 1 and 4056 inclusive. This error would be returned in response to the following example:

(10:-3)

NDLERROR 0098. A sign is not allowed for a non-numeric operand. Field 'field-name'.
Returned when a plus or minus sign prefixes a string value, for example, +S. A sign can only be used with int and float values.

NDLERROR 0099. Unable to locate 'ODBC-library' file.
The ODBC driver required for the ODBCIMPORT operation could not be found. If the DSNSTR option is used in the specification file, ensure that the specified ODBC driver exists and is spelled correctly. If the DSNFILE option is used, ensure that the specified file DSN contains the correct ODBC driver path location.

NDLERROR 0100. Unable to find function function-name() in 'ODBC-library'.
An internal error occurred while attempting an ODBC import. If importing from a SAND database, make sure that the latest version of the Nucleus ODBC Driver is installed. If the problem persists, contact a SAND support representative. If another ODBC driver is being used, contact the developers of that driver for help with troubleshooting the problem.

NDLERROR 0101. Can't open DSN file 'DSN-file-path'.
Returned when the file DSN could not be found in the path specified with the DSNFILE option, or the file DSN is locked by another process. Ensure that the path is correct, and that no other process is using the file DSN. If necessary, create a new file DSN with the path specified; or else use the DSNSTR option in conjunction with an appropriate connection string.

NDLERROR 0102. DSN file 'DSN-name' doesn't exist on the registry.
On the Windows platform, the specified DSN name could not be found in the system registry. Ensure that the spelling of the DSN name is correct. If necessary, create the appropriate DSN using the Nucleus ODBC Data Source Wizard or the Windows Data Source Administrator control panel applet prior to attempting the load operation. Consult the Nucleus ODBC Configuration Guide for information about defining an ODBC data source.

NDLERROR 0103. Unable to locate 'user-library-name' file.
Returned when a user-defined library file could not be located in the path specified in the LIBRARY section of an NDL script. Ensure that the user library path is correct before attempting the load operation again.

NDLERROR 0104. User library is referencing the built-in function 'function-name'.
Returned when a user-defined function declared in a LIBRARY section has the same name as a built-in NDL++ function. NDL++ does not permit function "overloading". Each function name, whether user-defined or built-in, must be unique within an NDL script.

NDLERROR 0105. User function 'function-name' already defined.
Returned when the same user-defined function name is declared more than once in an NDL script. NDL++ does not permit function "overloading". Each user-defined function name must be unique within an NDL script, even if functions with the same name belong to different libraries.

NDLERROR 0112. Unable to find user function 'function-name'.
Returned when a user-defined function is declared in an NDL script, but the function does not exist in the specified library file. Ensure that the library file includes the specified function, and that the correct function name is provided for its declaration in the NDL script.

NDLERROR 0113. Invalid number of arguments in definition of the user function 'function-name' (must be > 0 and <= 10).
Returned when a user-defined function requires 11 or more arguments. NDL++ imposes a limit of 10 arguments for all functions. In order to be used in an NDL script, this user function must be redefined with fewer arguments.

NDLERROR 0114. Too many user functions (must be <= 1024).
Returned when an NDL script contains more than 1024 user function definitions. Before attempting the load operation again, remove any unnecessary function definitions, or functions that can be easily substituted for by built-in NDL++ functions, so that the number of function definitions in the script is less than or equal to 1024.

NDLERROR 0115. PICTURE has been defined more then once on field 'field-name'.
Returned when the PIC keyword appears more than once in relation to the same field. A field can have at most one PIC clause associated with it.

NDLERROR 0116. NULLIF has been defined more then once on field 'field-name'.
Returned when the NULLIF keyword appears more than once in relation to the same field. A field can have at most one NULLIF clause associated with it.

NDLERROR 0117. MISSINGIF has been defined more then once on field 'field-name'.
Returned when the MISSINGIF keyword appears more than once in relation to the same field. A field can have at most one MISSINGIF clause associated with it.

NDLERROR 0118. User library 'user-library-name' has been already initialized.
Returned when a particular user-defined library is referenced in multiple initialization statements in the INIT section of an NDL script. The library may be initialized only once. Remove any redundant initialization statements from the NDL script before attempting the load operation again.

NDLERROR 0119. User library 'user-library-name' is referenced but not defined.
Returned when the INIT section of an NDL script contains an initialization statement for a user library that does not have a corresponding LIBRARY section. Ensure that a valid LIBRARY section exists for the user library before attempting the load operation again.

NDLERROR 0120. Duplicate lookup name 'lookup-instance'.
Returned when the INIT section of an NDL script contains two or more LOOKUP instances with the same name. Each LOOKUP instance must have a unique name.

NDLERROR 0121. Unknown lookup name 'lookup-instance'.
Returned when a LOOKUP call references a lookup instance that was never initialized in the INIT section. Ensure that the referenced lookup name matches one in the INIT section.

NDLERROR 0122. Duplicate attribute column 'column-name' for lookup 'lookup-instance'.
Returned when the same attribute name appears more than once in a LOOKUP instance attribute list in the INIT section of an NDL file. A specific attribute name may be included only once in a LOOKUP instance attribute list.

NDLERROR 0123. Unknown attribute column 'column-name' for lookup 'lookup-instance'.
Returned when the second argument in a LOOKUP call is not listed among the attribute fields in the initialization of the lookup instance. Ensure that the attribute argument in the LOOKUP call matches one of the attributes declared for the lookup instance.

NDLERROR 0124. Duplicate key column 'column-name' for lookup 'lookup-instance'.
Returned when the same key name appears more than once in a LOOKUP instance key list in the INIT section of an NDL file. A specific key name may be included only once in a LOOKUP instance key list.

NDLERROR 0125. Unknown key column 'column-name' for lookup 'lookup-instance'.
Returned when one of the key fields in a LOOKUP call does not match any of the key fields declared in the initialization of the lookup instance. Ensure that there is correspondence among the key fields in the LOOKUP call and the key field list in the lookup initialization.

NDLERROR 0126. Lookup name must be a character constant.
Returned when a LOOKUP instance name in the INIT section of an NDL file is not a character constant value. Ensure that the LOOKUP instance name is contained in quotation marks ('lookup-name').

NDLERROR 0127. Lookup attribute must be a character constant.
Returned when a LOOKUP attribute name in the INIT section of an NDL file is not a character constant value. Ensure that each name in the LOOKUP attribute list is contained in quotation marks ('attribute-name').

NDLERROR 0128. Lookup key must be a character constant.
Returned when a LOOKUP key name in the INIT section of an NDL file is not a character constant value. Ensure that each name in the LOOKUP key list is contained in quotation marks ('key-name').

NDLERROR 0129. Too many data files found (must be <= 16384).
Returned when the number of data files referenced in an NDL script exceeds 16,384. The SAND CDBMS Data Loader imposes a limit of 16,384 on the number of files it can process in a single load operation. Note that this error will be returned whether the excessive number of data file references is explicit (that is, 16,385 or more individual @data-file references) or implicit (through the use of wildcards, such as, @*.dat).

If there are more than 16,384 data files, combine some of them in order to reduce their number if possible. Otherwise split the NDL script into multiple scripts, so as to distribute a smaller number of data file references per script.

NDLERROR 0130. No data files found. Nothing to load.
Returned when the specification file references a data file that does not exist. Ensure that the correct data file is being referenced, and that it exists in the specified directory. (Note that if no file path is given, the current directory is searched.) If wildcards are used, make certain that at least one file matches the file name mask.

NDLERROR 0131. Missing column specification.
Returned when a load specification script does not define any columns into which to load. At least one column must be defined for the load operation.

NDLERROR 0132. Lookup name too long.
Returned when the length of a LOOKUP instance name is 256 or more characters. The maximum length of a LOOKUP name is 255 characters.