Red Alert for DB2 V9 http://www14.software.ibm.com/webapp/set2/sas/f/redAlerts/20090325.html
Are you signed up for Red Alerts? You should be. http://www14.software.ibm.com/webapp/set2/sas/f/redAlerts/home.html Best Regards, Sam Knutson Abstract: DB2 9 for z/OS potential data loss following REORG or REBUILD INDEX in non-data sharing. 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. * The first exposure exists if the following are all true: 1. The subsystem is non-data sharing. 2. The subsystem is in New Function Mode (NFM). 3. The current log RBA is greater than the z/OS system timestamp value. If the above criteria are satisfied and REORG or REBUILD INDEX with a LOG phase is run then data loss may occur. APAR PK82890 has been created to address this problem. The second, unrelated, exposure exists if the following are all true: 1. The subsystem is non-data sharing. 2. The subsystem is in the process of being converted to NFM or has just been converted to NFM. 3. REORG or REBUILD INDEX with a LOG phase is run during or immediately following conversion to NFM. If the above criteria are satisfied then data loss may occur due to skipped SYSLGRNX entries during the LOG phase. APAR PK83078 has been created to address this problem. Note that there is no exposure to this second problem for V9 non-datasharing systems that remain in CM or have already been converted to NFM. Recommended Actions: If a DB2 subsystem meets the criteria for the first defect then avoid REORG or REBUILD INDEX with a LOG phase until the solution for PK82890 is applied. To avoid exposure to the second problem, either avoid conversion from CM to NFM mode until the solution for PK83078 is applied, or if conversion to NFM is necessary prior to applying the fix for PK83078 then ensure that DB2 is stopped and started prior to running any REORG or REBUILD INDEX with a LOG phase following conversion. ==================== This email/fax message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this email/fax is prohibited. If you are not the intended recipient, please destroy all paper and electronic copies of the original message. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
