Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> EXP/IMP - Different Space used
I am trying to migrate from Oracle 7.3.3 to Oracle 8.0.4 using full export
backup as system user. I have tried two option for taking the export backup
1) compress=y 2) compress=n.
To my surprise, on importing the export backup (with options compress=y and compress=n), the space utilisations for the tablespace containing indexes are different (I have different tablespace for data & index).
The following are after importing the export backup with compress=y SQL> select sum(bytes),tablespace_name from dba_free_space group by tablespace_name;
SUM(BYTES) TABLESPACE_NAME
---------- ------------------------------
291,823,616 INDEX_TAB ( Tablespace containing indexes)
610,803,712 DATA_TAB ( Tablespace containing data )
SQL> select sum(bytes),tablespace_name from dba_data_files group by tablespace_name;
SUM(BYTES) TABLESPACE_NAME
---------- ------------------------------
3221,225,472 INDEX_TAB
2147,483,648 DATA_TAB
The following are after importing the export backup with compress=n
select sum(bytes),tablespace_name from dba_free_space group by
tablespace_name
SQL> /
SUM(BYTES) TABLESPACE_NAME
---------- ------------------------------
1374,478,336 INDEX_TAB
610,803,712 DATA_TAB
SQL> select sum(bytes),tablespace_name from dba_data_files group by
tablespace_name;
SUM(BYTES) TABLESPACE_NAME
---------- ------------------------------
3221,225,472 INDEX_TAB
2147,483,648 DATA_TAB
The tablespace containing indexes is having only 291,823,616 bytes free on
importing the export backup with compress=y whereas
the tablespace containing indexes is having 1374,478,336 bytes free on
importing the export backup with compress=n.
Please note that the source database (from where export is taken) is also
showing 291,823,616 bytes free only.
Would appreciate, If you can expain the reason for different space utilisations.
Thanks in advance. Received on Fri Dec 25 1998 - 22:54:38 CST