|
Problem IC95327
|
Status: Closed |
ON WINDOWS IMPORT UTILITY MIGHT FAIL WITH ERROR SQL0604N WHEN DB2_COMPATIBILITY_VECTOR=ORA IS SET. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
IMPORT fails with following error:
----
SQL3109N The utility is beginning to load data from file
"data.del".
SQL3037N An SQL error "-604" occurred during Import processing.
SQL0604N The length, precision, or scale attribute for column,
distinct type,
structured type, array type, attribute of structured type,
routine, cast
target type, type mapping, or global variable "CHAR()" is not
valid.
SQLSTATE=42611
SQL3110N The utility has completed processing. "0" rows were
read from the
input file
---- |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Windows users with DB2 setting: *
* DB2_COMPATIBILITY_VECTOR=ORA *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB Version 10.5 Fix Pack 3 *
**************************************************************** |
| Local Fix: |
Set input file encoding to unicode with global registry variable
DB2CODEPAGE :
db2set DB2CODEPAGE=1208 |
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in DB2 UDB Version 10.5 Fix Pack 3 |
| Workaround |
Set input file encoding to unicode with global registry variable
DB2CODEPAGE :
db2set DB2CODEPAGE=1208
and terminating existing connections with:
db2 terminate
Client application encoding will be set to 1208 (UTF) |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2013
27.02.2014
27.02.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
