By kellyc-Oracle on Aug 21, 2009
I finally succumbed to the peer pressure. So now we have a blog about dbhang.
You can get the current version of the dbhang tarball from the GDD site.
You may also find a recent version in /opt/sun/comms/messaging64/examples/unsupported on your system.
dbhang is a troubleshooting data collection script for use with Sun's Messaging Server product. The name comes from the fact that the original intent, long ago, was to gather data specifically about problems where something is "hanging" because of a lock in the message store database. It has long since grown to gather, among other things:
- a smattering of current system performance type information
- process stack trace of all (most) Messaging Server processes
- commonly needed configuration information
- some logs
There are command line switches or options you can edit in the script to gather other things, but the defaults is usually the best place to start.
I do not want to encourage people to try to just collect data without understanding what data will really be useful. But if you have no idea where to start, at least some of the info collected by dbhang should be useful when you open a support case.
The tar ball on the GDD site contians v2.10 for use on iMS 5.2 systems and the current version for use on Messaging Server 6.x and 7 systems. It also contains examples of how you could use a wrapper around msprobe to make it invoke dbhang automatically if it detects a hang problem, before it initiates a restart.
I am interested in any comments about how to use dbhang, ideas about improving it, or discussion of how to interpret the data. But we should defer discussion of specific problems to the developer forum, info-ims mailing list, or the official support mechanisms.