Re: LMT and Siebel/Peoplesoft?

Vikas Agnihotri wrote:
>
> "Daniel A. Morgan" <damorgan_at_exesolutions.com> wrote in message news:<3C4B368E.8988E9E5_at_exesolutions.com>...
> > Don't use one tablespace size. Create three or four for data and three or four for indexes. For example
> >
> > data_sml 256K
> > data_med 2.5M
> > data_lrg 25M
> > data_ext 250M
>
> Thats what I wanted to do as well, but unfortunately, the Siebel
> install/upgrade process doesnt allow you to specify the tablespace
> with that degree of control.
>
> It just asks you for a data tablespace and a index tablespace. Then it
> proceeds to create all the objects with (I think) no STORAGE clause in
> its CREATE statements. For objects with a high growth rate, it uses
> the old PCTINCREASE concept, which Oracle would ignore anyway for a
> LMT.
>
> Thanks for the ideas.

The Siebel import allows for this - the control file for the import (???.dat) needs to have it nominated for the relevant objects.

hth
connor

-- 
==============================
Connor McDonald

http://www.oracledba.co.uk

"Some days you're the pigeon, some days you're the statue..."