DB2(z/OS) index utilized 100% full

Ken Ford

DB2(z/OS) index utilized 100% full

Hi All -

DB2 (z/OS) index is utilized 100% full, how ever it is at 10 extents, and the respective table space has enough space

do we need to alter index Primary, secondary ? if no whether there will be any impact to performance  of the queries accessing the columns in index.

 

please suggest me the best way to handle

 

Thank you

 

Roy Boxwell

DB2(z/OS) index utilized 100% full
(in response to Ken Ford)
I do not even begin to worry until over 200 extents are there! I also let Db2 size everything with its sliding scale so I only care about LDS shortage and partitions filling up.

Roy Boxwell
SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-
Heinrichstrasse 83-85
40239 Düsseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
http://www.seg.de

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert, Bettina Schubert

On 15 Nov 2017, at 20:14, Ken Ford <[login to unmask email]<mailto:[login to unmask email]>> wrote:


Hi All -

DB2 (z/OS) index is utilized 100% full, how ever it is at 10 extents, and the respective table space has enough space

do we need to alter index Primary, secondary ? if no whether there will be any impact to performance of the queries accessing the columns in index.



please suggest me the best way to handle



Thank you



-----End Original Message-----