Mainframe Blog

Exceptions in Db2 12

3 minute read
Stephen Watts
Status Code Status name Affected objects Corrective action(s)
ACHKP Auxiliary CHECK pending Base table space, LOB table space 1. Update or delete invalid LOBs and XML objects using SQL

2. Run CHECK DATA with appropriate SCOPE option to verify the validity of LOBs and XML objects

AUXW Auxiliary warning Base table space 1. One update or delete invalid LOBs and XML using SQL

2. If an orphan LOB or a version mismatch exists between the base table and the auxiliary index, use REPAIR to delete the LOB from the LOB table space

3. Check data to verify the validity of LOBs and XML objects

LOB table space 1. Update or delete invalid LOBs and XML using SQL

2. If an orphan LOB or a version mismatch exists between the base table and the auxiliary index, use REPAIR to delete the LOB from the Lob table space

3. Run CHECK LOB to verify the validity of the LOBs and XML objects

CHECKP CHECK

Pending

Table space, base table space Check and correct RI constraints using CHECK DATA

 

If a tablespace is in both REORG-pending and CHECK pending (or auxiliary CHECK-pending) status, run REORD first and then use CHECK DATA

Partitioning index, non-partitioning index, index on auxiliary table 1. Run CHECK INDEX on the index

2. If errors, run REBUILD INDEX

LOB table space Run CHECK LOB. If errors:

1. Correct defects found in the LOB table space with REPAIR

2. Run CHECK LOB again

COPY COPY

pending

Table space, table space partition Take an image copy (best action), use – START DATABASE(db) SPACENAM(ts) ACCESS FORCE, or run REPAIR and reset copy flag
DBETE Database

Exception table (DBET) error

Table space, partition, index, index partition, logical index partition Contact IBM support
GRECP Group buffer pool (GBP) recover pending Table space, index space, RECOVER the object, or use the START DATABASE command
ICOPY Informational COPY pending Partitioned index, non-partitioned index, index on auxiliary table Copy the affected index
NOT LOGGED table space Copy the affected table space
LPL Logical page list Table spaces, index space · START DATABASE ACCESS RA/W or R/O

· Run RECOVER or REBUILD INDEX utility

· Run LOAD REPLACE

· DROP the object

PRO Persistent Read Only Table space partitions
ARDBP Advisory REBUILD pending Index Run REBUILD on affected index
RBDP REBUILD pending Physical or logical index partition Run REBUILD or RECOVER on the affect index partition
RBDP* Logical partitions of non-partitioned secondary indexes Run REBUILD INDEX PART or RECOVER on the affected logical partitions
PSRBD Non-partitioned secondary index, index on auxiliary table Run REBUILD INDEX ALL, RECOVER or REBUILD INDEX
Note: The following actions also reset the REBUILD status.

 

· LOAD REPLACE with table space or partition

· REPAIR SET INDEX with NORBDPEND on index part (however this action doesn’t correct inconsistencies)

· Start database ACCESS FORCE (however this action doesn’t correct inconsistencies)

· REORG INDEX SORTDATA on the index

RECP RECOVER pending Table space Run the RECOVER utility on the affected object
Table space partition Recover the logical partition
Index on auxiliary table Run REBUILD INDEX, RECOVER INDEX, or REORG SORTDATA
Index space Run one of the following utilities on the affected index space:

 

· REBUILD INDEX

· RECOVER INDEX

· REORG INDEX SORTDATA

Any The following actions also reset the RECOVER status:

 

· LOAD REPLACE with table space or partition

· REPAIR SET TABLESPACE or INDEX with NORCVRPEND on index part (however this action doesn’t correct inconsistencies)

· Start database ACCESS FORCE (however this action doesn’t correct inconsistencies)

REFP Refresh pending Table space, index space Run a LOAD REPLACE. The object will also be in RECP or RBDP status and will need appropriate action taken
REORP REORG

pending

Table space Perform one of the following:

· LOAD REPLACE an entire table space

· REORG TABLESPACE SHRLEVEL NONE

· REORD TABLESPACE PART n:m SHRLEVEL NONE

· REORD TABLESPACE REFERENCE or CHANGE

Partitioned table space For rows <=32 K;

Run REORG TABLESPACE SHRLEVEL NONE SORTDATA

 

For rows > 32 K;

1. Run REORG TABLESPACE UNLOAD ONLY

2. Run LOAD TABLESPACE FORMAT UNLOAD

AREO* Advisory REORG Table space Run one of the following utilities:

 

· REORG TABLESPACE

· LOAD REPLACE

· REPAIR TABLESPACE

Index space Run one of the following utilities:

 

· REORG TABLESPACE

· LOAD REPLACE

· REORG INDEX

· REPAIR INDEX

AREOR Advisory REORG Table space Run one of the following utilities:

 

· REORG TABLESPACE

· REPAIR TABLESPACE

Index Space Run one of the following utilities:

 

· REORG TABLESPACE

· LOAD REPLACE

· REBUILD INDEX

· REPAIR INDEX

RESTP Restart pending Table space, partition, index space, physical index partition Objects are unavailable until back-out work is complete or until restart is canceled and a conditional restart or cold start is performed
STOPE Stop error Table space, index space RECOVER the tablespace or index space
WEPR Write error page range Page range in error Run a RECOVER utility on affected data

Disclaimer: This Db2® 12 for z/OS Reference Guide was developed to help users in their daily activities in administrating and programming in Db2 for z/OS. There are no guarantees expressed or implied with the contents in this guide. We want to provide a quality and useful reference for users. Please notify us of any mistakes or errors in this reference guide at blogs@bmc.com. Db2 is a registered trademark of the IBM Corporation.

Order Now! Get your free Db2 collateral from BMC!

Get your free Reference Guide and Catalog Tables Poster for z/OS from BMC. This collateral helps DB2 for z/OS users with daily activities in administering and programming for DB2 on z/OS.


These postings are my own and do not necessarily represent BMC's position, strategies, or opinion.

See an error or have a suggestion? Please let us know by emailing blogs@bmc.com.

BMC Bring the A-Game

From core to cloud to edge, BMC delivers the software and services that enable nearly 10,000 global customers, including 84% of the Forbes Global 100, to thrive in their ongoing evolution to an Autonomous Digital Enterprise.
Learn more about BMC ›

About the author

Stephen Watts

Stephen Watts (Birmingham, AL) has worked at the intersection of IT and marketing for BMC Software since 2012.

Stephen contributes to a variety of publications including CIO.com, Search Engine Journal, ITSM.Tools, IT Chronicles, DZone, and CompTIA.