Recovery senario
=====================
Think Database is having having backup copy which is not valid and DG/DR is there which is not in sync with production database.
Around 10 to 15 datafiles located in perticular vg/mount point is corrupted due to hardware error.
How to handle this senario ?
Solution
===========
1. If Database is not having any nologging objects try to sync up DG by applying all archive logfiles and carryout switch over process and start using DG as production database.
2. IF Database is having nologging objects i.e index try to sync up DG by applying all archive logfiles and carryout switch over process and start using DG as production database. After switch over recreate all indexes will fix issue.
3. Else copy Datafiles from DG/DR to production database and start recovery will also help to recover database. In this methode if objects are loaded with nologging option will loose data.
Hence before building DG enable forced login in all critical database which will helps all recovery senarios.
Wednesday, June 23, 2010
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment