Fixes are available
APAR status
Closed as program error.
Error description
Using WebSphere MQ queue managers on a host that is heavily loaded with other applications and with many memory demands. Sometimes the node becomes unresponsive and a monitor tool forces the reboot of the host. Most of the time the queue managers are not affected and they restart fine after the reboot. But one time, a queue manager failed to start and generated the following FDC: | Probe Id :- AO000001 | Component :- apiStartup | Major Errorcode :- xecF_E_UNEXPECTED_RC | Minor Errorcode :- arcE_OBJECT_DAMAGED Notice in the FDC that the function that detected the error is one that loads the "Object Catalogue": } aocLoadCatalogue rc=MQRC_OBJECT_DAMAGED { xcsFFST The Object Catalogue became truncated during this forced reboot. The startup of the queue manager is coded to automatically recover (without reporting an FDC) from an object catalogue in such a state, but only if the queue manager has "media recovery", that is, only if it is using linear logging.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: Users may be impacted by this problem if the queue manager ends abnormally, i.e. other than via endmqm. The damaged object catalogue may be unrecoverable for circular logging queue managers. Platforms affected: MultiPlatform **************************************************************** PROBLEM SUMMARY: An update to a queue manager's object catalogue can lead to an inconsistent state if it coincides with an abnormal termination of the queue manager process performing the update.
Problem conclusion
An environment variable, AMQ_FORCE_OBJ_CAT is now provided. That should be set prior to issuing strmqm, and will ensure that all object catalogue updates are forced. Note that there may well be performance implications to use of that environment variable particularly for systems which frequently create/destroy dynamic queues and/or have slow disk systems. --------------------------------------------------------------- The fix is targeted for delivery in the following: v7.0 Platform Fix Pack 7.0.1.11 -------- -------------------- Windows 7.0.1.11 AIX 7.0.1.11 HP-UX (PA-RISC) 7.0.1.11 HP-UX (Itanium) 7.0.1.11 Solaris (SPARC) 7.0.1.11 Solaris (x86-64) 7.0.1.11 iSeries 7.0.1.11 Linux (x86) 7.0.1.11 Linux (x86-64) 7.0.1.11 Linux (zSeries) 7.0.1.11 Linux (Power) 7.0.1.11 v7.1 Platform Fix Pack 7.1.0.4 -------- -------------------- Windows 7.1.0.4 AIX 7.1.0.4 HP-UX (Itanium) 7.1.0.4 Solaris (SPARC) 7.1.0.4 Solaris (x86-64) 7.1.0.4 iSeries 7.1.0.4 Linux (x86) 7.1.0.4 Linux (x86-64) 7.1.0.4 Linux (zSeries) 7.1.0.4 Linux (Power) 7.1.0.4 Version v7.5 -------- -------------------- Fix available in: 7.5.0.2 The latest available maintenance can be obtained from 'WebSphere MQ Recommended Fixes' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037 If the maintenance level is not yet available information on its planned availability can be found in 'WebSphere MQ Planned Maintenance Release Dates' http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309 ---------------------------------------------------------------
Temporary fix
Comments
APAR Information
APAR number
IC87766
Reported component name
WMQ BASE MULTIP
Reported component ID
5724H7241
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-11-01
Closed date
2013-03-14
Last modified date
2013-08-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WMQ BASE MULTIP
Fixed component ID
5724H7241
Applicable component levels
R750 PSY
UP
[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFKSJ","label":"WebSphere MQ"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5"}]
Document Information
Modified date:
23 September 2021