Attention, Internet Explorer UserAnnouncement: Oracle Community has discontinued support for Internet Explorer 7 and below.In order to provide the best platform for continued innovation, Oracle Community no longer supports Internet Explorer 7.Oracle Community will not function with this version of Internet Explorer. Please consider upgrading to a more recent version of Internet Explorer, or trying another browser such as Firefox, Safari, or Google Chrome.(Please remember to honor your company's IT policies before installing new software!).
This note explains the procedure used to restore an Oracle Suggested Strategy incremental backup on another server. This is useful when we have to do periodic testing of disaster recovery procedures where we simulate a scenario when the complete database server has crashed and a new server has been provisioned.
I've been tasked with developing an Oracle 11g backup/restore strategy for some remote instances. RESTORE is not the most convenient command to fulfill you requirements (in this case you would need to temporarily set dbname= parameter on a new instance to be identical to the existing database, then restore all files to different names and then to perform a procedure to change database name and id - quite a difficult task).On 11g, the proper command intended to use in this situation is DUPLICATE DATABASE. The source that DUPLICATE use is either from backup (exactly as RESTORE does) or FROM ACTIVE DATABASE.