Blog
DB2utor

Categories

April 21, 2009

Be Alert for Red Alerts

On March 25 IBM posted a Red Alert titled, "DB2 9 for z/OS potential data loss following REORG or REBUILD INDEX in non-data sharing."

You'll want to read the entire alert, but here's a short description:

"Two unrelated defects have been identified that may result in data loss in DB2 9 for z/OS due to the LOG phase of REORG or REBUILD INDEX incorrectly skipping SYSLGRNX entries.
"The following REORG and REBUILD INDEX utilities have a LOG phase and are therefore exposed to these defects:

  • REBUILD INDEX with SHRLEVEL CHANGE.
  • REORG with SHRLEVEL CHANGE.
  • REORG with SHRLEVEL REFERENCE at the partition level and a non-partitioned secondary index exists on the table."

IBM describes Red Alerts as a subscription service that provides technical information for mainframe professionals. Check the Web site and you'll see that DB2-specific Red Alerts occur only about once per year.

  • June 17, 2008: "DB2 for z/OS V8 and V9 potential loss of data during update of fixed length rows."
  • April 05, 2007: "DB2 for z/OS V7 potential loss of data with partitioned tablespaces in a data sharing environment."

Infrequent as they are, when Red Alerts do occur you'll want to know about them as soon as possible to avoid any potential data loss. To receive free notification of Red Alerts, go to the Red Alerts Subscription Service and select the "Sign up" link in the box on the upper right.