Recommendations for maintaining Prod support DB [message #293726] |
Mon, 14 January 2008 14:53 |
jssc
Messages: 1 Registered: January 2008 Location: Irvine, CA
|
Junior Member |
|
|
Recommendations for maintaining Production Support DB
I'm investigating available methods for maintaining a production support DB. It needs to contain all production data, kept current or refreshed nightly. It will only be used when we need to determine the resolution for a (rare) production data issue. However, when we have issues, we may have them a couple days in a row, so the time required to re-sync the DB after using for production support is important.
The DB is currently 400GB and growing. There seems to be several techniques that may be used, any comments/suggestions would be appreciated.
1) setup a Data Guard standby database. If needed to investigate an issue,would we be able to disable DG replication with no impact to the production side? After the issue was resolved, what steps would be needed to resume data guard (assume we had to modify some data)
2) Use Oracle streams to maintain current data in the PS DB. Could we 'pause' the streaming replication while researching an issue? After the issue was resolved, what steps would be needed to resume the replication?
3) I've had very little exposure to RMAN. Does it have features that I might take advantage of for this purpose?
4) any other tecniques?
|
|
|
|
|
|