SQL1139n The total size of the table space is too big.

Question

Hi
Our R3 QA system runs on Solaris 10, using DB6 822.
We have now run into a problem, where we cannot extend a table. It is 66GB in size. Because the page file size is 8 kb, the limit is apparently 64 GB (we got it to 66GB).
It seems we will have to increase the page file size to get past the problem, say 16k or 32k. The question is how?
So far we have a framework in mind:
Create new table
Copy old table into new table
Drop old table
Recreate old table with bigger page file size
Copy new table into old table (now this new /old is getting confusing..)
Bob's you aunty, or something of that effect...
Is the thinking correct? If it is I will need much more detail, as I am not too familiar with DB2.
Thanks in advance!

Answer 1

hi derik,
the db6-specific limits for max tablespace/table size are
64/128/256/512GB for 4/8/16/32KB pagesize.
for problems like "tablespace/table reaches its pagesize dependent max. size",
we (DB6 porting team of SAP) have developed a special tool/ABAP report called 'DB6CONV'.
DB6CONV takes care of everything concerning a table conversion.
it is in depth described in OSS note 362325. the report itself it delivered by means of a transport, which is attached to note 362325 and/or can be downloaded via sapmats.
in your case you have to
a) get the latest DB6CONV transport and import it into your system
b) create a new tablespace with a pagesize >8k
c) assign a new data class for this tbsp in tables TADB6 (for data tbsp) and/or IADB6 (for index/tbsp)
d) run DB6CONV from transaction SE38 as described in note 362325
to convert(transfer) the table that is at/near the size limit
by specifying either target tablespaces or target data class
e) DB6CONV will duplicate the table first into the new tablespace, then copy the data into the newly created table. this can be done either 'offline' (fastes way, but table is not accessible during the conversion) or 'online' (slow, but table is accessible the whole time - despite a short time period when the switch from original to target table is performed)
please make yourself familiar with the tool and the documentation.
and feel free to ask if you need more information or have additional questions/remarks.
regards, frank