with Tags:
directory
X
X
APARs for excessive SPT01/DBD01 growth – Base and LOB tablespaces - including related Utility APARs
Customers running with DB2 10 NFM have noticed that table spaces associated with the DB2 directory data base or catalog (DSNDB01 and SPT01) experience significant space growth resulting from BIND/REBIND operations, DDL, utility activity (Reorg). The only way customer could sustain the issue was by frequently scheduling reorgs on the DB2 directory and catalog in DB2 10 NFM. Updated list of APARs for excessive SPT01/DBD01 growth – Base and LOB tablespaces - including related Utility APARs in this area! DB2 10 NFM Cat/Dir SPT01/DBD01 excessive growth APAR PM66874 to resolve: LOB integrity abend during REORG of DBD01. DB2 10 NFM Cat/Dir SPT01/DBD01 excessive growth related APAR PM68842 to resolve: REORG abend. Broken aux index. Tags: growth nfm db2 directory space 10 catalog and |
REORG of the Directory
If you want to REORG a LOB tablespace then you can just REORG that LOB tablespace. You want to run REORG of the base tablespace using AUX YES. This will work fine, but if you're doing this against a compressed SPT01 then make sure you do not also specify KEEPDICTIONARY until you have the fix on for PM67696.
Also you want to make sure you have PM66874 applied, when running the REORG. Before you go ahead with the REORGs, we discussed that you would validate that there isn't any dormant corruption that REORG could trip over. To do that, I recommend you run the following: CHECK LOB SHRLEVEL CHANGE CHECK INDEX SHRLEVEL CHANGE on the aux index CHECK DATA SHRLEVEL CHANGE on the base tablespace using SCOPE AUXONLY AUXERROR REPORT. Tags: directory catalog |
Growth in DB2 10 Catalog and Directory LOB ObjectsOpen APAR PM64226 describes an issue where catalog and directory LOB objects can grow considerably when a long READ claim is held on the object. The APAR refers specifically to DSNDB01.SYSDBDXA but goes on to say the problem can occur for other catalog and directory objects. You should track this APAR if you are already at DB2 10 NFM or are planning to move to NFM in the near to medium future. The problem applies to both data sharing and non-data sharing systems, so all customers need to be vigilant. PM64226 was open at the time of writing (27 June 2012)
Tags: directory catalog lob |
