On October 29, 2015, IBM issued a Red Alert to any DB2 11 customer converting partition table spaces from basic format to extended format. Red Alerts are used to identify and notify customers of critical issues with IBM z Systems products. They should be immediately reviewed to determine how they may impact your specific environment.
Posted Saturday, July 18, 2015
If you have a product license for DB2 11 for z/OS or DB2 10 for z/OS, it’s time to get your updated copy of the Diagnosis Guide and Reference. DB2 11 for z/OS Diagnostics Guide and Reference (LY37-3222-03), the Fourth edition published June 2015 and DB2 10 for z/OS Diagnosis Guide and Reference (LY37-3220-08), the Ninth edition published June 2015 are now available via APAR PI43370. The correct associated PTF number is listed in the APAR cover.
It appears that in rare situations the DB2 log records could be written with invalid control information, not a good thing. A “ Red Alert” was put out today by the Red Alert subscription service for zSeries to warn customers of this serious situation. This is a situation that should be taken lightly. It issue should be addressed or at the very least reviewed for the potential impact to your installation.
Posted Friday June 11, 2015
Testing for RSU service package RSU1505 is now complete. This June 9, 2015 1st Quarter “1st quarter Quarterly Report, 2nd Addendum” (57.1 KB PDF file) is based on RSU1503 recommendations and contains ALL service through the end of December 2014 not already marked RSU. This service also includes PE resolution and HIPER/Security/Integrity/Pervasive PTFs and their associated requisites and supersedes through the end of April 2015.
I was attempting to move away from posting about fixes to issues in DB2. It felt like I was doing it way to often, almost like a easy why out of dreaming up my own content. However, with that said, I thought the following APAR was worth decimating to my readers. The issue this APAR addresses with its potential consequences if not applied justifies an APAR post this week.
Testing for RSU service package RSU1504 is now complete. This April 3, 2015 1st Quarter “1st quarter Quarterly Report, 1st Addendum” (55 KB PDF file) contains ALL service through the end of December 2014 not already marked RSU. This service also includes PE resolution and HIPER/Security/Integrity/Pervasive PTFs and their associated requisites and supersedes through the end of March 2015.
Posted Friday March 6, 2015
Testing for RSU service package RSU1502 is now complete. This March 4, 2015 4th Quarter “2nd Addendum Quarterly Report” (65 KB PDF file) is based on the 4th quarter 2014 service ( RSU1412) and contains ALL service through the end of September 2014 not already marked RSU. This service also includes PE resolution and HIPER/Security/Integrity/Pervasive PTFs and their associated requisites and supersedes through January 2015.
Sometimes I feel like I am a waling advertisement for DB2 maintenance, like it’s the only thing I blog about. Although it may seem like that (and I actually hope it doesn’t), I do try to publish blog entries that cover general information that I think could be of use to the many. I try to stay away from the stuff that is obviously a fix for a program error; 0C7, 04E, or some other system threatening abend or return code.
Posted Wednesday, February 11, 2015
Sometimes receiving an extra cup of coffee, a second handful of M&M’s, a few more minutes of sleep, or a little extra time to get to your destination is a good thing. We most all enjoy the occasional “more”. However it you are talking DB2 for z/OS and happen to be running an INDEX REBUILD, too much can lead to certain disaster.
Unless you are running your DB2 10 or DB2 11 subsystem right at the bleeding edge of DB2’s maintenance, it is possible that you could crash your DB2 by simply running a REBUILD INDEX against an unique index having a few too many duplicate keys.