Question & Answer
Question
How to recover when Q Capture fails with messages similar to these:
<sendQueue::putTransMsg> ASN0575E "Q Capture" : "ASN" : "WorkerThread" : The program encountered a WebSphere MQ error "2003 (MQRC_BACKED_OUT)" while issuing the WebSphere MQ command "MQPUT" on object "SENDQ".
<sendQueue::rowBufferTooSmall> ASN0589I "Q Capture" : "ASN" : "WorkerThread" The program received return code "503" from routine "putTransMsg".
<subMgr::consGroupInError> ASN7015W "Q Capture" : "ASN" : "WorkerThread" : The program detected an unrecoverable MQ error for send queue "SENDQ". Publishing or replication queue map: "QMAP1". The error action specified for the queue map is "S". Look for a previous message with more information about the MQ error on this queue.
<sendQueue::rowBufferTooSmall> ASN0589I "Q Capture" : "ASN" : "WorkerThread" The program received return code "6030" from routine "queueInError".
<sendQueue::rowBufferTooSmall> ASN0589I "Q Capture" : "ASN" : "WorkerThread" The program received return code "503" from routine "putTransMsg".
<subMgr::consGroupInError> ASN7015W "Q Capture" : "ASN" : "WorkerThread" : The program detected an unrecoverable MQ error for send queue "SENDQ". Publishing or replication queue map: "QMAP1". The error action specified for the queue map is "S". Look for a previous message with more information about the MQ error on this queue.
<sendQueue::rowBufferTooSmall> ASN0589I "Q Capture" : "ASN" : "WorkerThread" The program received return code "6030" from routine "queueInError".
Answer
"2003 (MQRC_BACKED_OUT)" means that a unit of work has been rolled back because the queue manager ran out of log space while the Q Capture program was trying to put message onto sendq.
To resolve the problem, do the following to increase MQ log space
a. Stop Q Capture and MQ manager
b. Increase LogPrimaryFiles, LogSecondaryFiles, or LogFilePages MQ parameters so that the largest
transaction can fit.
These parameters are in the QM.INI file on UNIX. By default, QM.INI is found in
/var/mqm/qmgrs/<qmgrname>/ (where qmgrname is the name of the queue manager).
/var/mqm/qmgrs/<qmgrname>/ (where qmgrname is the name of the queue manager).
On Windows, the values are located in the Windows registry. For instance, they are under
HKEY_LOCAL_MACHINE-> SOFTWARE-> IBM -> MQSeries -> CurrentVersion -> Configuration ->
LogDefaults.
HKEY_LOCAL_MACHINE-> SOFTWARE-> IBM -> MQSeries -> CurrentVersion -> Configuration ->
LogDefaults.
If you don't know how many logs are needed or transactions don't normally get this large, then increase
LogSecondaryFiles first so space will only be allocated as needed and not preallocated as will be the case
with LogPrimaryFiles.
LogSecondaryFiles first so space will only be allocated as needed and not preallocated as will be the case
with LogPrimaryFiles.
Queue manager will need to be restarted. If increase LogFilePages, then queue manager needs to be
recreated.
recreated.
You will also need to be sure that enough space is available on filesystem to handle additional logs.
e.g. total log space = LogFilePagesx4KBx(primary + secondary)
e.g. total log space = LogFilePagesx4KBx(primary + secondary)
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTRGZ","label":"InfoSphere Data Replication"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Was this topic helpful?
Document Information
Modified date:
14 November 2019
UID
ibm11107285