HELP: Import generates too many space allocation
Hi friends,
I'm migrating my database from 8i to 9i.
I made a blank 9i database and I'm using the IMP/EXP utility to export the information from 8i to 9i.
The problem is that the segments of the schemas's are growing a lot (200%), so a schema that allocates 50Mb in 8i, now allocates almost 100Mb in 9i.
I created the control file of the 9i database with a different value of the parameter MAXINSTANCES. Is it the reason of the increment
of the space?
I'm importing the information in two phases, using the commands:
imp system/manager file=mydump.dmp buffer=30000 commit=y full=y rows=y indexes=n constraints=n grants=n ignore=y log=import1.log
imp system/manager file=mydump.dmp buffer=30000 commit=y full=y rows=n indexes=y constraints=y grants=y ignore=y log=import2.log
Any help will be very appreciated. Thanks a lot for your answers.
;)
Re: HELP: Import generates too many space allocation
Quote:
Originally posted by Turin
I created the control file of the 9i database with a different value of the parameter MAXINSTANCES. Is it the reason of the increment
of the space?
No.
Quote:
I'm importing the information in two phases, using the commands:
imp system/manager file=mydump.dmp buffer=30000 commit=y full=y rows=y indexes=n constraints=n grants=n ignore=y log=import1.log
imp system/manager file=mydump.dmp buffer=30000 commit=y full=y rows=n indexes=y constraints=y grants=y ignore=y log=import2.log
Probably what's happening is a combination of differing minimum extent sizes and a "feature" of the export/import process. exp by default uses compress=y so that all your extents get compressed into one large extent. To bypass this "feature", use compress=n...