Add or resize containers?

[j***@gmail.com]

Hi.

I have the necessity to increase the size of my tablespaces, I have HP-UX, my tablespaces are DMS in raw device.

I want to know, wich it is the best option: add a new container(s) or resize my existing container(s)

Thanks.

[Mark A]

Post by j***@gmail.com
Hi.
I have the necessity to increase the size of my tablespaces, I have HP-UX,
my tablespaces are DMS in raw device.
I want to know, wich it is the best option: add a new container(s) or
resize my existing container(s)
Thanks.

If you add a new container, DB2 will rebalance the data across all the
containers, so that each holds approximately the same amount of data. This
is fine so long as you don't want to use the tablespace for awhile.

If you already have 2 or more containers in a tablespace, and you want to
increase the size, make sure you do both in the same SQL statement, or else
you will have a rebalance going on after you do the first one.

The optimal number of containers per tablespace cannot be answered from the
information you provided about your database and the tablespace (which was
practically zero).

[j***@gmail.com]

Thanks for your answer:

For example:

Tablespace X. total 33,554,432 KB USED 87.8 %
CONTEINERS:
/dev/vgX/rdata160 8,388,608 kb.
/dev/vgX/rdata161 8,388,608 kb.
/dev/vgX/rdata162 8,388,608 kb.
/dev/vgX/rdata163 8,388,608 kb.

Wich is the best option? add or resize containers?

[Willy Unger]

A big IT DEPENDS!

For example, if you are using discrete hard drives, adding new containers in different physical HDDs adds more DASD arms that can be brought to bear to scan the whole tablespace.

Then again, if all your queries are index probes, i.e., quintessencial transactions, I/O throughput for a single query is not that important.


Best Regards,

Willy Unger

DB2 Certified Specialist
***@yahoo.com