PRR3022E - Tablespace Tablespace.Name Pages Exceed Dataset Max

book

Article ID: 6164

calendar_today

Updated On:

Products

CA Database Analyzer for DB2 for z/OS CA Fast Unload for DB2 for z/OS CA Fast Check for DB2 for z/OS CA Fast Index for DB2 for z/OS CA Fast Load for DB2 for z/OS CA Rapid Reorg for DB2 for z/OS

Issue/Introduction

Running a CA Rapid Reorg utility against a segmented Tablespace, the job fails due to errors:

PRR3022E - Tablespace Tablespace.Name Pages Exceed Dataset Max

PRR2267I - Tablespace Tablespace.Name Elapsed..01:29:29.22 Task Time

PRR2267I - Tablespace Tablespace.Name CPU......00:02:39.71 Task Time

PRR0091E - Tablespace Tablespace.Name

           Application Abended when UNLOADing the Tablespace

           Task ECB: X'00000000' Return Code: X'00000008'

           Detected in module RRA$ULA

 

Cause

PRR3022E message is saying that there is no more space in the data set. The max is 4 GB, so probably the data set is at 4 GB and cannot be reorg. 

Environment

DB2 Tools R18.0 DB2 V10.0

Resolution

As a workaround when we need to finish the reorg, we could try the following options after executing a LISTCAT to check there could be enough space available:

 try using EXTENDED-TSREORG NO

 (the original reorg was with EXTENDED-TSREORG YES)  EXTENDED-TSREORG NO calculates the space available in another way. 

 or

 try setting  FREEPAGE 0 PCTFREE 0

 On this way we will get more space and we can complete this particular reorg, but we have to convert the Tablespace greater than 4 GB anyway. 

 

Additional Information

The above could be a valid workarounds when we need to finish the reorg. 

The best solution probably should be to convert to PBG or increase the Tablespace greater than 4 GB. For a Tablespace greater than 4 GB it has to be SMS managed.