Re: Migrating Oracle 7.3.3 to Oracle 8.0.4

From: <ashok_b_at_hotmail.com>
Date: Mon, 21 Dec 1998 16:35:59 GMT
Message-ID: <75ltdg$b7p$1@nnrp1.dejanews.com>

The COMPRESS parameter does the following: If COMPRESS = N, the current table storage clause remains intact, but if COMPRESS=Y, the storage clause is altered to reflect one extent, the sum of all the tables extents, whatever its size.

Ashok

In article <01be2b33$a0bcb240$b8b915a5_at_oempre-install>, "Sanjay Hans" <sanhans_at_mbox5.singnet.com.sg> wrote:
> I am planning to do the migration from Oracle 7.3.3 on DEC unix to Oracle
> 8.0.4 on NT 4.0. I will be taking full export backup as 'system' user
> from oracle 7.3.3 and import it into oracle 8.0.4 after creating the
> required tablespaces/rollback segments.
>
> I am not sure for taking the full export backup from oracle 7.3.3, whether
> I should set the parameter COMPRESS=Y or N. We are using the Oracle
> database as a datawarehouse. I have found that for some tables in Oracle
> 7.3.3 the initial extent is around 76 MB and next extent is around 70 MB,
> if I use the option COMPRESS=Y, it results in the initial extent size of
> around 320 MB for these tables. What is the implication of this parameter?
> Whether I should use COMPRESS=Y or N for doing the migration.
>
> Thanks in advance for your help/suggestions
>
>

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Mon Dec 21 1998 - 10:35:59 CST