I am playing DB2 detective to research further into our outstanding DB2 problems from the recent db2diag.log entries. I understand that you have to decipher the hex code into sql or other db2 errors but what about the other error codes? These are cryptic! If anyone has a good whitepaper on understanding DB2diag.log output files I would be most interested. Thanks!
I use the IBM Problem determination PDFs. I have the same error right now and 001a=decimal 26 (text file busy on AIX.) sqloopenp is the backup/restore function as outlined in the IBM manuals. With this I know something, but don't know what file it's waiting on yet.
I think that you can use the Unix command, ps -ef|grep db2 to search for runaway hung processes. Also the ipcs command will check for bad semaphore calls that may cause problems. I have also found that sometimes very long updates, inserts or deletes in a cursor SQL program will hang the db2 instance as well. We use Quest Central to do database monitoring and this has been helpful. Good luck.