DB2 - Problem description
Problem IC98623 | Status: Closed |
IMPORT MIGHT HIT SQL0304N ERROR AND REJECT ROWS CONTAINING TIMESTAMP DATA IF TIMESTAMPFORMAT IS SPECIFIED FOR ASC/DEL FILE | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
With V9.7 client, when importing data to a table with TIMESTAMP column(s) in V9.5 or earlier database, if the timestampformat file type modifier is specified for ASC/DEL file, IMPORT might hit SQL0304N error when attempting to import rows containing TIMESTAMP data, and then reject the rows. You can see the following messages when the issue occurs: SQL3148W A row from the input file was not inserted into the table. SQLCODE "-304" was returned. SQL0304N A value cannot be assigned to a host variable because the value is not within the range of the host variable's data type. SQLSTATE=22003 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Using V9.7 or higher client import ASC/DEL file into V9.5 or * * lower database. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 for LUW V9.7FP10. * **************************************************************** | |
Local Fix: | |
Try to remove the timestampformat file type modifier from the IMPORT command and import again when TIMESTAMP data is well formatted in the ASC/DEL file. | |
Solution | |
The problem is firstly fixed on V9.7FP10. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC99917 IC99920 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.01.2014 10.11.2014 10.11.2014 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP10 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.10 |