home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC98623 Status: Geschlossen

IMPORT MIGHT HIT SQL0304N ERROR AND REJECT ROWS CONTAINING TIMESTAMP DATA
IF TIMESTAMPFORMAT IS SPECIFIED FOR ASC/DEL FILE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
Lösung
The problem is firstly fixed on V9.7FP10.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC99917 IC99920 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.01.2014
10.11.2014
10.11.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP10
Problem behoben lt. FixList in der Version
9.7.0.10 FixList