Explanation

The RESTORE utility either could not read data from the restored database or only a portion of the database was restored. Both cases indicate that the restored database is not usable.

The database is unusable and the RESTORE utility stops processing.

Explanation

An operating system error occurred when the RESTORE utility was reading the diskette or disk, or the diskette or disk does not contain a backup of the database directory or does not contain the results of any previous backup.

The utility stops processing.

Explanation

The name of the database contained on the backup disk does not match the database name specified on the RESTORE command. The RESTORE utility cannot determine the name until after the database has been restored because a previous release backup image was restored.

The utility stops processing.

Explanation

The RESTORE utility reads the first backup diskette to determine the path of the database directory that was backed up. If the backup media is a diskette and the diskette is not found in the specified input drive, the utility returns to the caller with this prompt. The calling program is expected to query the user and return to the utility with the user response.

The utility waits for a response from the caller.

Explanation

If the database being restored already exists, its files will be deleted before the restore process starts. The utility returns to the caller with this warning. The caller is expected to query the user and return to the utility with the user response. Once the database is dropped, it cannot be accessed again.

The utility waits for response from the caller.

Explanation

If changes-only backups were performed and database files were deleted between backups, the RESTORE utility adds these deleted files back into the database. The restore process could not delete the extra files either because of an I/O error or by the failure of an internal connection to an internally stopped database.

The utility ends successfully.

Explanation

Because the RESTORE utility was not bound to the database or the package of the utility that was bound to the database is not compatible with the installed version of DB2, all the utilities have been rebound to the database. But there is a timestamp conflict between the installed version of the database product and the package so the utility and bind file are not compatible.

The database is restored, but the utility is not correctly bound.

Explanation

The timestamp parameter must contain either NULL or a portion of a valid timestamp, the portion consisting of complete components of a timestamp.

Explanation

The drive specified does not exist, or the database does not exist on this drive or is not cataloged on this drive. RESTORE should use the db2uexit command to perform the database restore.

The utility stops processing.

Explanation

An error occurred in the wait or post semaphore.

The utility stops processing.

Explanation

The utility could not drop the database.

The utility stops processing.

Explanation

The utility could not create the database.

The utility stops processing.

Explanation

The utility could not rename the database.

The utility stops processing.

Explanation

The release number of the restored database is not compatible with the release number of the installed version of the database manager.

The utility stops processing.

Explanation

The user attempted to execute the RESTORE DATABASE utility without SYSADM authority.

The utility stops processing.

Explanation

In some situations, the RESTORE utility can attempt to move a database to a directory by renaming the directory associated with the database. This cannot be done if any databases are in use in any process on the workstation.

The utility stops processing.

Explanation

You can upgrade a database from one version to a newer version using the restore utility. You can upgrade by recreating your old database manager instance in the new version and then restoring a backup image from the the old instance into the new instance. In this scenario, after restoring the database in the new database instance, the restore utility automatically performs the upgrade operation. This message is returned when the upgrade operation that the restore utility automatically runs returns a warning or error.

Explanation

The database configuration file could not be restored due to an I/O error.

The utility stops processing.

Explanation

The database backup that you restored is from a previous database product release. After the database files were restored, an attempt was made to upgrade the database to the current release. The database upgrade failed.

The database restore was completed but the database was not upgraded.

Explanation

When a database is restored, the current database configuration file is not always replaced with the backup version. The current database configuration file was not usable. It has been replaced by the backup version.

The utility completed successfully.

Explanation

The restore process ran successfully. The specified file was not deleted due to an I/O error.

A file with the extension “.BRG” is used to determine whether a RESTORE operation has terminated abnormally. The file resides in the local database directory of the database for which the RESTORE operation was attempted.

A file with the extension “.BRI” stores information about the progress of an incremental RESTORE operation. The file resides in the local database directory of the database for which the RESTORE INCREMENTAL operation was attempted.

The file name consists of the database token concatenated with the file type extension. For example, if the database “SAMPLE” is assigned the database token “SQL00001”, the BRI file will have the name “instance/NODE0000/sqldbdir/SQL00001.BRI”.

The utility completed successfully.

Explanation

The backup image file file name consists of a database alias and a time stamp component. A file name is constructed from the source database alias and time stamp parameters provided in the Database Restore call. A portion of a time stamp may have been specified so that a match with more than one backup image file name was found. If no time stamp was provided restore implicitly matches any backup image; implying if there are more than one backup images a unique match cannot be made.

Explanation

The database alias and name of the target database are the same as the backup image database alias and name. The database seeds are not the same indicating that the databases are not the same. The target database will be overwritten by the backup version. The Roll-forward recovery logs associated with the target database will be deleted. The current configuration file will be overwritten with the backup version.

Explanation

The database seeds of the target database and the database image are the same, indicating these are the same databases, the database names are the same, but the database aliases are not the same. The target database will be overwritten by the backup version.

Explanation

The database aliases of the target database and database image are not the same, the database names are the same, and the database seeds are not the same, indicating these are different databases. The target database will be overwritten by the backup version. The Roll-forward recovery logs associated with the target database will be deleted. The current configuration file will be overwritten with the backup version.

Explanation

The database aliases of the target database and database image are the same, and the database seeds are the same, however the database names are different. These are the same databases. The target database will be overwritten by the backup version.

Explanation

The database aliases of the target database and database image are the same, the database names are not the same, and the database seeds are not the same, indicating these are different databases. The target database will be overwritten by the backup version. The Roll-forward recovery logs associated with the target database will be deleted. The current configuration file will be overwritten with the backup version.

Explanation

The database aliases of the target database and database image are not the same, the database names are not the same, and the database seeds are the same, indicating these are the same databases. The current database will be overwritten by the backup version.

Explanation

The database aliases of the target and database image are not the same, the database names are not the same, and the database seeds are not the same, indicating these are different databases. The current database will be overwritten by the backup version. The Roll-forward recovery logs associated with the target database will be deleted. The current configuration file will be overwritten with the backup version.

Explanation

The backup image being restored is corrupted making the database image non-restorable.

Explanation

The file selected for restore is not a valid backup image. Either the file selected has become corrupted or a backup tape is not at the correct position.

Explanation

The file selected for restore does not contain the requested backup image. The image is for a different database than that requested.

Explanation

The backup image read from the tape position contains a media header that does not match the header of the image of the first file of the backup file sequence.

Explanation

The data read from the tape position does not contain a valid backup media header.

Explanation

The end of tape has been reached and there is still more data to be processed. The remainder of the backup or load source exists on another tape or on several more tapes.

Explanation

The tape is positioned on a backup image file that is out of sequence. The tape containing the backup image must be positioned to the file of sequence number sequence of the backup image.

Explanation

SQLUD_NOROLLFWD was specified for the rst_type parameter of the Database Restore utility, indicating that a roll-forward is not required to make the restored database usable. If the database to be restored was backed up in online mode or the restore issued was a tablespace level restore, then a roll-forward operation is necessary to make the database usable.

Explanation

While reading and restoring from the Backup Image file, an end of file condition was reached unexpectedly. The backup image is unusable and the restore operation terminates.

Explanation

This message is returned when the database aliases, names and seeds of the target database and database image are the same, indicating these are the same databases. The current database will be overwritten by the backup version.

This message can also be returned when the RESTORE command is called with the GENERATE SCRIPT parameter. When the RESTORE command is used to generate a restore script, the restore utility performs some of the same error checking that is performed when a restore operation is being performed. When this message is returned when the RESTORE command is called with the GENERATE SCRIPT parameter, the message can be ignored.

Explanation

The Database Restore utility was invoked in No Interrupt mode, i.e. WITHOUT PROMPTING. During the processing, one or more warnings were encountered but not returned at the time they were encountered. The Restore has completed successfully and the warning messages found are shown at the completion in this message.

Explanation

The utility was successful, but the file containing the backup image could not be closed.

Explanation

The backup image file filename consists of a database alias and a timestamp component. A filename is constructed from the source database alias and timestamp parameters provided in the Database Restore call. No filename existed in the source directory that matched based on the source database alias and timestamp provided.

The following situations might apply:

1. The path to the backup was incorrectly specified in the restore command.
2. You do not have permission to access the backup image or the directory within which the backup image resides.
3. You are performing an automatic incremental restore and a required image was not found based on the timestamp and location in the database history.
4. You are restoring a database in a partitioned database environment, the database does not already exist, and the first database partition being restored is not the catalog partition.
5. You are restoring from TSM media, and the TSM API client configuration used by the current instance is not able to access the backup image.

Explanation

The application calling the Restore utility has supplied a target directory for the new database to be created. Either this directory does not exist, or is not a valid directory for database creation. An invalid directory for database creation would be a directory of greater than 215 characters in length.

Explanation

While the database was being restored the directory to which it was being restored had become full. The database being restored is unusable. The Restore terminates and if the database being restored is a new database, then it is deleted.

Explanation

The backup image is not immediately accessible by the TSM server. The restore process can continue and make the request to the server to retrieve the data. The time required is unknown.

Explanation

During restore or load recovery, the first image from the backup or copy must be processed first. The image found on the media is not the first in sequence.

The utility waits for a response to continue.

Explanation

The physical log file formats have changed between these releases, making rollforward impossible.

Explanation

Explanation

The containers which were used by the table spaces in the backup image are not available, are already in use, or one or more table space names specified in the list on the restore command do not exist in the backup image.

Explanation

The backup image used for the restore is a backup of a database from a different node. You can only restore a backup to the same node.

Explanation

In an environment that is not a DB2 pureScale environment, the catalog node can exist on only one node. This message is returned when there is a discrepancy between the backup image and the node being restored to. This can occur in the following cases:

1. The backup image specified catalog node node1 and the restore was attempted to an existing database whose catalog node is node node2
2. The restore was attempted to a new database and the catalog node has not been restored first.

Explanation

The length of the report file name exceeded the allowed limit of 255.

Explanation

The utility completed successfully.

Explanation

Explanation

The backup that you used to restore the database is from a previous DB2 release. After you restored the database, it was upgraded to the DB2 release where you issued the RESTORE DATABASE command.

The user who issued the RESTORE DATABASE command is given DBADM authority to the database. If other users had DBADM authority prior to restore, the security administrator, who has SECADM authority, must grant DBADM authorization to these users.

The RESTORE DATABASE command was completed successfully. The UPGRADE DATABASE command issued automatically after the database restore was also completed successfully.

Explanation

A RESTORE DATABASE command was issued with the optional LOGTARGET path specified but the backup image did not contain all of the logs required for a successful rollforward recovery.

Explanation

You can restore a database or restore one or more table spaces in a database from a backup image into a target database using the RESTORE DATABASE command or the db2Restore API.

There are some conditions that must be met to run a restore operation from a table space level backup. For example, the target database that is specified for the restore operation must meet one of the following conditions:

• The specified target database is the original database from which the backup image was taken.
• The specified target database. does not exist, and the rebuild option is specified in the restore command or API call.

This message is returned when an attempt is made to perform a database restore operation or a table space-level restore operation to a target database that is neither the original database from which the backup image was created nor a newly-created database.

Explanation

The RESTORE utility was issued with the REBUILD option and either specified a table space image to restore or specified a list of table spaces to restore from a backup image. If the database does not already exist, it will be created using the table spaces available for restore and the same database attributes as those in the image. If the database already exists, the database will be overwritten using the table spaces available for restore and based on the sqlcode returned with this warning.

If a subset of table spaces is restored from a non-recoverable database, the table spaces that were not part of the restore can never be recovered unless you do a complete database restore.

Explanation

This message can be returned for different reasons, including the following examples:

• An error was encountered while accessing the containers of the table spaces.
• The restore command was invoked with a list of table spaces so that only a subset of the table spaces in the backup were restored.
• An attempt was made to restore table spaces that have file system caching enabled into containers on disks that do not support file system caching.

Explanation

The database contained in the backup image is an existing database and does not match the database to be restored. The option you have specified for restore requires that the database being restored to is new or the same as in the backup image.

The utility stops processing.

Explanation

One or more table spaces have tables in DATALINK Reconcile Pending (DRP) or DATALINK Reconcile Not Possible (DRNP) because of one of the following reasons:

• Restoring to a database that has a different database name, alias, hostname, or instance than the backup image. If no rollforward follows the restore, any tables with DATALINK columns are placed in DRNP state.
• Restore is done specifying the WITHOUT DATALINK option and no rollforward follows the restore. Any tables with DATALINK columns are placed in DRP state.
• Restoring from a backup image that has become unusable. If no rollforward follows the restore, any tables with DATALINK columns are placed in DRNP state.
• DATALINK column information does not exist at the DB2 Data Links Manager(s). Affected tables are placed in DRNP state.
• Restore involving fast reconciliation failed while trying to relink files at the DB2 Data Links Manager(s). Affected tables are placed in DRNP state.

Explanation

Possible reason codes are:

1

target-OS and source-OS are not compatible systems.

2

A cross-platform restore of a compressed backup was attempted and no decompression library was specified. By default the library in the backup image from source-OS is used. This library is not suitable for a restore on target-OS.

3

A compression library-only restore was attempted on target-OS, a different operating system from the one on which the backup was taken (source-OS).

Explanation

An error was encountered during the automatic restore process. This error occurred during an incremental restore or during a rebuild of a database from table space images or from a subset of table spaces in a database image. The utility was unable to complete as intended. The utility stops processing.

In the case of an incremental restore, this error is returned after the initial definitions have been restored and the processing of the required incremental restore set cannot be completed successfully.

In the case of a rebuild, this error is returned after the initial target image has been restored and the processing of the remaining required restore set cannot be completed successfully.

The error is a result of one of the following reason codes:

1

The backup image corresponding to the specified timestamp could not be found in the database history.

2

An error occurred trying to determine which table spaces to restore.

3

A required backup image could not be found in the database history.

4

The wrong rebuild type was specified for the incremental rebuild intended.

5

Cannot automatically restore only temporary table spaces.

Explanation

Each tablespace in the backup image is aware of the backup image that must be restored before the backup image that failed can be successfully restored. You must restore the image with the timestamp reported in this message before you can successfully restore the image that invoked this message. There might be additional images to restore before the indicated image, but this was the first tablespace to encounter an error.

Explanation

A RESTORE operation was attempted using an incremental backup image. An incremental backup cannot be restored on its own; it can be restored only as part of an incremental RESTORE operation.

The utility stops processing.

Explanation

The target image is the first image to be restored as part of an incremental RESTORE operation. This image contains the tablespace definitions and other control structures for the database that is being restored. The RESTORE utility cannot restore an image that is newer than the target image during an incremental RESTORE operation, because it could corrupt the database.

The incremental RESTORE operation failed because it attempted to restore a backup image with a timestamp that is more recent than the timestamp of the target image.

The utility stops processing.

Explanation

To perform an incremental RESTORE operation, the backup images must be restored in chronological order of oldest to newest for each tablespace. An incremental RESTORE operation specified a backup image with a timestamp older than the timestamp of the previous image that was restored for the specified tablespace.

The utility stops processing.

Explanation

To perform a manual, cumulative restore operation you must issue the RESTORE command, specifying the INCREMENTAL clause, for each image involved in the restore operation.

This message is returned when the RESTORE command is issued without the INCREMENTAL clause, but the utility detects that a previous incremental restore operation has not completed.

Explanation

The image being restored is a compressed backup, but no decompression library was specified and no library was found in the image.

The RESTORE utility requires a plug-in library to decompress the backup. This library is typically stored in the backup image itself, but in this case the creator of the backup chose to exclude the library. The library name can also be specified as a parameter to the RESTORE utility.

The utility stops processing.

Explanation

The specific object that was asked to be restored does not exist in the backup image.

The RESTORE utility attempted to restore a single object from the backup image. No object of this type exists in the backup image.

The backup history file and the decompression library are the objects that can be restored individually.

The utility stops processing.

Explanation

The specified log target path contains at least one file with a name which matches the log filename format. If the restore operation later attempts to extract a log file of the same name, this will cause the restore to fail.

Explanation

An error occurred while attempting to extract a log file from the backup image. This could be because one of the following reasons:

1

The backup image does not include logs.

2

The log target path specified could be full or invalid.

3

A log file name in the backup image matches a log file which already exists in the log target path.

4

There was an I/O error while trying to write the file.

5

The primary log directory on disk contains log files that will be destroyed by restore.

6

The mirror log directory on disk contains log files that will be destroyed by restore.

7

The default log directory of the existing database has logs that will be destroyed by the restore.

Explanation

The RESTORE utility was issued with the REBUILD option but it has detected that a rebuild of the database is already in progress. If this operation were to take place then it would abort the current rebuild in progress and start a new one using this backup image as the target. The database will be overwritten.

Subsequent restore commands during the rebuild phase of the database should not be issued with the REBUILD option.

Explanation

The RESTORE utility has detected that a previous incremental restore operation has not completed. The intended restore command is not part of the previous incremental restore and cannot be processed unless the previous incremental restore is aborted.

The utility stops processing.

Explanation

Snapshot backup enables you to use fast copying technologies for the data copying and movement parts of DB2 database backup and restore operations.

The snapshot backup image must be restored as a whole. For this reason, when there are database logs in the snapshot backup image, they must be restored with the rest of the image.

There are database logs in the snapshot backup image you are restoring, so they must be restored with the rest of the image. However, the path for the given log directory shares a path or storage device with other paths or storage devices used by the database being restored.

It is not unusual for the path of the log directory to share a path or storage device with other database paths or storage devices. For example: when you create a database, the log directory is created under the main database directory by default. When a log path shares a path or storage device with other database paths or storage devices, a snapshot restore can not restore the log directory unless you specify the target location for the log directory using the LOGTARGET parameter.

The snaphot restore failed because you did not specify a LOGTARGET, or because you specified an invalid LOGTARGET.

Explanation

The backup image selected for restore is from an instance that does not match the current instance.

Snapshot backup images can only be restored to the same instance name they were taken from.

Explanation

An error occurred while using the RESTORE DATABASE command with the TRANSPORT option to transport table spaces and schemas from a database backup image to a target database. The following reason code indicates the error:

1

The list of table spaces and schemas being transported is not a valid transportable set.

2

The table spaces and schemas being transported contain tables with columns that are of a data type that is not supported with schema transport.

3

Table spaces or schemas already exists on the target database.

4

The list of table spaces and schemas being transported contains system catalogs. The system catalogs can not be transported.

5

All default staging databases are already in use.

6

Rollforward requires user interaction to resolve load copy recovery.

7

The backup image must contain the SYSCATSPACE table space.

8

Transport is not supported in partitioned database environments or in DB2 pureScale environments.

9

Transport is not supported when the source instance is an ESE instance and the target instance is a DB2 pureScale instance.

10

Attempting to increase LSN on target database failed.

12

Table space ID for schema transport cannot be reserved because another session of transport is already in progress.

13

Storage paths are dropped as table spaces are being reserved for schema transport.

14

A warning occurred when creating the staging database.

15

An error occurred on target database while transporting table spaces.

16

An error occurred on staging database while transporting table spaces.

17

Schema transport stopped because table space ID mapping is not resolved or validated. An error occurred in one of the following situations:

• Mapping table space IDs between the staging database and the target database.
• Validating table space IDs provided by the client against the server memory.
• The mapped table space is not valid.

18

Reason code 18 can be returned for two reasons:

• An attempt was made to perform a schema transport operation into a database that is configured to disallow non-logged operations.
• An attempt was made to specify the TRANSPORT INTO clause with the RESTORE command when restoring to a target database that is encrypted with DB2 native encryption.

19

Not all DDL objects in the transportable set can be created on the target database.

20

The specified backup image was created using an online backup operation, and the LOGTARGET parameter was not specified with the RESTORE command.

21

The table spaces and schemas being transported contain partitioned tables, which are not supported with schema transport.

Explanation

The pointer to the authorization structure parameter is NULL, the pointer to the authorization structure points to an area that is smaller than the length indicated in the structure length field, or the authorization structure length field is not set to the correct value.

The command cannot be processed.

Explanation

An invalid parameter was passed to a read log API. The possible reason codes are as follows:

01

Invalid action specified.

02

The starting log record identifier is greater than the current database active log record identifier.

03

The log record identifier range bounded by the starting and ending log record identifiers is not large enough to span a log record.

04

The starting log record identifier does not represent the start of an actual log record.

05

The starting log record identifier's location could not be determined.

06

The ending log record identifier is less than or equal to the starting log record identifier.

07

The buffer is not valid for the indicated size.

08

The buffer is not of sufficient size to store a log record.

09

A pointer is not valid.

10

The filter option is not valid.

11

The logfile path is not valid.

12

The overflow logfile path is not valid.

13

The retrieve logs option is not valid.

14

The specified number of bytes for memory allocation is too small.

15

The log sequence number is larger than can be contained by its respective API field.

16

The log record identifier type for piStartLRI is invalid.

17

The log record identifier types for piStartLRI and piEndLRI are not the same.

Explanation

The asynchronous read log API was used against a connected database which does not have LOG RETAIN or USER EXITS ON. Only databases which are forward recoverable may have their associated logs read.

Explanation

The allocation of internal structures and buffers that are used by the db2ReadLog or db2ReadLogNoConn API has failed.

Explanation

A Restore, Rollforward or Crash Recovery might have reused log sequence number ranges. The possible reason codes are as follows:

1

Restore has taken place.

2

Rollforward has taken place.

3

Crash Recovery has taken place.

Explanation

All log records in the database active log have been read by the asynchronous log reader.

Explanation

The Asynchronous Log Reader attempted to read log records from the specified log file. The specified log file is not associated with the database being asynchronously read.

Explanation

The Asynchronous Log Reader attempted to read log records from the specified log file. The specified log file has been corrupted and cannot be read.

Explanation

You can read log records from the DB2 database logs, or query the log manager for information about the current state of logs using the db2ReadLog API.

This message is returned when the db2ReadLog API is called, but the log reader cannot access log records from the indicated log file on the indicated log stream. One reason this can happen is because the log path was recently changed, using the newlogpath database configuration parameter, and the required log file is located in the old log path.

Explanation

Explanation

The utility cannot read the configuration file config-file.

Explanation

The utility cannot open the log file log-file for writing or appending.

Explanation

The utility cannot read the input data file input-data-file.

Explanation

The utility cannot read the input partitioning map file in-map-file.

Explanation

The utility cannot open the output partitioning map file out-map-file for writing.

Explanation

The utility cannot open the distribution file dist-file for writing.

Explanation

The utility cannot open the output data file out-data-file for writing.

Explanation

There is a syntax error in the specification of a keyword and its argument.

Explanation

There is an undefined keyword in the configuration file.

Explanation

The column delimiter (CDELIMITER) specified in the configuration file is not valid.

Explanation

The string delimiter (SDELIMITER) specified in the configuration file is not valid.

Explanation

The value for run type (RUNTYPE) specified in the configuration file is not valid.

Explanation

The value for message level (MSG_LEVEL) specified in the configuration file is not valid.

Explanation

The value for check level (CHECK_LEVEL) specified in the configuration file is not valid.

Explanation

The value for record length (RECLEN) reclen specified in the configuration file is not valid.

Explanation

The node specification (NODES) in the configuration file is not valid.

Explanation

The output node specification (OUTPUTNODES) in the configuration file is not valid.

Explanation

The output type (OUTPUTTYPE) in the configuration file is not valid.

Explanation

The number of partitioning keys defined cannot exceed the maximum limit: 256.

Explanation

 PARTITION=<key name>,
           <position>,
           <offset>,
           <len>,
           <nullable>,
           <datatype>

If a delimited-data file, <position> must be defined; otherwise, <offset> and <len> must be defined.

Explanation

The log file specification (LOGFILE) in the configuration file is not valid.

Explanation

The trace specification (TRACE) in the configuration file is not valid.

Explanation

The node list specification is not valid.

Explanation

If run type is ANALYZE, a filename for the output partition map must be defined.

Explanation

At least one partitioning key must be defined.

Explanation

For non-delimited data, starting position for a key must be less than the record length.

Explanation

Output node list must be a subset of the node list, which is derived from NODES or the input partition map file.

Explanation

There is at least one error in the partitioning map file.

The specific error is indicated by the reason code:

1

The partitioning map file cannot be read.

2

The number of values in the partitioning map file is not 1 or 32768.

3

The node number in the partitioning map file is not between 0 and 999.

4

The data in the partitioning map file is not in a valid format.

Explanation

An I/O error occurred while writing the header to an output data file.

Explanation

An I/O error occurred while reading from input data file.

Explanation

Binary data is not permitted on the host versions of this utility program.

Explanation

The run type (RUNTYPE) must be defined as either PARTITION or ANALYZE.

Explanation

The specification for parameter 32KLIMIT in the configuration file is not valid.

Explanation

The record rec-no of the input data is discarded because it contains nothing but spaces.

Explanation

Partitioning key fields contain invalid data.

Explanation

An I/O error occurred while writing a record to the output data file for node out-node.

Explanation

Expected writing length (RECLEN) does not match the actual writing length.

Explanation

If a binary numerical input data file, the record length has to be defined.

Explanation

Float data type is only supported when the file type is BIN (binary).

Explanation

The file type specification (FILETYPE) in the configuration file is not valid.

Explanation

In a binary input data file, the length of a partition key with decimal data type must conform to the equation: LENGTH=(PRECISION+2)/2 (integer division), because it is a packed decimal.

Explanation

In a binary input data file, the length of a partition key with integer, small integer, float, and double data type must be a predefined constant, i.e. 4 for integer, 2 for small integer, 4 for float, and 8 for double.

Explanation

The maximum length for a file name is 80 bytes.

Explanation

The NEWLINE flag must be either YES or NO, and if not given, it is NO.

Explanation

If a fixed-length positional ASC file or a binary numerical data file, each record has to be exactly the same length as the value of the RECLEN parameter in the configuration file.

Explanation

For a positional ASC input data file or a delimited data file with parameter 32KLIMIT on, the maximum record length can not exceed the 32k (bytes) limit.

Explanation

For a positional ASC input data file or a binary numerical data file, each record has to be long enough to hold all partitioning keys.

Explanation

If a record is greater than 32k bytes long in a delimited data file, all partitioning keys of each record have to be within the first 32k bytes of the record.