Hello,

I find the secondary extent allocation for a partitioned tablespace was varying randomly when I did a LISTCAT on one of the partition dataset. Similar to the one below

TRACKS--------------1095

TRACKS---------------330

TRACKS--------------1575

TRACKS--------------1065

TRACKS---------------435

TRACKS---------------765

TRACKS---------------600

TRACKS---------------135

TRACKS---------------450

TRACKS---------------435

The DB2 version is V8 on compatibility mode. The secondary quantity for this partition is 720 KB in DDL for the tablespace.

The issue is, the data load was tested in TEST system and went fine (where the secondary extents varied randomly as shown above) but failed in production where maximum number of extents reached.Also the secondary quantity for the partition was 720 KB similar to test.

What could be the reason behind taking random size for secondary extent?

Will z parm MGEXTSZ=YES play a role with DB2 V8 compatibility mode?

In that case MGEXTSZ=YES is set both in Test and Prod the same way?

Could you please help me in diagnosing the issue?

One more information to add,the DB2 is running on mainframe.

Thanks
Aravinth