Re: Migrating Oracle 7.3.3 to Oracle 8.0.4

Well, I tend to design and build all my datawarehouses via Oracle Designer 2000, which includes good facilities for defining object-level storage parameters. In other words, I'd be pretty upset if you destroyed most of my hard work with a compress=y.

If the database you are moving is well designed and not heavily fragmented, then I suggest use compress=n (I always use this). If you've a bit of fragmentation on certain objects, you can always put that right afterwards.

If you're db is in a bit of a mess and woud benefit from the compress=y, then I guess you could use it. But that's not a very good fix for a longer term problem, IMHO.

MotoX.

On 19 Dec 1998 09:36:08 GMT, "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
>
Received on Sat Dec 19 1998 - 09:20:21 CST