11-17-2002 09:37 PM
11-18-2002 03:16 AM
Are you running Oracle on an MPEiX server? Or on a Windows or UNIX platforms? If the latter, then you are in the wrong room; please call Oracle for assistance.
02-06-2005 02:09 AM
You could use destroy=Y when using imp but more elegant would be to drop the tables and indexes on it before import them.
After imp you recreate the indexes.
It is faster this way.
04-30-2007 04:54 AM
04-30-2007 06:11 AM
So it is how truncate is used that determines what may or may not happen to space, in itself truncate is not a space saver.
The point on moving the HWM to the initial block is true and would greatly speed up subsequent inserts as the process no longer needs to check blocks for space to insert as all blocks would be free until populated, by which time they would be removed from the free list. So in that scenario a truncate could speed the subsequent import.
Personally, if Oracle 'imp' could not meet my needs then I would not obtain my data using Oracle 'exp' - I would write a table unload to produce an OS file and then use sql*ldr to read it in - that oracle product has far more appropriate functionality in the load control, including overwriting table data.