|
Problem IC80300
|
Status: Closed |
"EXPORT COMMAND FAILS ON LINUX WITH -3009 ERROR WHEN THE SELECT STATEMENT IS 64K OR GREATER IN SIZE" |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
On linux, when the select clause in import command exceeds 64k
or more, the command may fail with -3009 error.
For example:
When the below test script is executed:
db2 "create db xmldb using CODESET utf-8 TERRITORY us"
db2 connect to xmldb
db2 "CREATE TABLE longstmtsel( column000000000001
VARCHAR(25),column000000000002 VARCHAR(25) )"
db2 "INSERT INTO longstmtsel VALUES('select', 'select
validated')"
db2 -tvf test.clp
cat test.clp:
UPDATE COMMAND OPTIONS USING s OFF;
UPDATE COMMAND OPTIONS USING c OFF;
UPDATE DB CFG FOR XMLDB USING APPLHEAPSZ 1000 STMTHEAP 524288;
!db2 -tvf 64kexport.clp;
Export may return the error:
SQL3009N The Action String parameter is not valid or too long.
File 64kexport.clp contains an import command with select clause
exceeding 64k in size. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* clp users *
****************************************************************
* PROBLEM DESCRIPTION: *
* export command fails on linux when the select stmt exceeds *
* 64K *
****************************************************************
* RECOMMENDATION: *
* upgrade to v97fp6 or later *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
problem fixed |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.12.2011
08.12.2011
08.12.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
