A fairly standard strategy when the bulk of the database is in time-based
partitions - which seems possible in your case - is to have time-related
tablespaces and make "older" tablespaces read-only as soon as the data they
contain stops changing. Then you can use transportable tablespaces to get the
old tablespaces to the test system as a one-off exercise and only use a
backup/recover type of strategy for the most recent data.
Regards
Jonathan Lewis
________________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on behalf
of Sanjay Mishra <dmarc-noreply@xxxxxxxxxxxxx>
Sent: 24 February 2020 22:14
To: Oracle-L Freelists
Subject: VLDB Refresh
Do we have any better way to refresh Test with Production when the database is
very big like close to 100Tb? The requirement is not the timing which anyway
using Tape backup will take day or more based on Tape library But looking for
the following points
1. Only One Application Schema in the database using Bigfile Tablespace
2. Contains multiple Table with LOBs Partitioned
3. All Big tables are monthly Partitioned with 2 years of Data in all
So now looking to refresh Test with only last 3-6 months of data using a
monthly partition. It cannot use Datapump not only due to several Terabytes but
also cannot put any load on the critical Production environment. Does Oracle
provide such features using any backup technologies including Oracle ZDLRA or
any new features that can help to not only refresh the Test environment but
also take lesser storage?
TIA
Sanjay
--
//www.freelists.org/webpage/oracle-l
