Running db2move with export against a DB2 z/OS database gives
error. For example:
db2move <dbname> export -tc <definer> -tn <tablename> -u
'<userid>' -p
'<password>'
Message in the file db2diag.log:
2013-10-07-10.31.30.325675-300 I3439124E728 LEVEL:
Error
(Origin)
PID : 18297 TID : 140737278388000 PROC :
db2move
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPID : XXXXXXXX.XXXX.XXXXXXXXXXXX
HOSTNAME: xxxxxxxxx.xxxxxxxxx.xxx
FUNCTION: DB2 UDB, database utilities, sqlueAllocAndDescSqlda,
probe:3863
MESSAGE : SQL3022N An SQL error "" occurred while processing
the
SELECT string
in the Action String parameter.
DATA #1 : String, 28 bytes
Export SQL failed processing
DATA #2 : Hexdump, 32 bytes
0x00007FFFEB614D44 : 5345 4C45 4354 202A 2046 524F 4D20 2258
SELECT
* FROM "X
0x00007FFFEB614D54 : 5858 2200 5858 5858 5858 5858 5858 5858
XX"."XXXXXXXXX".
2013-10-07-10.41.28.818258-300 I3439853E571 LEVEL:
Error
PID : 18899 TID : 140737278388000 PROC :
db2move
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPID : O6DFE162.DB4F.131007154126
HOSTNAME: xxxxxxxxxx.xxxxxxxxx.xxx
FUNCTION: DB2 UDB, database utilities, sqluCheckSqlca, probe:298
MESSAGE : SQL0104N An unexpected token "" was found following
"".
Expected
tokens may include: "".
DATA #1 : String, 17 bytes
sqluiDescribe.SQC
DATA #2 : String, 44 bytes
Error from Import/Export or Load Processing.
Message generated into EXPORT.out:
Connecting to database SAMPLE ... successful! Server : DB2 for
MVS V8.1.5
*** Table "XXX "."XXXXXXXXX": ERROR -3022. Check message
file tab1.msg!
*** SQLCODE: -3022 - SQLSTATE:
*** SQL3022N An SQL error "-104" occurred while processing the
SELECT string in the Action String parameter.
**Error occured -1
Message in file .msg for the corresponding table:
SQL3022N An SQL error "-104" occurred while processing the
SELECT string in
the Action String parameter.
SQL0104N An unexpected token " " was found following "".
Expected tokens may
include: "FOR WITH FETCH ORDER UNION EXCEPT QUERYNO OPTIMIZE".
SQLSTATE=42601
The error occurs because db2move mistakenly passed an extra NULL
byte 00 to the DB2 export utility. We can see it in the trace
file:
SQLSTT OBJDSS (ASCII)
(EBCDIC)
0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF
0123456789ABCDEF
0000 0035D0030001002F 2414000000002553 .5...../$.....%S
..}.............
0010 454C454354202A20 46524F4D20225858 ELECT * FROM "XX
.<........!(....
0020 582020202020222E 2258585858585858 X "."XXXXXXX
............<...
0030 58582200FF XX"..
.....
This just cause issue for DB2 z/OS database. (Running a db2move
export on DB2 LUW server, there is the extra 00 in the trace,
but db2move completes successfully. It seems that DB2 LUW
server can tolerate the extra 00.) |
