Re: Export- Import

From: SChebr123 <schebr123_at_aol.com>
Date: 1997/01/11
Message-ID: <19970111031500.WAA03506@ladder01.news.aol.com>#1/1

Venu Sripada wrote:
>
> To Everyone: Please help
>
> We have an overnight process where by :
>
> 1.Full export ( Oracle EXP )of production database is produced on
> production machine.
> 2.Export file is rcp-ed to development machine.
> 3.All application tables on development database are droped.
> 4.All application tables are imported ( ORACLE IMP ) to development
> database from production export file.
> Thus, every day our developers have fresh data as of the end of previous
> business day.
> The problem we run into is that some tables fail to import due to
> unavailability of large contigious extents. We try to create these
> tables after having droped them specifying storage parameters like (
> initial and next sizes) . But problem occurs with another table.
>
> Our environment is:
> 1. Production machine: Sun Solaris 2.4 ; Oracle rel. 7.1.6
> 2. Development machine: Sun OS 4.1.3; Oracle rel. 7.1.6
>
> Is there better way to achive out goal of providing backup copy of
> prodn. data ( also the flexibility of refreshing individual tables)
>
> thanks in advance
>
> Venu
> Citibank.

Hello!

Export with 'Compress extents=Y' option will export the structure of Tables and Indexes with Initial Extent='total object storage' and Next extent= 'Half of the initial extent'.

If you import with 'Index file=xxxx' option, it creates a DDL in 'xxxx'. Check the DDL to understand Import.

There are number of ways you can import without getting into trouble:

Edit 'NEXT EXTENT' in the DDL as required, create all the objects, Import with ignore=Y option. OR
Import the structure with out data, ALTER TABLE/INDEX ....NEXT EXTENT size, then import data with ignore=Y option. OR
Instead of Dropping tables Truncate tables retain sizes, and Import data with ignore=Y option

GoodLuck
Samba. Received on Sat Jan 11 1997 - 00:00:00 CST