Production z95 taking 2 gig more space than Test

• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
We ran new Keyword indexes on our Production v18 over the weekend. We removed an index (#060) called WSX. And, indeed, I see there are no values in the z98 for 060. Good, so far as that goes.

But I cannot account for the space used by the Z95 table. On the production server, where only 059 and not 060 have counts, the Z95 table is using 14GB of space. But on the test server, where *both* 059 and 060 show up, the Z95 table is taking up only 12GB of space. I don't understand how a definition in which *more* fields are included in the index uses *less* space in z95 than a definition in which fewer fields are defined.

Resolution:
util a/17/11/2 shows this on Test:

Enter Table/Index Name: z95
...
BYTES/1024 BLOCKS EXTENTS INITIAL_EXTENT NEXT_EXTENT
---------- ---------- ---------- -------------- -----------
12000000 1500000 6 1024000000 2048000000
Elapsed: 00:00:00.09

COUNT(*)
----------
2285470


And this on Production:

Enter Table/Index Name: z95
...
BYTES/1024 BLOCKS EXTENTS INITIAL_EXTENT NEXT_EXTENT
---------- ---------- ---------- -------------- -----------
14000000 1750000 7 1024000000 2048000000
Elapsed: 00:00:00.15

COUNT(*)
----------
2287164

There is one z95 record for each non-deleted bib record. The 1,694 (2287164 minus 2285470) additional non-deleted bib records on Production have pushed the number of z95 extents from 6 to 7 -- resulting in an additional 2 gig on Production.