Example recovery scenarios

 

This chapter describes procedures for recovering WebSphere MQ after various error conditions. These error conditions are grouped in the following categories:

Table 5. Example recovery scenarios

Problem category	Problem	Where to look next
Shared queue problems	Queue both private and shared.	Shared queue problems
Active log problems	Dual logging is lost. Active log has stopped. One or both copies of the active log data set are damaged. Write errors on active log data set. Active log is becoming full or is full. Read errors on active log data set.	Active log problems
Archive log problems	Insufficient DASD space to complete off-loading active log data sets. Off-load task has terminated abnormally. Archive data set allocation problem. Read I/O errors on the archive data set during restart.	Archive log problems
BSDS problems	Error opening BSDS. Log content does not correspond with BSDS information. Both copies of the BSDS are damaged. Unequal time stamps. Dual BSDS data sets are out of synchronization. I/O error on BSDS.	BSDS problems
Page set problems	Page set full. A page set has an I/O error.	Page set problems
Coupling Facility and DB2 problems	Storage medium full. DB2 system fails. DB2 data-sharing group fails. DB2 and the Coupling Facility fail.	Coupling Facility and DB2 problems
Unit of work problems	A long-running unit of work is encountered.	Problems with long-running units of work
IMS problems	An IMS application terminates abnormally. The IMS adapter cannot connect to WebSphere MQ. IMS not operational.	IMS-related problems