Quote:
|
Originally Posted by ashaq
Our DB V7.2 runs on Aix V4.3
Before refreshing the Database we noticed the following message in the db2diag.log
2004-05-03-17.35.20.979394 Instance:db200001 Node:000
PID:9776(db2) Appid:
command_line_process clp_send_bpreq Probe:4
Error returned from SQLOWQUE: ffff f63e
From Troubleshooting guide - f63e means "Bad Queue Handle".
F63E -902 62 Bad queue handle
To obtain detailed information after the database refresh we changed the dbm cfg parameter DIAGLEVEL to 4
but it started flooding the same message in log file which caused the (/home/db200001/sqllib/db2dump(instance directory))
file system full .To avoid the 100% used scenario we allocated more space to the above file system
To reduce the intensity of logging we changed the DIAGLEVEL to default 0.
removed the db2diag , Deactivated the DB ,stopped and started the instance
but we found that same error was been logged in diag file when we expected it would not log any error in the diag file
also the space was not being freed even after removing the diag file
Finally we reset the diaglevel to 3
To make sure that no commands are hung ,we ran the utility ipclean to remove DB2 engine and clients IPC resources
We also tried to remove defunct interprocess communication segments ,semaphore segments ,message queue segments
We found that one of the memory segment was getting killed but was coming up again automatically
this reduced the intensity of logging by 60% but the same error persisted
Any help in this regard will be appretiated
with regards
ashaq
|
Seems there is a problem with the clp talking to the db2bp process, do you see it even when there are no db2bp's out there?
I would suggest a db2 terminate, but seems like you've already killed and cleaned everything... does this effect your ability to issue commands?
Try killing and cleaning everything, then check what db2bp processes are out there... make sure it's not dying when you start issuing commands against the database.
Probably one the lab would have to look at...