multiple tablespaces containers on SAN

[paul]

Hi,
i want to know if this is better to split a tablespace into several
containers while the database are on san disk.
And how can i configure optimally the values for prefetch and extend ?

thx

[Lew]

I would say the answer is almost always yes. How you set it up exactly
depends on the way your logical disk volumes and file systems are
mapped to the backend storage packs. The values for prefetch and
extentsize are somewhat (but not entirely) related to how the data will
be accessed.

Lew

paul wrote:

Hi,
i want to know if this is better to split a tablespace into several
containers while the database are on san disk.
And how can i configure optimally the values for prefetch and extend ?

thx

[Ian]

paul wrote:

Hi,
i want to know if this is better to split a tablespace into several
containers while the database are on san disk.

Assuming you have DB2_PARALLEL_IO set properly (to enable DB2 to issue
multiple I/O requests to each container) then the answer is no.
Spreading your tablespace across multiple containers in the same
file system will result in I/O contention at the disk level.

Use 1 container per RAID array in the SAN device (note, multiple LUNs
may exist on a single RAID array, so make sure you understand the
mapping from file system -LUN -RAID array).

And how can i configure optimally the values for prefetch and extend ?

Extent size should be set to the strip size (or a multiple thereof) of
the RAID arrays in your SAN device. Prefetch should be set to ensure
that all disks are serving data for a prefetch request.

[paul]

hi
thanks for your comment, i'll check this with the san administrator

paul

"Ian" <ia*****@mobileaudio.comwrote in message
news:zG***************@newsfe08.phx...

paul wrote:

Hi,
i want to know if this is better to split a tablespace into several
containers while the database are on san disk.

Assuming you have DB2_PARALLEL_IO set properly (to enable DB2 to issue
multiple I/O requests to each container) then the answer is no.
Spreading your tablespace across multiple containers in the same
file system will result in I/O contention at the disk level.

Use 1 container per RAID array in the SAN device (note, multiple LUNs
may exist on a single RAID array, so make sure you understand the
mapping from file system -LUN -RAID array).

And how can i configure optimally the values for prefetch and extend ?

Extent size should be set to the strip size (or a multiple thereof) of
the RAID arrays in your SAN device. Prefetch should be set to ensure
that all disks are serving data for a prefetch request.

[mike]

Use 1 container per RAID array in the SAN device (note, multiple LUNs
may exist on a single RAID array, so make sure you understand the
mapping from file system -LUN -RAID array).

The DB2 publications continue to advise to use one container per
tablespace when using RAID devices.

Is that always the best advice ?

[Mark A]

"mike" <_l*****@yahoo.comwrote in message
news:11*********************@m73g2000cwd.googlegro ups.com...

>Use 1 container per RAID array in the SAN device (note, multiple LUNs
may exist on a single RAID array, so make sure you understand the
mapping from file system -LUN -RAID array).

The DB2 publications continue to advise to use one container per
tablespace when using RAID devices.

Is that always the best advice ?

Probably is the correct advise for most systems, depending on the throughout
of you RAID controller.

However, unless you have a data warehouse and are doing a lot of table
scans, it doesn't matter much, one way or the other. Check your buffer pool
hit ratio, and if it is above 95%, don't even worry about it.