Another interesting subject we tested during the seminar was activating a physical standby database for test, reporting, etc.
Usually we are using storage snapshots for this purpose; we mount a storage generated copy of the production database on a report server, perform recovery and use it during the day. The process of resynchronizing the storage copy is repeated each night.
Using a physical standby for the same purpose is possible on 10g when flashback database is enabled on the standby. A guaranteed restore point is created to be able to re-activate and resynchronize the standby when the period of report/testing is over.
This is a powerful feature, worth knowing and using it.
You can find step by step implementation details on this document:
« MAA Seminar in Istanbul: Database Migration to ASM | Main | MAA Seminar in Istanbul: using Cross Platform Transportable Tablespaces into ASM »
MAA Seminar in Istanbul: Using a Physical Standby For Read/Write Testing and Reporting
TrackBack
TrackBack URL for this entry:
http://blogs.oracle.com/mte1521/mt-tb.cgi/4297
Search All Blogs
Google Search
About This Entry
This page contains a single entry from the blog posted on December 28, 2007 10:52 AM.
The previous post in this blog was MAA Seminar in Istanbul: Database Migration to ASM.
The next post in this blog is MAA Seminar in Istanbul: using Cross Platform Transportable Tablespaces into ASM.
Many more can be found on the main index page or by looking through the archives.
