There can be several types of unload and reload command
errors.
- Symptoms
- If an error occurs when unload or reload commands are
deployed, the SQL code is always -22220. This code means that the IBM® Data
Server Client has encountered an error in the script. The exact reason
for the error is specified by the error code. The error codes will
appear in the data output view. The detailed description for a particular
error code can be found in the DB2® Message
Reference manual.
- Resolving the problem
Reload command errors- Error code 3088
- The source column that was specified to be loaded into the database
column name is not compatible with the database column, but the database
column is not nullable.
Source table tblA: col1 int, col2 int, col3 varchar(5), col4
num(6, 2)
Target table (table being loaded) tblB: col2 int, col3 varchar(5),
col4 num(6, 2) not null.
If you selected all the rows
during the unload, then, due to a data type mismatch, the VARCHAR
values will fail to be inserted into col4 of the target table during
the reload. Fix this problem in one following ways:
- Edit the data file.
- Use the Customize Data Preservation wizard to select
the last three columns from tblA, in the unload statement. Use the
wizard to add column functions as needed.
- Error code 3124
- The field value in row "2" and column "3" cannot be converted
to a PACKED DECIMAL value, but the target column is not nullable.
The row was not loaded.
- Error code 3196
- The input file was not found. If the data file is located on a
remote machine where the unload command was run, then you must issue
the reload command again from the Data Project Explorer. Ensure that
the data file has been transferred to the machine where the reload
command is run, then select the reload command file, for example xxx_import.chx,
from the Data Project Explorer, right-click and select Run
SQL to complete the reload.
unload command errors- Error code 3025
- A parameter that specifies a file name or path is not valid. Because
the reload and unload commands are most likely run on remote systems, IBM Data
Studio does
not verify that the specified path exists. To avoid data loss, ensure
that the path is valid. You can also run the unload commands from
the project explorer before you deploy the scripts.
- Error code 3304
- The table does not exist. The unload commands must be issued before
the tables are dropped. The order of the commands needs to be verified
in the Commands section the Change Management Script Editor before
deploying the scripts. The default data file type is DEL (Delimited
ASCII, for exchange with many database managers and file managers).
You can change the file type to IXF if necessary.
If the error code is not in the data output
view, you can find the code in the Administration notification log
file (db2dasdiag.log). For more information, such as the location
of this file, see DB2 Information Center.