A fix is available
APAR status
Closed as program error.
Error description
While running in log backward mode, if DB2 activity is occurring against a tablespace that the run is currently processing against, it is possible to receive an ALAA447E error message. This can occur if all the following are true: 1. A specific row (page/rid) is continuously deleted, re-inserted, and updated into the same page/rid value. 2. When the tablespace is read for the starting row image, the page/rid is empty (deleted) at that specific time. 3. The last action (i.e., log record) found for that page/rid is an update. This action is not part of the output of the product. It occurs after the requested time range, but is found during detail report log reads. The update occurs after the last update RBA/LRSN (PGLOGRBA value) contained on the page during the tablespace read operation.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of DB2 Log Analysis Tool. * **************************************************************** * PROBLEM DESCRIPTION: While running in log backward mode, if * * DB2 activity is occurring against a * * tablespace that the run is currently * * processing against, it is possible to * * receive an ALAA447E error message. * * This can occur if all the following * * are true: * * 1. A specific row (page/rid) is * * continuously deleted, re-inserted, * * and updated into the same page/rid * * value. * * 2. When the tablespace is read for the * * starting row image, the page/rid is * * empty (deleted) at that specific time. * * 3. The last action (i.e., log record) * * found for that page/rid is an update. * * This action is not part of the output * * of the product. It occurs after the * * requested time range, but is found * * during detail report log reads. The * * update occurs after the last update * * RBA/LRSN (PGLOGRBA value) contained * * on the page during the tablespace read * * operation. * **************************************************************** * RECOMMENDATION: APPLY the PTF. * **************************************************************** Code has been changed to correct this condition.
Problem conclusion
APPLY the PTF.
Temporary fix
Comments
APAR Information
APAR number
PI18361
Reported component name
DB2 LOG ANALYSI
Reported component ID
5655E6601
Reported release
330
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-05-20
Closed date
2014-07-08
Last modified date
2014-08-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
ALAREC
Fix information
Fixed component name
DB2 LOG ANALYSI
Fixed component ID
5655E6601
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSZJXP","label":"DB2 Tools for z\/OS"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.3.0"}]
Document Information
Modified date:
18 March 2021