Home   |   Register   |   Rules   |   Calendar   |   Get Daily   |     |  
 


If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > DB2 Crashes with insert

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 07-13-06, 14:28
mdx34 mdx34 is offline
Registered User
  
Join Date: Oct 2004
Posts: 238
DB2 Crashes with insert
DB2 V8.2 FixPack 1 - Red Hat Linux.

DB2 crashes with the following Insert statement:

INSERT INTO upd.TABLE1
(IDCOLUMN, DATA, IDOTHER)
VALUES (1301,
GX'0041002000500072006900630069006E006700200047007 200690064002000540065006D0070006C00610074006500200 064006500660069006E0065007300200074006800650020006 3006F006C0075006D006E007300200061006E0064002000720 06F0077007300200074006800610074002000770069006C006 C00200062006500200069006E0020006500610063006800200 050006500720066006F0072006D0061006E006300650020004 C006500760065006C0020004D00610074007200690078002E0 0200020005400680065002000500072006900630069006E006 700200047007200690064002000540065006D0070006C00610 0740065002000770069006C006C00200062006500200062007 50069006C007400200074006F00200079006F0075007200200 0730070006500630069006600690063006100740069006F006 E0073002E0020003C00430052004C0046003E003C004300520 04C0046003E002000530065006C00650063007400200074006 800650020006E0075006D0062006500720020006F006600200 063006F006C0075006D006E007300200074006F00200062006 500200069006E0020007400680065002000500072006900630 069006E006700200047007200690064002000740065006D007 0006C0061007400650020006200790020007500730069006E0 0670020007400680065002000550070002F0044006F0077006 E0020006100720072006F007700730020006F0072002000650 06E0074006500720069006E006700200074006800650020007 60061006C00750065002E002000200054006800650020006E0 075006D0062006500720020006F006600200063006F006C007 5006D006E0073002000630061006E006E006F0074002000650 07800630065006500640020003100300030002E0020003C004 30052004C0046003E003C00430052004C0046003E002000570 0680065006E00200079006F007500200068006100760065002 00064006500660069006E00650064002000740068006500200 06E0075006D0062006500720020006F006600200063006F006 C0075006D006E0073002000740068006100740020007700690 06C006C00200062006500200069006E00200079006F0075002 000500072006900630069006E0067002000470072006900640 02000740065006D0070006C006100740065002C00200063006 C00690063006B002000220022004E006500780074002200220 0200074006F00200063006F006E00740069006E00750065002 E',
0
);

From db2 describe:

IDCOLUMN: BIGINT 8
DATA: VARCHAR 4096
IDOTHER: SMALLINT 2

In this case the GX isn't part of the actual data, it is an operator that will accept input in UCS-2 encode unicode characters and decode them into the database

Any ideas ?

Thanks.
Reply With Quote
  #2 (permalink)  
Old 07-13-06, 20:08
sathyaram_s sathyaram_s is offline
Super Moderator
  
Join Date: Aug 2001
Location: UK
Posts: 4,534
I would suggest that you raise a PMR

Have you checked db2diag.log and the Linux system log for any clues ???
__________________
Visit the new-look IDUG Website , register to gain access to the excellent content.
Reply With Quote
  #3 (permalink)  
Old 07-14-06, 09:11
mdx34 mdx34 is offline
Registered User
  
Join Date: Oct 2004
Posts: 238
It doesn't tell me much............

2006-07-13-16.16.26.691672-240 I1655625G417 LEVEL: Severe
PID : 13516 TID : 8192 PROC : db2agent (UPD)
INSTANCE: db2inst1 NODE : 000 DB : UPD
APPHDL : 0-23 APPID: *LOCAL.db2inst1.060713201616
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSignalHandler, probe:10
MESSAGE : DIA0505I Execution of a component signal handling function has begun.

2006-07-13-16.16.26.691793-240 I1656043G430 LEVEL: Severe
PID : 13516 TID : 8192 PROC : db2agent (UPD)
INSTANCE: db2inst1 NODE : 000 DB : UPD
APPHDL : 0-23 APPID: *LOCAL.db2inst1.060713201616
FUNCTION: DB2 UDB, DRDA Application Server, sqljsSignalHandler, probe:20
MESSAGE : DIA0506I Execution of a component signal handling function is
complete.

2006-07-13-16.16.26.691915-240 I1656474G166 LEVEL: Severe
PID:13516 TID:8192 NODE:000 Title: SQLE_AGENTCB
Dump File:/home/db2inst1/sqllib/db2dump/135168192.000

2006-07-13-16.16.26.692008-240 I1656641G174 LEVEL: Severe
PID:13516 TID:8192 NODE:000 Title: SQLE_AGENT_PRIVATECB
Dump File:/home/db2inst1/sqllib/db2dump/135168192.000

2006-07-13-16.16.26.692086-240 I1656816G163 LEVEL: Severe
PID:13516 TID:8192 NODE:000 Title: SQLE_DBCB
Dump File:/home/db2inst1/sqllib/db2dump/135168192.000

2006-07-13-16.16.26.692210-240 I1656980G166 LEVEL: Severe
PID:13516 TID:8192 NODE:000 Title: SQLE_TRAN_CB
Dump File:/home/db2inst1/sqllib/db2dump/135168192.000

2006-07-13-16.16.26.692287-240 I1657147G172 LEVEL: Severe
PID:13516 TID:8192 NODE:000 Title: SQLE_MASTER_APP_CB
Dump File:/home/db2inst1/sqllib/db2dump/135168192.000

2006-07-13-16.16.26.692363-240 I1657320G165 LEVEL: Severe
PID:13516 TID:8192 NODE:000 Title: SQLE_APP_CB
Dump File:/home/db2inst1/sqllib/db2dump/135168192.000

2006-07-13-16.16.26.692442-240 I1657486G173 LEVEL: Severe
PID:13516 TID:8192 NODE:000 Title: SQLE_COORDINATOR_CB
Dump File:/home/db2inst1/sqllib/db2dump/135168192.000

2006-07-13-16.16.26.692528-240 I1657660G171 LEVEL: Severe
PID:13516 TID:8192 NODE:000 Title: SQLE_APP_GROUP_CB
Dump File:/home/db2inst1/sqllib/db2dump/135168192.000

2006-07-13-16.16.26.700175-240 I1657832G429 LEVEL: Severe
PID : 12520 TID : 8192 PROC : db2gds
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUSIGCHLDHandler, probe:50
DATA #1 : String, 158 bytes
Detected the death of an EDU with process id 13516
The signal number that terminated this process was 11
Look for trap files (t13516.*) in the dump directory

2006-07-13-16.16.26.713231-240 E1658262G508 LEVEL: Severe
PID : 12520 TID : 8192 PROC : db2gds
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:10
MESSAGE : ADM0503C An unexpected internal processing error has occurred. ALL
DB2 PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE BEEN SHUTDOWN.
Diagnostic information has been recorded. Contact IBM Support for
further assistance.

2006-07-13-16.16.26.713950-240 E1658771G901 LEVEL: Severe
PID : 12520 TID : 8192 PROC : db2gds
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloEDUCodeTrapHandler, probe:20
DATA #1 : Signal Number Recieved, 4 bytes
6
DATA #2 : Siginfo, 128 bytes
0xBFFFCD18 : 0600 0000 0000 0000 0000 0000 E830 0000 .............0..
0xBFFFCD28 : FF01 0000 6700 0000 0000 0000 0000 0000 ....g...........
0xBFFFCD38 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xBFFFCD48 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xBFFFCD58 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xBFFFCD68 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xBFFFCD78 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0xBFFFCD88 : 0000 0000 0000 0000 0000 0000 0000 0000 ................

2006-07-13-16.16.34.532820-240 I1659673G361 LEVEL: Severe
PID : 12516 TID : 8192 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:15
MESSAGE : DiagData
DATA #1 : Hexdump, 15 bytes
0x08052DCC : 416E 2045 4455 2063 7261 7368 6564 2E An EDU crashed.

2006-07-13-16.16.34.535571-240 I1660035G349 LEVEL: Severe
PID : 12516 TID : 8192 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:16
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0xBFFFD554 : E830 0000 .0..

2006-07-13-16.16.34.535643-240 I1660385G349 LEVEL: Severe
PID : 12516 TID : 8192 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:17
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0xBFFFD54C : 0101 0000 ....

2006-07-13-16.16.34.535706-240 I1660735G349 LEVEL: Severe
PID : 12516 TID : 8192 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:18
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0xBFFFD550 : FFFF FFFF ....

2006-07-13-16.16.34.535779-240 I1661085G349 LEVEL: Severe
PID : 12516 TID : 8192 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:19
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0xBFFFD548 : 88FC FFFF ....

2006-07-13-16.16.34.535849-240 I1661435G339 LEVEL: Severe
PID : 12516 TID : 8192 PROC : db2sysc
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleSysCtlr, probe:10
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0xBFFFD7F4 : 0100 0000 ....

2006-07-13-16.16.34.656675-240 E1661775G503 LEVEL: Severe
PID : 12515 TID : 8192 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloRunInstance, probe:490
MESSAGE : ADM0503C An unexpected internal processing error has occurred. ALL
DB2 PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE BEEN SHUTDOWN.
Diagnostic information has been recorded. Contact IBM Support for
further assistance.

2006-07-13-16.16.34.657554-240 I1662279G350 LEVEL: Severe
PID : 12515 TID : 8192 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloRunInstance, probe:500
MESSAGE : DiagData
DATA #1 : Hexdump, 8 bytes
0xBFFFDAE8 : 0201 0000 0900 0000 ........

2006-07-13-16.16.34.657750-240 I1662630G347 LEVEL: Severe
PID : 12515 TID : 8192 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleCleanupResources, probe:5
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0xBFFFD7F4 : 0201 0000 ....

2006-07-13-16.16.34.658897-240 I1662978G393 LEVEL: Warning
PID : 12515 TID : 8192 PROC : db2wdog
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
MESSAGE : Bringing down all db2fmp processes as part of db2stop
DATA #1 : Hexdump, 4 bytes
0xBFFFD6C8 : 0000 0000 ....

2006-07-13-16.16.43.674203-240 I1663372G311 LEVEL: Event
PID : 13761 TID : 8192 PROC : db2star2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, config/install, sqlfLogUpdateCfgParam, probe:30
CHANGE : CFG DBM: "Instance_Memory" <automatic> From: "4680" To: "4680"

2006-07-13-16.16.46.087287-240 E1663684G975 LEVEL: Event
PID : 13761 TID : 8192 PROC : db2star2
INSTANCE: db2inst1 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
MESSAGE : ADM7513W Database manager has started.
START : DB2 DBM
DATA #1 : Build Level, 124 bytes
Instance "db2inst1" uses "32" bits and DB2 code release "SQL08021"
with level identifier "03020106".
Informational tokens are "DB2 v8.1.0.80", "s041221", "MI00099", FixPak "8".
DATA #2 : System Info, 364 bytes
System: Linux cghlinux3.cghcare.com 4 2 i686
CPU: total:1 online:1
Physical Memory: total:1007 free:553
Virtual Memory: total:1517 free:1063
Swap Memory: total:510 free:510
Kernel Params: msgMaxMessageSize:8192 msgMsgMap:16384 msgMaxQueueIDs:1024
msgNumberOfHeaders:16384 msgMaxQueueSize:16384
msgMaxSegmentSize:16 shmMax:268435456 shmMin:1 shmIDs:4096
shmSegments:4096
Reply With Quote
  #4 (permalink)  
Old 07-14-06, 12:57
umayer umayer is offline
Registered User
  
Join Date: Dec 2005
Posts: 273
DATA is a VARCHAR and you try to insert a GRAPHIC-string.
shoudn't DATA be a VARGRAPHIC type in that case ?
Reply With Quote
  #5 (permalink)  
Old 07-14-06, 16:34
mdx34 mdx34 is offline
Registered User
  
Join Date: Oct 2004
Posts: 238
Yes but believe it or not this works on Windows machine with DB2 V7.2. Would it be that it was an error in 7.2 and fixed in 8.2 ?
Reply With Quote
Reply

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 
 
 
Home  |   Register  |   Get New  |   FAQ's  |   Sitemap

Powered by vBulletin
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.