dear all,

just wonder if anyone tested DB2 V8.1 FP4 under AIX 5.1 ML 5 ?
knowing that i tested DB2 V8.1 FP4 under Linux works fine !

Mainly i got 2 problems :

1. while using Xmanager from windowns machine to access the AIX machine, tyring to start up the db2cc i have this error :
[IBM] JDBC java.lang.UnsatisfiedLinkError: cannot find library
db2jdbc (libdb2jdbcr.a or .so) in java.library.path
java.lbrary.path=/usr/java131/jre/bin:/usr/java131/jre/bin/classic:/usr/lib

i found a dummy solution for it is to do :
export LIBPATH=/usr/lib:/lib:/home/db2inst1/sqllib/lib ; db2cc

it looks strange, but this happen only with CDE


2. while using the control center, somtimes i get this error
[IBM] CLI Dirver SQL1224N a database agent could not be started to service request, or was terminated as a result of database system shutdown or force command. SQLSTATE=55032

and i got this in db2diag.log :

2004-01-13-15.01.10.619925 Instance:db2inst1 Node:000
PID:13498(java) TID:1029 Appid:none
SQO Memory Management sqlocshr2 Probe:200
errno:
0x38FC2D24 : 0x00000018

2004-01-13-15.01.11.161802 Instance:db2inst1 Node:000
PID:13498(java) TID:1029 Appid:none
SQO Memory Management sqlocshr2 Probe:200
pSetHdl:
0x38FC2E94 : FFFF FFFF FFFF FFFF 0000 0000 003E 000B
0x38FC2EA4 : 0004 0000


i have checked the number of process DB2 use , the database manager is running, i still can connect using CLP (db2 connect to xyz user xx using yy )


can anyone help !!

I would check the the db2diag.log on both server and client.

From your posting I understand that you are accessing your AIX box from a remote Windows Client through XManager. Can you tell me if you set DISPLAY in your XManager?

Control Center runs at client. So check the diaglog at the client. You could also access the DB from your local control center.

playing around with control center, i found a solution for this error
it says that databe archive log should be used insetd of circular logging
and when i change the DB logging , everything works fine, no more ERRORS, i think this is STRANGE

anyone have an idea why ?

I got this same error and my db is not using archive logging, but with one difference, this error occurs not using any java feature, I got it from the fault monitor. As it follows. I hope not having to turn my db onto archive logging, that would ridiculous as it can be.

2004-02-01-23.59.15.158926 Instance:db2inst1 Node:000
PID:19297(db2fmd) TID:1 Appid:none
SQO Memory Management sqlocshr2 Probe:200

pSetHdl:
0xFFB19794 : 1000 0000 1000 0000 0000 0000 0000 200C .............. .
0xFFB197A4 : 0000 0000 ....