Title:
For DB2 V10 and DB2 V11 users: DB2 log records may be written with invalid control information in certain rare cancel window situations and cause unpredictable results
Abstract:
DB2 log records may be written with invalid control information in certain rare cancel window situations. This could cause log read errors, data replication issues, recovery issues, or even potential data loss. Both DB2 10 and 11 systems are affected, although the exposure is higher for DB2 11 systems that have not converted BSDS data sets to use 10 byte RBA values. DB2 9 and prior releases are not affected.
There's an entire description in the Red Alert itself. Let me just give you the recommended actions.
There's an entire description in the Red Alert itself. Let me just give you the recommended actions.
Recommended Actions for DB2 11 customers:
Recommended Actions for DB2 10 customers:
If you haven't signed up to the Red Alerts by now, you really should do it. Just go over here. - Install APAR PI41630 (PTF UI28315). This fix will prevent log records with LRSN value of 'FFFFFFFFFBAD'x being created.
- Install APARFIX for PI42170 (AI42170) or PTF when available. This fix will prevent log records with invalid values being created, and it contains toleration code to recognize and recover from the incorrect values, including LRSN value of 'FFFFFFFFFBAD'x.
- Install APARFIX for PI42170 (AI42170) or PTF when available. This fix will prevent log records with invalid values being created, and it contains toleration code to recognize and recover from the incorrect values, including LRSN value of 'FFFFFFFFFBAD'x if the system fallback from DB2 11.
No comments:
Post a Comment