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

jdbc connection crashing database

P: n/a
Here is my jdbc info

url = jdbc:db2://LXPP04913:60000/TEST
driver = COM.ibm.db2.jdbc.net.DB2Driver

For some reason as I'm importing data via a jdbc client Db2 gets
through a few rows and then crashes. Subsequent connections receive
the

[java] Caused by: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver]
SQL1032N
No start database manager command was issued. SQLSTATE=57019

message. But that seems to be because something kills the db before
hand. My db2diag log file contains the following ominous messages.
Can anyone help me make sense of them?

2005-06-19-19.34.36.118000-420 E387482H791 LEVEL: Event
PID : 1316 TID : 1056 PROC : db2syscs.exe
INSTANCE: DB2 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 "DB2" uses "32" bits and DB2 code release "SQL08020"
with level identifier "03010106".
Informational tokens are "DB2 v8.1.7.445", "s040812", "WR21342", FixPak
"7".
DATA #2 : System Info, 1304 bytes
System: WIN32_NT LXPP04913 Service Pack 1 5.1 x86 Family 6, model 9,
stepping 5
CPU: total:1 online:1
Physical Memory: total:1023 free:379 available:379
Virtual Memory: total:2463 free:1811
Swap Memory: total:1440 free:1432

..
..
..

2005-06-19-19.29.31.320000-420 I383693H444 LEVEL: Severe
PID : 3792 TID : 3584 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TESTDB
APPHDL : 0-11 APPID: *LOCAL.DB2.050620022924
FUNCTION: DB2 UDB, base sys utilities, sqleCleanupResources, probe:5
MESSAGE : DiagData
DATA #1 : Hexdump, 4 bytes
0x01AEFDAC : 0000 0000 ....

2005-06-19-19.29.31.340000-420 I384139H490 LEVEL: Warning
PID : 3792 TID : 3584 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TESTDB
APPHDL : 0-11 APPID: *LOCAL.DB2.050620022924
FUNCTION: DB2 UDB, routine_infrastructure, sqlerKillAllFmps, probe:5
MESSAGE : Bringing down all db2fmp processes as part of db2stop
DATA #1 : Hexdump, 4 bytes
0x01AEFC78 : 0000 0000 ....

2005-06-19-19.29.31.590000-420 E384631H395 LEVEL: Error (OS)
PID : 3996 TID : 2416 PROC : db2jd.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
CALLED : OS, -, unspecified_system_function OSERR: 6
RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
Invalid parameter

2005-06-19-19.29.31.590000-420 E385028H395 LEVEL: Error (OS)
PID : 3996 TID : 2416 PROC : db2jd.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
CALLED : OS, -, unspecified_system_function OSERR: 6
RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
Invalid parameter

2005-06-19-19.29.31.610000-420 I385425H467 LEVEL: Severe
PID : 3792 TID : 3584 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : TESTDB
APPHDL : 0-11 APPID: *LOCAL.DB2.050620022924
FUNCTION: DB2 UDB, SQO Memory Management, sqlofpol, probe:1030
MESSAGE : sqloGetMemChunks not explicitly freed.
DATA #1 : Hexdump, 4 bytes
0x01AEFBFC : 0100 0000 ....

2005-06-19-19.29.31.640000-420 E385894H395 LEVEL: Error (OS)
PID : 3996 TID : 3732 PROC : db2jd.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
CALLED : OS, -, unspecified_system_function OSERR: 6
RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
Invalid parameter

2005-06-19-19.29.31.640000-420 E386291H395 LEVEL: Error (OS)
PID : 3996 TID : 3732 PROC : db2jd.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
CALLED : OS, -, unspecified_system_function OSERR: 6
RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
Invalid parameter

2005-06-19-19.29.31.640000-420 E386688H395 LEVEL: Error (OS)
PID : 3996 TID : 212 PROC : db2jd.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
CALLED : OS, -, unspecified_system_function OSERR: 6
RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
Invalid parameter

2005-06-19-19.29.31.640000-420 E387085H395 LEVEL: Error (OS)
PID : 3996 TID : 212 PROC : db2jd.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, oper system services, sqloSSemClose, probe:20
CALLED : OS, -, unspecified_system_function OSERR: 6
RETCODE : ECF=0x9000000C=-1879048180=ECF_INVALID_PARAMETER
Invalid parameter
<<<<<<<<<<<<

I've also followed a procedure found here to make the local database
appear as if it is a remote database

http://www.mycore.de/faq/FAQ_sql1224N_UK.txt

But I think this is unrelated. Thanks in advance. Here

Nov 12 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Do you have any trap files ? Are you running your application fenced or
unfenced ?
Here obviously Operating system services had some serious problems ,
would call it a db2 defect if you are sure about your application ,
can you give a bit more detail about your application ?

Nov 12 '05 #2

P: n/a
So for all intensive purposes it is a jdbc client using DB2 provided
drivers/classes. I'm running windows XP but also have duplicated the
same error on a DB2 instance running on windows 2003 server.

For my java persistence layer I'm usign hibernate (www.hibernate.org)

where can I find the trap files? what do I use to look at these?

Nov 12 '05 #3

P: n/a
Upgraded my database to 8.2 Fix Pack 9 the problem went away.

Nov 12 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.