Was it the first connection ? Then, obviously, it will be quiet slow because db2 has to allocate memory resources+ primary log files for the dataabse ....
Another reason for the first connection taking longer time is Crash Recovery (which has not, in your case, as, with diaglevel 3, crash recover writes info to db2diag.log)
One other reason can be INDEXREC parm set to restart ... If so, invalid indexes will be rebuilt on the activation of the database (Not sure whether this will write to db2diag.log, but would assume so ... ) .. This parameter being set to restart is what I would recommend .. The other option is access , in which case, the index will be rebuild during the first access to the object , therby, making the query 'hang'
Originally posted by mixxalot
Actually I find no errors in db2diag log file and the node directory issue has nothing to do with connection problems to db2. Found out that I may need to run the db2 activate database command to have more stable connection state for db2. But weird to have the db2 connect run so slowly.