First is the Red Alert for PM51093 that was recently posted on the Red Alert website: http://www14.software.ibm.com/webapp/set2/sas/f/redAlerts/
Other potential data loss HIPERs include:
- PM45458 DB2 10 for z/OS NFM users using UTS may receive ABEND04E RC090105 at DSNIREPR:0C27 when processing an UPDATE on a pointer record.
Correction: PTF UK71644 is available (RSU 1110).
Notes : Latent data page corruption is possible as a result of this problem. DSN1COPY CHECK or the IBM COPY utility can be used to identify corrupted pages. If found to exist, manual REPAIR by IBM Support may be required, and potentially a REORG.
- PM55070 DB2 10 for z/OS NFM users of UTS table spaces defined for row level locking that are performing SQL UPDATE may see broken pages during backout processing.
- PM56535 DB2 10 for z/OS NFM users using UTS that was created in V9 may encounter broken pages during cross partition update cleanup operations in DSNIKDEF.
- PM58114 DB2 for z/OS V9 or DB2 10 for z/OS NFM uses concurrent "LOCK table" and "INSERT" on a PBG TABLESPACE may cause page regression.
Correction: APAR remains open. Corrective relief, AM58114B, is available from DB2 Technical Support. The estimated PTF availability date is April 20.
Notes: Latent data corruption may exist as a result of page regression. CHECK INDEX and CHECK DATA are the best tools for attempting to proactively detect the situation. DSN1LOGP with the CHECK parm may also be used. If any inconsistencies are encountered then they should be corrected, e.g. by using REORG or REBUILD INDEX.
Correction: APAR remains open. Corrective relief, AM55070, is available from DB2 Technical Support. The estimated PTF availability date is April 6.
Notes: This is a problem specific to freespace reuse and later rollback. There should be no latent data corruption. i.e. the only way a customer would have data corruption is if they actually encountered an abend during rollback, in which case the page would be marked broken and they should report the problem to IBM Support.
There is no need for customers to proactively check for problems. If such is desired, then any utility such as DSN1COPY, REORG, COPY or any application access would report a page marked broken.
Correction: PTF UK76352 is available (not yet RSU)
Notes: There is no actual data loss, however, the potential exists for corrupted data pages and orphan pointer records. Customers wishing to proactively check for this condition can use DSN1COPY with the CHECK option, which runs offline and is non-disruptive.
However, the IBM COPY utility would automatically detect corrupted data pages, so a normal backup cycle should be sufficient to validate data. If DB2 detects a problem, then the page may be marked broken. This can be reset by REPAIR using REPAIR LOCATE db.ts PAGE(nnnn) RESET. The IBM REORG utility will correct the page corruption.