Hello,

Here is my config:

Linux 2.6.9-55.ELsmp #1 SMP Wed May 2 14:28:44 EDT 2007 i686 i686 i386 GNU/Linux
IBMJava2-131 under /opt
db2level: DB21085I Instance "test2" uses "32" bits and DB2 code release "SQL08024" with
level identifier "03050106".
Informational tokens are "DB2 v8.1.2.105", "special_15656", "MI00152_15656",
and FixPak "11".
Product is installed at "/opt/IBM/db2/V8.1".

What I've checked:

Symbolic links under /usr/lib are ok
JDK_PATH from the 'db2 get admin cfg'and 'db2 get dbm cfg' are ok
access rights for the fenced user on sqllib/adm/.fenced are ok
latest gcc* package installed.

My problem is that I'm trying to make a sqlj.INSTALL_JAR from DB2 and it's returning me an error:

Call sqlj.INSTALL_JAR( 'file:///opt/IBM/db2data/mtest/tmp/classes/scripts/schema/core/idgenerator/PRC_NEXTVAL.jar','TEST.PRC_NEXTVAL',0)
SQL1131N DARI (Stored Procedure) process has been terminated abnormally.
SQLSTATE=38503

In the db2diag.log, I can see this :

...
2007-12-23-00.23.04.092708+060 I249315G302 LEVEL: Warning
PID : 9206 TID : 3086354112 PROC : db2sysc
INSTANCE: sibdb2 NODE : 000
MESSAGE : Removing FMP from pool
DATA #1 : Hexdump, 12 bytes
0xBFEC0B14 : 0000 0000 1824 0000 0000 0000 .....$......

2007-12-23-00.23.04.095670+060 I249618G427 LEVEL: Severe
PID : 9206 TID : 3086354112 PROC : db2sysc
INSTANCE: sibdb2 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleChildCrashHandler, probe:15
MESSAGE : DiagData
DATA #1 : Hexdump, 24 bytes
0x080525B0 : 4120 6E6F 6E2D 4544 5520 6368 696C 6420 A non-EDU child
0x080525C0 : 6372 6173 6865 642E crashed.
...

If I use the IBMJava2-142, I'm getting the error described in this thread SQL4301N Java or .NET interpreter startup..., reason code "2". SQLSTATE=58004

Does anybody have an idea ?

Phil

Hello,

more informations concerning my problem:
db2clim -l is giving:
Product Name = "DB2 Universal Database Express Edition"
Product Identifier = "DB2EXP"
Version Information = "8.2"
Expiry Date = "Permanent"
Registered User Policy = "Disabled"
Enforcement Policy = "Soft Stop"
Number of processors = "1"
Number of licensed processors = "2"
Annotation = ""
Other information = ""

Seems that the previous sysadmin didn't install the Dev tools, so I was not able to find the 'sqlj.zip',... I've installed them.

Now when I'm echoing my CLASSPATH I can see these libs, but my problem is still the same

Hello,
Just to add some informations,
I've ran 'strace' and found something in the output:
...

[002197a2] getuid32() = 501
[002197a2] open("/opt/IBM/db2data/sib/sqllib/tmp/R1117833A501", O_WRONLY|O_NONBLOCK) = -1 ENOENT (No such file or directory)
[002197a2] getuid32() = 501
[002197a2] msgget(IPC_PRIVATE, IPC_CREAT|IPC_EXCL|0600) = 12320768
[002197a2] clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGC HLD, child_tidptr=0xb7feaa68) = 17840
[002197a2] --- SIGCHLD (Child exited) @ 0 (0) ---
[002197a2] waitpid(17840, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WSTOPPED) = 17840
[002197a2] msgrcv(12320768, 12320768, {1, "\261E\0\0"}, 4, 0, IPC_NOWAIT) = 4
[002197a2] msgctl(12320768, IPC_64|IPC_RMID, 0) = 0
[002197a2] open("/opt/IBM/db2data/sib/sqllib/tmp/R1117833A501", O_WRONLY|O_NONBLOCK) = 3
[002197a2] fcntl64(3, F_GETFL) = 0x801 (flags O_WRONLY|O_NONBLOCK)
...

If someone has an idea...

Phil

It would be helpful if you could check your ~/sqllib/db2dump/ directory (or the directory that DIAGPATH is pointing to). There should be a few more files, including a trap file - first letter of the file name is a 't'. Posting the content here could help track the issue down.

Note: If you can, you should wipe out everything in the ~/sqllib/db2dump/ directory before calling the stored procedure. That will reduce the amount of information collected only to whatever DB2 will write during the problematic SQL statement.

Hi!,

I've checked under the db2dump directory but there was no trap file. So I wiped out the others, restart db2, re-execute the call and generated a trap file (by a kill on db2sys) during this call. Here's the result in attach.

Thanks for your help,

Phil

Killing db2sysc is not good because it doesn't give you the trap file for the crash - instead, you get a trap file for the kill.

Was there anything in the sqllib/db2dump/ directory besides the db2diag.log file? If so, what?

p.s: Your best bet with such crashes is to contact IBM support because they will give you dedicated help. Here, we could only help in figuring what's going on and possible suggest some work-arounds.

Hello,
I've opened a case at IBM.
During this time, I had the opportunity to reconfigure a server and re-install DB2 and it's working fine now... So, I still don't know what was the problem...
Thanks again for your help!