Tom,
A "container" can be a file or a device or a directory. Here again are examples that I already posted in
another thread:
In the first example there are 3 devices specified as containers. In the second example 3 directories are
specified as containers (DB2 therefore makes its own file names in it - and uses OIDs to do it I think). In
the third example 2 files are the 2 containers. In the fourth example 6 devices on 3 nodes are the
containers.
CREATE TABLESPACE PAYROLL MANAGED BY DATABASE USING (DEVICE'/dev/rhdisk6' 10000, DEVICE '/dev/rhdisk7'
10000, DEVICE '/dev/rhdisk8' 10000) OVERHEAD 24.1 TRANSFERRATE 0.9
CREATE TABLESPACE ACCOUNTING MANAGED BY SYSTEM USING ('d:\acc_tbsp', 'e:\acc_tbsp', 'f:\acc_tbsp')
EXTENTSIZE64 PREFETCHSIZE 32
CREATE TEMPORARY TABLESPACE TEMPSPACE2 MANAGED BY DATABASE USING (FILE '/tmp/tempspace2.f1' 50000,
FILE'/tmp/tempspace2.f2' 50000) EXTENTSIZE 256
CREATE TABLESPACE PLANS MANAGED BY DATABASE USING (DEVICE '/dev/rhdisk0' 10000, DEVICE '/dev/rn1hd01' 40000)
ONNODE 1 USING (DEVICE '/dev/rhdisk0' 10000, DEVICE '/dev/rn3hd03' 40000) ON NODE 3 USING (DEVICE
'/dev/rhdisk0'10000, DEVICE '/dev/rn5hd05' 40000) ON NODE 5
On Wed, 21 Jun 2000 23:03:03 -0400, Tom Lane wrote:
>"Randall Parker" <randall@nls.net> writes:
>> DB2 supports an ALTER TABLESPACE command that allows one to add new
>> containers to an existing tablespace. IMO, that's far more supportive
>> of 24x7 usage.
>
>Er, what do they mean by "container", and why is it better?
>
> regards, tom lane