Hello,
First, DB2 for z/OS does not store table and index data within the same
dataset (file)! It allocates at least one new file for each index you
create.
Second, and the VSAM "file system" used by DB2 for z/OS does not extend
files infinitely until all available disk space is used. Therefore, you must
specify a "primary" (initial) and "secondary" (increment) size for each
table-and indexspace by specifying the PRIQTY <kB> and SECQTY <kB> keywords
within your CREATE INDEX - Statement. If you omit this keywords, DB2 uses a
very small default of 48kB for both, which is obviously not applicable for
your table .
Cheers - Walter.
"Michal Krawczyk" <ca*******@poczta.onet.pl> schrieb im Newsbeitrag
news:cj**********@flis.man.torun.pl...
J have tablespace named TSPACE, with table DATA with about 3mln rows.
I want to create index named O123TA, but execution ends with error:
DSNT408I SQLCODE = -904, ERROR: UNSUCCESSFUL EXECUTION CAUSED BY
AN UNAVAILABLE RESOURCE. REASON 00D70014, TYPE OF RESOURCE
00000220, AND RESOURCE NAME
DBIV71.DSNDBC.USPLPPL.O123TA.I0001.A001
I think, there is problem with free space, so i increased by tablespace
quadruply, but it has changed nothing.
Where is problem?
Michal
