A fix is available
APAR status
Closed as program error.
Error description
After a REORG PART to convert a tablespace partition from 6 byte to 10 byte lrsn format, the following errors can occur: DSNISMSU ERQUAL0CA8 or ERQUAL0CA9 RC00C90101 DSNISMRS ERQUAL5003 RC00C90101 DSNIBROK RC00C90105 DSNIRFNX ERQUAL5398 RC00C90101 Keywords: DB2EXTRBA/K ExtendedRBA DB2OVRLAY/K
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: DB2 V11 users, with table spaces created in, * * or converted to, extended format (that is, * * with 10-byte RBA/LRSN values). * **************************************************************** * PROBLEM DESCRIPTION: Corrupted space map pages, resulting in * * any of the following abends (not an * * exhaustive list): * * - ABEND0C4 in DSNILSMG * * - ABEND04E RC00E40316 in DSNUKIUL * * - ABEND04E RC00C90105 in DSNISMSU:0CA8 * * - ABEND04E RC00C90105 in DSNIWLPG:0CA8 * * * * Corrputed space map pages may also * * cause messages similar to these * * (not an exhaustive list): * * * * - DSNU518I -DB2A DSNUBASA - * * TABLESPACE BP1DB.BP1TS * * DSNUM 1 CONTAINS BROKEN PAGE * * X'00000EF2' ERROR CODE X'0C33' * * * * - DSNU441I -DB2A DSNUBASA - BROKEN * * PAGE FOUND DBNAME = BP1DB * * TSNAME = BP1TS DSNUM = 1 * * PAGE = X'00000001' * * ERRORCODE = X'0CA8' * * * * - DSNI010I -DB2A BROKEN PAGE ACCESSED * * TYPE 00000302 * * NAME BP1DB .BP1TS .X'00000EF2' * * MODNAME DSNINXTP * * CONNECTION-ID=BATCH * * CORRELATION-ID=UPD1 * * LUW-ID=.... * * * * - DSNI011I -DB2A PAGE TEMPORARILY * * UNAVAILABLE TYPE 00000302 * * NAME BP1DB .BP1TS .X'000029D8' * * MODNAME DSNISMSU ERQUAL 0CA8 * * * * Corrupted data pages, overlaid with * * space map information, resulting in * * any of the following (not an exhaustive * * list): * * - Incorrect output, INCORROUT. * * - ABEND04E RC00C90101, RC00C90102, * * RC00C90105, or RC00C902xx in * * various CSECTs. * * - Data/index inconsistencies reported * * by the CHECK INDEX utility. * **************************************************************** * RECOMMENDATION: * **************************************************************** When DB2 restarts after a crash, or after a Restart Light, or after being shutdown with indoubt or postponed URs, or after being stopped with the CASTOUT(NO) option, the number of pages covered by a table space's space map page must be obtained from the pageset control log records. If DB2 was not running in V11 New Function Mode, the value for pages covered by a space map in extended mode is not available in the logs, and the restart code simply assumes (possibly incorrectly) that this value is the same as for the non-extended format. Once a pageset control block is populated with the incorrect value, it can persist indefinitely, even across another restart, and across migration into New Function Mode, as long as DB2 is never shut down cleanly with no outstanding URs or castouts. If the incorrect pages-per-spacemap value ends up being used on an object in extended format, whether it was already in extended format when the problematic log record was written, or whether it was converted later, the bad value may be used during log apply, resulting in either an inconsistent space map page, or in damaged data caused by treating a data page as if it were a space map page.
Problem conclusion
The DB2 restart code, which obtains a table space's attributes from the pageset control log records, has been modified to determine via calculation what the correct "pages per space map in extended mode" is, when it cannot be obtained from the logs. This includes log records written in V10 format (prior to V11 New Function Mode), as well as log records written in V11 NFM before this APAR was applied.
Temporary fix
********* * HIPER * *********
Comments
APAR Information
APAR number
PI50522
Reported component name
DB2 OS/390 & Z/
Reported component ID
5740XYR00
Reported release
B10
Status
CLOSED PER
PE
NoPE
HIPER
YesHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-10-13
Closed date
2015-11-12
Last modified date
2018-03-14
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI32924
Modules/Macros
DSNB1CHK DSNB1SSR DSNIRCSB
Fix information
Fixed component name
DB2 OS/390 & Z/
Fixed component ID
5740XYR00
Applicable component levels
RB10 PSY UI32924
UP15/12/01 P F511
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.0","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
14 March 2018