DataPump Schema [message #608538] |
Thu, 20 February 2014 13:36 |
|
aislanluiz
Messages: 8 Registered: February 2014
|
Junior Member |
|
|
Hi,
Is it normal that the duplicated schema is about half size that the original?
I got only 12 same errors:
ORA-39083: Object type OBJECT_GRANT failed to create with error:
ORA-01749: you may not GRANT/REVOKE privileges to/from yourself
The size:
Tablespace----%Used----Alocated----Used----Free--------Datafiles
xxx_DATA------59,35-----28642,25-----16998------11644,25-----9
xxx_INDEX-----70,39-----20765-------14616-------6149--------7
yyy_DATA------84,05-----11320-------9514,75-----1805,25-----1
yyy_INDEX-----58,32-----10000-------5832,19-----4167,81-----1
The commands:
expdp xxx/xxx@xxx schemas=xxx directory=expdir dumpfile=xxx.dmp logfile=xxx.log
impdp yyy/yyy@yyy schemas=xxx directory=expdir dumpfile=xxx.dmp logfile=yyy.log remap_schema=xxx:yyy remap_tablespace=xxx_index:yyy_index remap_tablespace=xxx_data:yyy_data TABLE_EXISTS_ACTION=replace
|
|
|
|
|
|
|
|
Re: DataPump Schema [message #608547 is a reply to message #608546] |
Thu, 20 February 2014 14:29 |
|
BlackSwan
Messages: 26766 Registered: January 2009 Location: SoCal
|
Senior Member |
|
|
>Is there a "vacuum full" in oracle?
push back from the keyboard & consider the bigger picture.
The most common scenario when a large disparity exists between allocated & used is that periodically old data has been removed from the table.
If/when ZERO free space exists within a table & more rows need to be added to the table, then Oracle must incur the overhead to add more space to the table.
If you force the free space towards ZERO, then Oracle must expend extra resources to grow the table as new rows get added.
If you leave the free space alone & do nothing, then Oracle will REUSE the free space as new rows get added.
You are treating the table like an accordion; always expanding & contracting. The net results is wasted resource consumption.
|
|
|