methods for optimizing tablespace files ?

  In creating a brand new database, the syntax for 'create tablespace' allows for the specification of the datafiles.

  Before using LVM (Logical Volume Manager) we specify datafiles in such a way that they spread over physical discs, buses and IO backplanes. The goal is to spread the load to over several physical resources and avoid congestion.

  We used to say
datafile '/..../dsk001/file1' size xxx

'/..../dsk004/file2' size yyy

  and we know we have "striped" our tablespace across several disks, buses & backplanes.

  With the advent of LVM, the above assignment actually refers to some files contained in some logical volumes.
datafile '/..../lv001/file1' size xxx

'/..../lv004/file2' size yyy

  LVM manages physical media, thus you are not sure that file1 and file2 are on different physical disks/bus/backplane. This approach is not anymore correct, although LVM does its best to stripe.

  What other methods are people using to optimize their systems ? Received on Tue Aug 27 1996 - 00:00:00 CEST