Re: How to shrink a database

From: Barry Roomberg <barry_roomberg_at_iacnet.com>
Date: 1995/04/18
Message-ID: <D78Goz.4I7_at_zcias2.ziff.com>#1/1


In article <D72qqn.HtE_at_nl.oracle.com>, cgohring_at_lucifer (Carl Gohringer) says:
>
>dherdman_at_osil.demon.co.uk (Dave G Herdman) writes:
>: We are tseting an Oracle 7 application from another company
>: with a view to buying it. The application was delivered as
>: a dump of all the database files. We have now cleared out
>: most of the rows we dont need and we want to shrink the
>: database down from about 4Gig to say 300 meg. We cannot
>: use the creation scripts as they are incomplete and have
>: not been updated for several years.
>:
>: Plan 1 was to build a database with everything scaled down
>: to about 25% or the original. Export everything from the old
>: database and then import it into the new database.
>:
>: This failed as some of the tables and indexes have storage
>: parameters with large initial allocations (300Meg)
>:
 

>Plan one is your best bet.
>
>However, before doing the export, just make sure that you alter the tables
>with the large storage defs.
>
>ie
>alter table <table_name> storage (initial xx next xx pctincrease xx maxtextents xx);
>
>These new storage defs will be exported with the table.
>
>--

Or you can use a hex editor to edit the create statements in the .dmp file for the correct sizes. Received on Tue Apr 18 1995 - 00:00:00 CEST

Original text of this message