I'd then be extremely tempted to do the export and then recreate your
tablespaces with a default storage clause including PCTINCREASE 0. Then
precreate all your objects without overriding the tablespace storage clause.
That way you will get a bunch of tables in the tablespace that will most
likely always be able to extend. Your only problems will come if the app is
in the habit of creating (and dropping) tables with actual storage clauses.
You'll have to do import with ignore=y if you take this route (since the
objects will exist).
As I say painful.
--
Niall Litchfield
Oracle DBA
Audit Commission UK
*****************************************
Please include version and platform
and SQL where applicable
It makes life easier and increases the
likelihood of a good answer
******************************************
"Vince Laurent" <vlaurent_at_NOSPAMPLEASE.networkusa.net> wrote in message
news:kdo6buomc1r0msej4r8t8rueog71eleqfc_at_4ax.com...
> Thanks.... this is what I have been hearing. BTW, we are on 8.0.6.3
> (going to 8.1.7. later this year).
>
>
> On Tue, 9 Apr 2002 15:33:19 +0100, "Niall Litchfield"
> <n-litchfield_at_audit-commission.gov.uk> wrote:
>
> >export/import.
> >
> >You might be able to avoid the pain in future by use of locally managed
> >tablespaces but that is a version specific feature.
>
Received on Wed Apr 10 2002 - 03:49:05 CDT
