By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,564 Members | 1,081 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,564 IT Pros & Developers. It's quick & easy.

SQL3255 on DB2 v9.1 Win32 with db2move

P: n/a

Summary: SQL3255 Reason code 2 from db2move with DB2 v9.1 fixpack 5.
on Win32.

Win32 DB2 version 9.1 fixpack5 , performing DB2MOVE COPY with
SCHEMAMAP between two local databases in the same 32bit instance.

Problem: DB2MOVE COPY giving SQL3255N reason code 2 during the load
phase.

Command line: db2move sourcedb COPY -sn oldschema -co TARGET_DB newdb
USER userid USING password SCHEMA_MAP((oldschema,newschema))

Both sourcedb and target_db are in the same instance.
Sourcedb is a database that is restored+migrated from db2v8.
NEWDB is a freshly created db2v9 database, automatic storage yes ,
autoconfigure etc.

There are approximately 400 tables to copy, but around 60 tables get
the SQL3255N error, and the thing that seems to be in common
is that they all have a CLOB column.
The db2diag.log has these entries:
2008-10-22-15.24.24.171000+120 I2772940H360 LEVEL: Warning
PID : 9884 TID : 5632 PROC : db2syscs.exe
INSTANCE: ODS NODE : 000
APPHDL : 0-71
FUNCTION: DB2 UDB, database utilities, DIAG_NOTE, probe:0
DATA #1 : String, 75 bytes
LOADID: 3204.2008-10-22-15.24.23.921001.0 (2;5)
UserExitSA is running. 0, 0

2008-10-22-15.24.24.281000+120 I2773302H420 LEVEL: Warning
PID : 9884 TID : 7260 PROC : db2syscs.exe
INSTANCE: ODS NODE : 000
APPHDL : 0-71
FUNCTION: DB2 UDB, database utilities, sqlulPrintPhaseMsg, probe:311
DATA #1 : String, 125 bytes
LOADID: 3204.2008-10-22-15.24.23.921001.0 (2;5)
Starting LOAD phase at 10/22/2008 15:24:24.311698. Table
SNLODSADM.OPB_ATTR
2008-10-22-15.24.24.375000+120 I2773724H524 LEVEL: Error
PID : 9884 TID : 5632 PROC : db2syscs.exe
INSTANCE: ODS NODE : 000
APPHDL : 0-71
FUNCTION: DB2 UDB, database utilities, sqluffExecRecvReply, probe:1241
MESSAGE : ZRC=0x870F00A6=-2029059930=SQLO_NPIPE_BROKEN "Buffer too
small"
DATA #1 : LOADID, PD_TYPE_LOADID, 39 bytes
3204.2008-10-22-15.24.23.921001.0 (2;5)
DATA #2 : File name, 16 bytes
sqluueffServer.C
DATA #3 : String, 19 bytes
Error reading reply

2008-10-22-15.24.24.421000+120 I2774250H485 LEVEL: Error
PID : 9884 TID : 5632 PROC : db2syscs.exe
INSTANCE: ODS NODE : 000
APPHDL : 0-71
FUNCTION: DB2 UDB, database utilities, sqlusCUserExitSubAgent::iRun,
probe:1197
MESSAGE : ZRC=0x870F00A6=-2029059930=SQLO_NPIPE_BROKEN "Buffer too
small"
DATA #1 : LOADID, PD_TYPE_LOADID, 39 bytes
3204.2008-10-22-15.24.23.921001.0 (2;5)
DATA #2 : File name, 17 bytes
sqlusUserExitSA.C
2008-10-22-15.24.24.437000+120 E2774737H382 LEVEL: Error (OS)
PID : 9884 TID : 5632 PROC : db2syscs.exe
INSTANCE: ODS NODE : 000
APPHDL : 0-71
FUNCTION: DB2 UDB, oper system services, sqlowchd, probe:45
MESSAGE : ZRC=0x83000006=-2097151994
CALLED : OS, -, unspecified_system_function
OSERR : 6 "The handle is invalid."

2008-10-22-15.24.24.453000+120 I2775121H497 LEVEL: Error
PID : 9884 TID : 5632 PROC : db2syscs.exe
INSTANCE: ODS NODE : 000
APPHDL : 0-71
FUNCTION: DB2 UDB, database utilities, sqlusCUserExitSubAgent::iRun,
probe:1207
MESSAGE : ZRC=0x83000006=-2097151994
DATA #1 : LOADID, PD_TYPE_LOADID, 39 bytes
3204.2008-10-22-15.24.23.921001.0 (2;5)
DATA #2 : File name, 17 bytes
sqlusUserExitSA.C
DATA #3 : ZRC, PD_TYPE_ZRC, 4 bytes
0x870F00A6

2008-10-22-15.24.24.468000+120 I2775620H410 LEVEL: Error
PID : 9884 TID : 5632 PROC : db2syscs.exe
INSTANCE: ODS NODE : 000
APPHDL : 0-71
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 125 bytes
LOADID: 3204.2008-10-22-15.24.23.921001.0 (2;5)
UserExit Failure , 0, 00000000, Detected in file:sqlusUserExitSA.C,
Line:1234

2008-10-22-15.24.24.468000+120 I2776032H897 LEVEL: Error
PID : 9884 TID : 5632 PROC : db2syscs.exe
INSTANCE: ODS NODE : 000
APPHDL : 0-71
FUNCTION: DB2 UDB, database utilities, sqlusCUserExitSubAgent::iRun,
probe:1248
MESSAGE : ZRC=0x8015006D=-2146107283=SQLU_CA_BUILT
"SQLCA has already been built"
DATA #1 : LOADID, PD_TYPE_LOADID, 39 bytes
3204.2008-10-22-15.24.23.921001.0 (2;5)
DATA #2 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -3255 sqlerrml: 14
sqlerrmc: REMOTE FETCH 2
sqlerrp : SQLUUREX
sqlerrd : (1) 0x8015006D (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
Oct 22 '08 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.