APAR status
Closed as program error.
Error description
QCAPTURE stalling on occasion as total memory allocated for transactions approaches MEMORY_LIMIT.
Local fix
Problem summary
Problem Description: In the IBMQREP_CAPMON table, CURRENT_LOG_TIME does not increase, and LOGRDR_SLEEPTIME accounts for 100% of log reading thread time. . User Affected: Q Capture users . Problem Summary: QCAPTURE log reading thread might permanently suspend itself when memory used for transactions approaches the MEMORY_LIMIT parameter value and it waits for memory to be freed after transactions are published. . Problem Conclusion: QCAPTURE correctly determines when it can resume reading from the db2 log.
Problem conclusion
This fix will be available in DB2 LUW V9.5 FP9.
Temporary fix
Comments
APAR Information
APAR number
JR42117
Reported component name
WS Q-REPLIC LUW
Reported component ID
5724N9801
Reported release
950
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-02-29
Closed date
2012-02-29
Last modified date
2012-02-29
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
WS Q-REPLIC LUW
Fixed component ID
5724N9801
Applicable component levels
R950 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSDP5R","label":"InfoSphere Replication Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
29 February 2012