hi all

db2 V 8 , regular tablespace 4k
in the above tablespace a table can grow upto 64gb
if i have one table in the tablespace and its reaching the limit of 64gb
---
i getting this error when i trying to increase the size of the containers
and tablespace total pages is reached 16777215.
SQL1139N The total size of the table space is too big.

Explanation:

The size of the current table space is too big. The size of a
REGULAR or USER TEMPORARY table space is limited to 0xFFFFFF
(16777215) pages while the size of a SYSTEM TEMPORARY or LONG
table space is limited to 2 terabytes (2 TB).

User Response:

Check the administration notification log for details. Reduce the
size of the table space and correct the SQL statement.

sqlcode : -1139

sqlstate : 54047

does a regular tablespaces have limit of 16million pages
kindly suggest
regds
Paul

its a DMS tablespace

yes DMS has the limit 4k 64gb size of tablespaces
regds
Paul

Looks correct. 16777215 * 4K = 63.99 GB. But should still be able to allocate one extra page to be exact 64GB, but the error is valid

I see you have answered your own question Those limitations are mentioned in the manual someplace, just in case you want to check on the other limitations

if we have 450 tables and if i want to create DMS tablespace
we can put tables according to transaction and lookup tables in one tablespace, how many tablespaces can we create according transaction and lookup for 450 tables. kindly suggest
regds
Paul

s many as you want.

but is there any best Practices, any example for 450 tables to spread accross the file system
regds
Paul

Do you have real disks underneath or is it a storage system that exposes virtual disks? In the latter case, you don't even know where the data ends up, so you just create the tablespaces you need and try to minimize administration efforts by lumping everything together as much as possible.

thanks stolze,
its a storage system, i will let you know once the physical structure is prepared like transaction tablespace, lookup tablespaces, 8k 4k tablepsace and indexe tablespace
regds
paul

As I said, I wouldn't worry about the tablespaces and where they reside. The page size is something you have to take care of, depending on the data. And you should design your buffer pools accordingly to separate data with different access patterns. Once you have the buffer pools and the assignment of tables to those buffer pools, the tablespaces are implicitly given (because a tablespace can map to a single buffer pool only).