>
> On Tue, 25 Jan 2000, Paul Krier wrote:
>
> > I have a test environment that I want to refresh with
> > data from my production environment every weekend.
> > I have been attempting to export production, truncate test tables,
> > import production to test, but the import takes 30 hours. Most of
> > the data being exported/imported is static, so I was considering
> > using incremental export/import to speed this up. I am running
> > Oracle 8.0.5 on HP-UX 10.20.
> >
> > Is anyone doing something like this? There must be an quicker, easier
> > way to refresh test data.
> >
> > Thank you.
> > Paul Krier
> > Sr. Programmer/Analyst
> > Industrial Electric Wire & Cable
> > (262) 957-1143
> > paulk@iewc.com
> Paul,
>
> There are a few things you can do. If you want to focus only on using
> import, look at the following:
>
> 1) are you using "commit=y"? If not you may be slowed down by relying on
> long rollback segment processing.
> 2) is your buffer size appropriate ("BUFFER= xxx")? This can have a big
> impact on import performance
> 3) Consider disabling triggers, constraints, and dropping indexes on
> your tables before the import. Then enable + recreate them after the
> load.
> 4) Break the export into multiple streams. For example, have five export
> scripts to export five different users (or large tables). Then import
> them in parallel. This works very well for me.
>
> The incremental exports/imports don't always work as you would like. For
> example, if one record in a ten-million record table changes, then the
> entire ten-million record table is exported.
>
> The other option is to use snapshots on test pointing to production. Only
> updated data would be copied to test. This works best if the tables are
> read-only. Otherwise you can use Oracle's advanced replication to get your
> desired effects faster than export/import.
>
> Best regards,
>
> -Ari Kaplan
> 350+ Oracle Tips: www.arikaplan.com
> -----------------------------------------------------------------------
> >
Back to Ari Kaplan's Home Page