Gautam K. Bhat is an IBM Senior Certified IT Specialist, Chief Architect for Americas clients, and Global Subject Matter Expert for Messaging, Integration, and Middleware. He is involved in training and coaching at the Middleware Center of Excellence (CoE) for IBM Global Technology Services for strategic outsourcing in India. His professional certifications include Sun Certified Business Component Developer, Sun Certified Java Programmer, Sun Certified Web Component Developer, Service Oriented Architecture Associate, WebSphere Message Broker Administrator, and WebSphere MQ Administrator. You can contact Gautam at firstname.lastname@example.org .
This article is about disaster recovery, specifically recovering the queue manager and broker after a server crash involving IBM® WebSphere® MQ V7 and IBM WebSphere Message Broker V7/V8. A server crash can consist of any abrupt restart of the server that does not allow WebSphere MQ and WebSphere Message Broker shutdown routines to complete before the server goes down. It includes server hangs where the administrator must reboot the server, and the shutdown routines are not able to complete. This
article describes error scenarios following abrupt server restart, and shows system administrators how to recover from such situations.
Existing resources such as information centers provide standard WebSphere MQ and WebSphere Message Broker restore commands, but lack step-by-step troubleshooting information and additional steps that are sometimes needed to recover the environment. This article is for WebSphere MQ and WebSphere Message Broker administrators, and Integration and Infrastructure Architects who need to guide their Support Teams in recovering from a server crash. Many customers have business-critical applications that use WebSphere MQ as a messaging system and WebSphere Message Broker for transformation, enrichment, and routing, so detailed information on this topic is worth knowing.
Recovering the MQ queue manager
You attempt to restart the MQ queue manager after a server crash and startup fails.
The queue manager active logs appear okay, and the command strmqm –c for recovering any damaged system objects does not work. When starting the queue manager, you may see this error: