Are there any known issues with db2stop on Solaris 10? The log files have been archived successfully.

njs95d-0004:/tmp> db2level
DB21085I Instance "db2inst4" uses "64" bits and DB2 code release "SQL08028"
with level identifier "03090106".
Informational tokens are "DB2 v8.1.0.136", "s070720", "U810953", and FixPak
"15".
Product is installed at "/opt/IBM/db2/V8.1".

MODEL: SUNW,SPARC-Enterprise-T5220
SunOS RELEASE: 5.10

How long is it hanging? Is there anything in db2diag.log? What if you do "force applications all" before the db2stop? How long does that take? What transactions are running when you do the force? How big are they?

Andy

How long is it hanging? - Until we do a db2_kill. It has hung for several hours.

Is there anything in db2diag.log? - No errors, the last thing I see is that a log file was archived successfully.

What if you do "force applications all" before the db2stop? We do.
How long does that take? Seconds

What transactions are running when you do the force? Its a test environment with little activity.
How big are they?

Is there anything in the db2diag.log about the db2stop being issued?

After you do the "force all", do you check to make sure that they are all gone before you issue db2stop? Do you still issue db2stop force? If so try it without the force.

Andy

Please try following

db2set db2comm=
db2 force applications all
db2 deactivate db <dbname>


before db2stop force.

It seemed to work on one of our mirror database. we are having same issues with db2 V8 servers.

DBFinder

Sometimes DB2 will hang, in which case you can issue the ipclean command to kill all Db2 processes. Works on AIX and Linux, so I assume it works on Solaris.