Re: Export- Import

You may want to Truncate your tables (with reuse storage option), Instead of Dropping those tables. If you keep on dropping your tables daily, It may lead to Tablespace Fragmentation.

        While Importing data from Production, You need to set IGNORE=Y ROWS=Y options.

        Exporting Data from Production database will lead to slow response for the  transactions on your Production database. You may want to Consider Exporting data once in a week.

-- 
Vijaya Kumar Vardhineni
Oracle DBA, EDS
Plano, TX



Venu Sripada <venu.sripada_at_citicorp.com> wrote in article
<32D56B6C.3761_at_citicorp.com>...


> 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.

>