Re: initial value on create table/index statement
Date: Mon, 29 Jun 2009 06:32:45 -0700 (PDT)
On Jun 26, 5:52 pm, DEV <sdp..._at_gmail.com> wrote:
> On Jun 26, 2:46 pm, DEV <sdp..._at_gmail.com> wrote:
> > On Jun 26, 2:25 pm, John Hurley <johnbhur..._at_sbcglobal.net> wrote:
> > > On Jun 26, 5:18 pm, DEV <sdp..._at_gmail.com> wrote:
> > > > Is there a way to change the value of "inital" in "create table" or
> > > > "create index" during imp? Pre-creating table is not an option here.
> > > > I am taking a export dump with rows=n from production and importing it
> > > > into dev/QA and since the production tables/indexes have larger values
> > > > for "inital", it takes a lot of storage. Is there a way to create
> > > > tables/indexes with smaller inital values during import?
> > > > Thanks,
> > > > Dev
> > > What oracle versions are you going to/from in the export/import
> > > process?
> > > How are the relevant tablespaces defined in the to/from process?
> > Both are on same version (10.2.0.3) and defined the same way.
> > EXTENT MANAGEMENT LOCAL AUTOALLOCATE
> > BLOCKSIZE 8K
> > SEGMENT SPACE MANAGEMENT AUTO
> Sorry for the upper case on my last post. I wasn't shouting. It was
> due to copy/paste...- Hide quoted text -
> - Show quoted text -
You might consider just performing alter table move and alter index rebuild commands on the empty tables after the import. You can reset the initial extent allocation value on moves and rebuilds. The commands are easy to generate. As long as you have enough space to handle the initial allocation this should work.
Then I would notify the exporter that on all future exports you want compress=n set.
HTH -- Mark D Powell -- Received on Mon Jun 29 2009 - 08:32:45 CDT