Hi Mery:

I recommend you take care on this parameter of CREATE INDEX (PIECESIZE):

"
PIECESIZE integer

Specifies the maximum addressability of each piece (data set) for a nonpartitioning index. The subsequent
keyword K, M, or G, indicates the units of the value specified in integer.

K Indicates that the integer value is to be multiplied by 1 024 to specify the maximum piece size in bytes.
The integer must be a power of two between 256 and 67 108 864.

M Indicates that the integer value is to be multiplied by 1 048 576 to specify the maximum piece size in
bytes. The integer must be a power of two between 1 and 65 536.

G Indicates that the integer value is to be multiplied by 1 073 741 824 to specify the maximum piece size
in bytes. The integer must be a power of two between 1 and 64.


Table 34 shows the valid values for piece size, which depend on the size of the table space.

+--------------------------------------------------------------------+
¦ Table 34. Valid values of PIECESIZE clause ¦
+--------------------------------------------------------------------¦
¦ ¦ ¦ G ¦ ¦
¦ K units ¦ M units ¦ units ¦ Size attribute of table space ¦
+-----------+-----------+--------+-----------------------------------¦
¦ 254 K ¦ - ¦ - ¦ - ¦
¦ 512 K ¦ - ¦ - ¦ - ¦
¦ 1024 K ¦ 1 M ¦ - ¦ - ¦
¦ 2024 K ¦ 2 M ¦ - ¦ - ¦
¦ 4096 K ¦ 4 M ¦ - ¦ - ¦
¦ 8192 K ¦ 8 M ¦ - ¦ - ¦
¦ 16384 K ¦ 16 M ¦ - ¦ - ¦
¦ 32768 K ¦ 32 M ¦ - ¦ - ¦
¦ 65536 K ¦ 64 M ¦ - ¦ - ¦
¦ 131072 K ¦ 128 M ¦ - ¦ - ¦
¦ 262144 K ¦ 256 M ¦ - ¦ - ¦
¦ 524288 K ¦ 512 M ¦ - ¦ - ¦
¦ 1048576 K ¦ 1024 M ¦ 1 G ¦ - ¦
¦ 2097152 K ¦ 2048 M ¦ 2 G ¦ - ¦
¦ 4194304 K ¦ 4096 M ¦ 4 G ¦ LARGE, DSSIZE 4 G (or greater) ¦
¦ 8388608 K ¦ 8192 M ¦ 8 G ¦ DSSIZE 8 G (or greater) ¦
¦ 16777216 K¦ 16384 M ¦ 16 G ¦ DSSIZE 16 G (or greater) ¦
¦ 33554432 K¦ 32768 M ¦ 32 G ¦ DSSIZE 32 G (or greater) ¦
¦ 67108864 K¦ 65536 M ¦ 64 G ¦ DSSIZE 64 G ¦
+--------------------------------------------------------------------+

As only a specification of the maximum amount of data that a piece can hold and not the actual allocation of
storage, PIECESIZE has no effect on primary and secondary space allocation

The default for piece size is 2 G (2 GB) for indexes that are backed by table spaces that were created
without the LARGE or DSSIZE option, and 4 G (4 GB) for indexes that are backed by table spaces that were
created with the LARGE or DSSIZE option.

"

It is important when you define your INDEX. Also check the FREESPACE parameters (FREEPAGE
and PCTFREE) because can influence at time data set definition.

I hope this help.

Cheers
Ramiro López G.


-----Mensaje original-----
De: Mery Moreno
[mailto:db2udbdba-ezmlmshield-x70166934.[Email address protected]
Enviado el: Sábado 31 de Julio de 2004 5:47 PM
Para: LazyDBA Discussion
Asunto: extents


Gurus,
Can anyone have the kindness to explain me why when I increase the primary quantities and secondary quantities on a table space and indexes and apply a reorg on a table space and indexes the extents from the indexes quadruple the size? Please I need to reduce the extents for this table space ASAP. Please advise!

DB2 OS/390
vERSION 6.0

Thank you so much for all the help and advice!

Mery B. Moreno
Database Administrator - DBA
Lakeland Regional Medical Center
Phone: 863-687-1100 Ext 2830

BEGIN:VCARD
VERSION:2.1
X-GWTYPE:USER
FN:Moreno, Mery
ORG:;I.S.
EMAIL;WORK;PREF:Mery.[Email address protected]
N:Moreno;Mery
TITLE:DBA
END:VCARD



---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: db2udbdba-[Email address protected]



DB2 & UDB email list listserv db2-l LazyDBA home page