Load from cursor may fail with unexpected errors in the
following cases:
Please note that the SAMPLE database used by the examples is
created by db2sampl command.
1. Load from cursor fails with SQL1224N only when loading from a
column of CLOB data type to a column of DATE/TIME/TIMESTAMP data
type and the CLOB length is much greater than maximum length
that a TIMESTAMP column supports.
Symptom (use the DATE data type as an example):
$ db2 connect to SAMPLE
$ db2 "create table load1DATE (col1 DATE)"
$ db2 "declare mycursCLOB cursor for select RESUME from
EMP_RESUME"
$ db2 "load from mycursCLOB of cursor insert into load1DATE"
SQL1224N The database manager is not able to accept new
requests, has terminated all requests in progress, or has
terminated the specified request because of an error or a forced
interrupt. SQLSTATE=55032
2011-06-22-11.45.39.723181-240 I10798E505 LEVEL: Severe
PID : 28692 TID : 46912883386688PROC :
db2sysc
INSTANCE: amahadev NODE : 000 DB : SAMPLE
APPHDL : 0-25 APPID:
*LOCAL.amahadev.110622154443
AUTHID : AMAHADEV
EDUID : 72 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, RAS/PD component,
pdEDUIsInDB2KernelOperation, probe:180
MESSAGE : Stack analysis failed due to incomplete 'StackTrace'
section in trap file.
2011-06-22-11.45.39.723362-240 I11304E513 LEVEL: Severe
PID : 28692 TID : 46912883386688PROC :
db2sysc
INSTANCE: amahadev NODE : 000 DB : SAMPLE
APPHDL : 0-25 APPID:
*LOCAL.amahadev.110622154443
AUTHID : AMAHADEV
EDUID : 72 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, RAS/PD component,
pdEDUIsInDB2KernelOperation, probe:190
MESSAGE : Stack analysis failed, which implies stack corruption
or failed to do 'stack walk'.
2011-06-22-11.45.39.723442-240 I11818E556 LEVEL: Severe
PID : 28692 TID : 46912883386688PROC :
db2sysc
INSTANCE: amahadev NODE : 000 DB : SAMPLE
APPHDL : 0-25 APPID:
*LOCAL.amahadev.110622154443
AUTHID : AMAHADEV
EDUID : 72 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, RAS/PD component,
pdResilienceIsSafeToSustain, probe:800
DATA #1 : String, 37 bytes
Trap Sustainability Criteria Checking
DATA #2 : Hex integer, 8 bytes
0x000000030202180C
DATA #3 : Boolean, 1 bytes
false
2. Load from cursor fails with SQL0902C when loading from a
column of BLOB data type to a column of GRAPHIC/VARGRAPHIC/LONG
VARGRAPHIC/DBCLOB data type.
Symptom (use the GRAPHIC data type as an example):
$ db2 connect to SAMPLE
$ db2 "create table aarti43 (JOB GRAPHIC(5))"
$ db2 "declare mycursBLOB cursor for select PICTURE from
EMP_PHOTO"
$ db2 "load from mycursBLOB of cursor insert into aarti43"
SQL0902C A system error (reason code = "84") occurred.
Subsequent SQL statements cannot be processed. SQLSTATE=58005
2011-06-06-12.26.19.826394-240 I4716E717 LEVEL: Error
PID : 17519 TID : 47482268543296PROC :
db2sysc
INSTANCE: amahadev NODE : 000 DB : SAMPLE
APPHDL : 0-3793 APPID:
*LOCAL.amahadev.110606162547
AUTHID : AMAHADEV
EDUID : 3540 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, database utilities,
sqluCCrossParser::zInitialize, probe:1694
MESSAGE : ZRC=0x87150054=-2028666796=SQLU_PRG_ERR "Program
error" DIA8575C An index manager programming error occurred.
DATA #1 : LOADID, PD_TYPE_LOADID, 46 bytes
LOADID: 251.2011-06-06-12.26.19.251364.0 (3;5)
DATA #2 : File name, 16 bytes
sqlulxld_parse.C
DATA #4 : signed integer, 2 bytes
264
2011-06-06-12.26.19.826627-240 I5434E533 LEVEL: Error
PID : 17519 TID : 47482268543296PROC :
db2sysc
INSTANCE: amahadev NODE : 000 DB : SAMPLE
APPHDL : 0-3793 APPID:
*LOCAL.amahadev.110606162547
AUTHID : AMAHADEV
EDUID : 3540 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 114 bytes
LOADID: 251.2011-06-06-12.26.19.251364.0 (3;5)
, -2028666796, (nil), Detected in file:sqlulxld_parse.C,
Line:5214
2011-06-06-12.26.19.826750-240 I5968E530 LEVEL: Error
PID : 17519 TID : 47482268543296PROC :
db2sysc
INSTANCE: amahadev NODE : 000 DB : SAMPLE
APPHDL : 0-3793 APPID:
*LOCAL.amahadev.110606162547
AUTHID : AMAHADEV
EDUID : 3540 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 111 bytes
LOADID: 251.2011-06-06-12.26.19.251364.0 (3;5)
, -2028666796, (nil), Detected in file:sqlulxld_mem.C, Line:188
2011-06-06-12.26.19.826864-240 I6499E532 LEVEL: Error
PID : 17519 TID : 47482268543296PROC :
db2sysc
INSTANCE: amahadev NODE : 000 DB : SAMPLE
APPHDL : 0-3793 APPID:
*LOCAL.amahadev.110606162547
AUTHID : AMAHADEV
EDUID : 3540 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, database utilities, DIAG_ERROR, probe:0
DATA #1 : String, 113 bytes
LOADID: 251.2011-06-06-12.26.19.251364.0 (3;5)
, -2028666796, (nil), Detected in file:sqlulxld_parse.C,
Line:600
3. Load from cursor fails with SQL0901N when loading from a
column of DATE/TIME/TIMESTAMP data type to a column of XML data
type.
Symptom (use the TIME data type as an example):
$ db2 connect to SAMPLE
$ db2 "create table aarti7XML (ADDR XML)"
$ db2 "declare mycursTIME cursor for select STARTING from
CL_SCHED"
$ db2 "load from mycursTIME of cursor insert into aarti7XML"
SQL0901N The SQL statement failed because of a non-severe
system error. Subsequent SQL statements can be processed.
(Reason "Unknown zvalue type: 15".) SQLSTATE=58004
2011-06-07-16.54.23.074536-240 I48459E2766 LEVEL: Severe
PID : 18285 TID : 47639999539520PROC :
db2sysc
INSTANCE: amahadev NODE : 000 DB : SAMPLE
APPHDL : 0-7 APPID:
*LOCAL.amahadev.110607205334
AUTHID : AMAHADEV
EDUID : 60 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, XML Node Manager, xmlrnInsertDocument,
probe:825
MESSAGE : ZRC=0x82A40001=-2103181311=XMLRN_PRG_ERR
"XMRN unexpected system error"
DIA8532C An internal processing error has occurred.
DATA #1 : String, 23 bytes
Unknown zvalue type: 15
DATA #2 : XML data descriptor, PD_TYPE_XMRN_XMLDD, 80 bytes
CALLSTCK:
[0] 0x00002B53FE647C96 pdLog + 0x398
[1] 0x00002B5400D61A30 _Z19xmlrnInsertDocumentP11XmlrnIUD_CB +
0x2E0
[2] 0x00002B53FE6F8AFC
_Z21sqldInsertXMLDocumentP8sqeAgentP8SQLD_TCBiP10sqlz_valueP14SQ
LXMS_XDADESCS6_
+ 0x4A2
[3] 0x00002B54009A1B8F
/home/hotellnx88/amahadev/sqllib/lib64/libdb2e.so.1 + 0x309BB8F
[4] 0x00002B54009A3D01
_Z22sqluLoadFormatFixedVarP8sqeAgentP13SQLD_TDATARECS2_PP10SQLD_
VALUEiP8SQLD_TCBPiPhP15SQLD_XOR_UPDATEP8SQLD_CCB
+ 0xBE1
[5] 0x00002B53FEDDC4D8
_Z14sqluLoadFormatP8sqeAgentP13SQLD_TDATARECS2_PP10SQLD_VALUEiP8
SQLD_TCBPiPhP15SQLD_XOR_UPDATEP8SQLD_CCB
+ 0x4A
[6] 0x00002B540097879B
_Z15sqluFormatDMRecP13SQLUCACB_TYPEP17SQLU_FORMATTER_CBjPP10SQLD
_VALUEP14sqlrg_mdc_infoP12SQLU_RP_INFOji
+ 0x5CB
[7] 0x00002B5400940588
/home/hotellnx88/amahadev/sqllib/lib64/libdb2e.so.1 + 0x303A588
[8] 0x00002B540093AAE3 _ZN14sqluCFormatter4iRunEv + 0x865
[9] 0x00002B54009B80BA _Z17sqluLoadEDUDriverPhj + 0x2EA
2011-06-07-16.54.23.097505-240 I51226E1535 LEVEL: Severe
PID : 18285 TID : 47639999539520PROC :
db2sysc
INSTANCE: amahadev NODE : 000 DB : SAMPLE
APPHDL : 0-7 APPID:
*LOCAL.amahadev.110607205334
AUTHID : AMAHADEV
EDUID : 60 EDUNAME: db2lfrm0
FUNCTION: DB2 UDB, XML Node Manager, xmlrnInsertDocument,
probe:825
MESSAGE : ZRC=0x82A40001=-2103181311=XMLRN_PRG_ERR
"XMRN unexpected system error"
DIA8532C An internal processing error has occurred.
DATA #1 : String, 4 bytes
none
CALLSTCK:
[0] 0x00002B53FE647C96 pdLog + 0x398
[1] 0x00002B5400D4FBD8 _Z15xmlrnLogErrorRcmiiPc + 0xD6
[2] 0x00002B5400D61A45 _Z19xmlrnInsertDocumentP11XmlrnIUD_CB +
0x2F5
[3] 0x00002B53FE6F8AFC
_Z21sqldInsertXMLDocumentP8sqeAgentP8SQLD_TCBiP10sqlz_valueP14SQ
LXMS_XDADESCS6_
+ 0x4A2
[4] 0x00002B54009A1B8F
/home/hotellnx88/amahadev/sqllib/lib64/libdb2e.so.1 + 0x309BB8F
[5] 0x00002B54009A3D01
_Z22sqluLoadFormatFixedVarP8sqeAgentP13SQLD_TDATARECS2_PP10SQLD_
VALUEiP8SQLD_TCBPiPhP15SQLD_XOR_UPDATEP8SQLD_CCB
+ 0xBE1
[6] 0x00002B53FEDDC4D8
_Z14sqluLoadFormatP8sqeAgentP13SQLD_TDATARECS2_PP10SQLD_VALUEiP8
SQLD_TCBPiPhP15SQLD_XOR_UPDATEP8SQLD_CCB
+ 0x4A
[7] 0x00002B540097879B
_Z15sqluFormatDMRecP13SQLUCACB_TYPEP17SQLU_FORMATTER_CBjPP10SQLD
_VALUEP14sqlrg_mdc_infoP12SQLU_RP_INFOji
+ 0x5CB
[8] 0x00002B5400940588
/home/hotellnx88/amahadev/sqllib/lib64/libdb2e.so.1 + 0x303A588
[9] 0x00002B540093AAE3 _ZN14sqluCFormatter4iRunEv + 0x865
Conclusion:
For case 1, the failure is due to too long source data that
causes memory overflow during loading.
For case 2 and 3, the failures are due to incompatible column
data types.
Solution:
For case 1, load from cursor should avoid memory overflow and
reject invalid source data.
For case 2 and 3, load from cursor should fail with SQL1188N
gracefully. |
