Best Practices For Managing Backups In A Streams Environment

作者: Maclean Liu , post on September 30th, 2007 , English Version
【本站文章除注明转载外，均为本站原创编译】
转载请注明：文章转载自: Oracle Clinic – Maclean Liu的个人技术博客 [http://www.oracledatabase12g.com/]
本文标题: Best Practices For Managing Backups In A Streams Environment
本文永久地址: http://www.oracledatabase12g.com/archives/best-practices-for-managing-backups-in-a-streams-environment.html

Best Practices for Managing Backups in a Streams Environment 1. Ensure that any manual backup procedures that include the any of the following: statements include a non-null Streams tag: ALTER TABLESPACE ... BEGIN BACKUP ALTER TABLESPACE ... END BACKUP The tag should be chosen such that these DDL commands will be ignored by the capture rule set. Backups performed using RMAN do not need to set a Streams tag. To set a streams tag, use the DBMS_STREAMS.SET_TAG procedure. A non-null tag should be specified to avoid capturing these commands. 2. Force a checkpoint (logminer) before beginning the manual backup procedures. To force a checkpoint, explicitly reset the hidden capture parameter _CHECKPOINT_FORCE to Y. 3. Ensure that all archive logs (from all threads) are available. Database recovery depends on the availability of these logs, and a missing log will result in incomplete recovery. 4. Do not allow any automated backup of the archived logs to remove necessary archive logs. It is especially important in a Streams environment that all necessary archivedlogs remain available online and in the expected location until the capture process has finished processing them. If a log required by the capture process is unavailable, the capture process will abort. A procedure to determine the minimum archive log necessary for successful capture restart is available in the Streams health check script.note:273674.1 5. Ensure that the APPLY process parameter, COMMIT_SERIALIZATION, is set to the default value, FULL. 6. In 9i implement a "heartbeat" table. To ensure that the applied_scn of the DBA_CAPTURE view is updated periodically, implement a "heart beat" table. Implementing a heartbeat table ensures that the metadata is updated frequently. Additionally, the heartbeat table provides quick feedback as to the health of the streams replication. In 10g this is automated and if apply cannot cope with applying of LCrs then capture status changes to PAUSED FOR FLOW CONTROL. note.746247.1 7. In situations that result in incomplete recovery at the destination site, follow the instructions in Chapter 16 of the Streams manual "Performing Database Point-in-Time Recovery on a Destination Database

Oracle Clinic – Maclean Liu的个人技术博客

Best Practices For Managing Backups In A Streams Environment

Applies to:

Purpose

Scope and Application