Despite what your systems guy is saying, there is such thing as a physical disk (or volume). However, he's right that you should not be concerned with this. You should be thinking in logical volumes instead, which you see as separate devices but are in fact made of any number of physical volumes.
There is no need to bother yourself with multiple containers when working with striped volumes, which will be the case in your situation. You will still want to distribute different types of tablespaces to different logical volumes though: temporary spaces should reside on volumes separate from those containing data.
In brief the process should be something like this:
- determine the number and sizes of logical volumes that you will need; e.g. one for each data, LOB, or index tablespace; one for each temporary tablespace; one small volume for logs; one for archived logs and on-disk bakcups; etc.
- give this information to your systems guy, making sure that he understands which logical volumes must not share physical volumes, if you want maximum performance. There is no point in separating data and temp spaces if their logical volumes end up on the same physical disks. It is his task to make sure this does not happen;
- once the logical volumes are defined and mounted, create tablespaces with 1 container each (unless you hit the physical limit on the container size).
dBforums
>
Physical disk layout and DB2 containers. How to config?
03-06-08, 09:43
Linear Mode
