RE: Question On Data Guard And Database Refreshes
- From: Scott Canaan <srcdco@xxxxxxx>
- To: Justin Mungal <justin@xxxxxxx>
- Date: Fri, 06 Jun 2014 19:28:40 +0000
How do you deal with data changes in production during the data pump import?
It seems that data could get out of sync.
Scott Canaan ’88 (srcdco@xxxxxxx<mailto:srcdco@xxxxxxx>)
(585) 475-7886 – work (585) 339-8659 – cell
“Life is like a sewer, what you get out of it depends on what you put into it.”
– Tom Lehrer
From: Justin Mungal [mailto:justin@xxxxxxx]
Sent: Friday, June 06, 2014 3:02 PM
To: Scott Canaan
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Question On Data Guard And Database Refreshes
Sounds fine to me, just keep an eye on how many archive logs the import
generates. You can make the process quicker if there are only certain schemas
that need to be refreshed. I use Data Pump to do refreshes this way as well.
The process on the dev system I follow is pretty simple: record the password
hash, drop the schema(s), run the import, reset the password hashes if needed,
and update stats. You may want to log out of any production systems before
dropping schemas. :)
On Fri, Jun 6, 2014 at 12:34 PM, Scott Canaan
<srcdco@xxxxxxx<mailto:srcdco@xxxxxxx>> wrote:
We have dived into the world of Data Guard and have it working nicely.
Periodically, we get requests to refresh a test database from production to get
“up-to-date” data in test. If both production and test are Data Guarded, what
is the best way to do the refresh? We would like to not to have to rebuild the
test secondary database if at all possible. We don’t use RMAN for backups. We
are looking at using Data Pump between production and test and letting Data
Guard update the secondary from there.
Is there a better way, without purchasing a tool?
We are using Oracle 11.2.0.3 on Red Hat Linux.
Thank you,
Scott Canaan ’88 (srcdco@xxxxxxx<mailto:srcdco@xxxxxxx>)
(585) 475-7886<tel:%28585%29%20475-7886> – work (585)
339-8659<tel:%28585%29%20339-8659> – cell
“Life is like a sewer, what you get out of it depends on what you put into it.”
– Tom Lehrer
Other related posts:
