Setting up DR Site with Oracle Dataguard


Overview :

This course will help you plan and implement a Disaster Recovery strategy for your Oracle database.

It concentrates on the deployment of Oracle Data Guard which is Oracle’s Disaster Recovery product
that is included in Oracle RDBMS Server Enterprise edition.

Objectives:

Understand the need for Disaster Recovery(DR) and problems,methods involved in implementing it.

Learn how to plan to implement Oracle Data Guard and the steps involved in that implementation.

Understand the administrative requirements of a Data Guard implementation.

Learn how to do a switchover/failover from the primary site to the standby site and how to reinstate your DR configuration after this event.

Implement Data Guard so that the Standby Database can be used for alternative purposes such as read only applications

We will be give you practical experience to configure the following Real Time Scenarios

1-> Physical Standby Database
2-> Logical Standby Database
3-> Log Transport Services
4-> Log Apply Services
5-> Role Management
6-> Managing a Physical Standby Database
7-> Managing a Logical Standby Database

Duration :-

2 Days (16 Hours)

Details of the Topics Covered :-

1->     Physical Standby Database
         
    1.1 Preparing the Primary Database for Standby Database Creation
        1.1.1 Enable Forced Logging
        1.1.2 Create a Password File
        1.1.3 Setting Primary Database Initialization Parameters
        1.1.4 Enable Archiving
 
    1.2 Creating a Physical Standby Database

        1.2.1 Create a Backup Copy of the Primary Database Datafiles
        1.2.2 Create a Control File for the Standby Database
        1.2.3 Prepare an Initialization Parameter File for the Standby Database
        1.2.4 Copy Files from the Primary System to the Standby System
        1.2.5 Set Up the Environment to Support the Standby Database
        1.2.6 Start the Physical Standby Database
        1.2.7 Verify the Physical Standby Database Is Performing Properly

2->      Logical Standby Database

    2.1 Preparing for Logical Standby Database Creation

        2.1.1 Determine Support for Datatypes and Storage Attributes for Tables
        2.1.2 Ensure Table Rows in the Primary Database Can Be Uniquely Identified

    2.2 Creating a Logical Standby Database

        2.2.1 Create a Physical Standby Database
        2.2.2 Prepare the Primary Database to Support a Logical Standby Database
        2.2.3 Prepare to Transition to a Logical Standby Database
        2.2.4 Start the Logical Standby Database
        2.2.5 Verify the Logical Standby Database Is Performing Properly


3->     Log Transport Services


    3.1 Where to Send Redo Data

        3.1.1 Destination Types
        3.1.2 Configuring Destinations with the LOG_ARCHIVE_DEST_n Parameter

    3.2 How to Send Redo Data

        3.2.1 Using Archiver Processes (ARCn) to Archive Redo Data
        3.2.2 Using the Log Writer Process (LGWR) to Archive Redo Data
        3.2.3 Providing for Secure Redo Data Transmission

    3.3 What to Do If Errors Occur

    3.4 Setting Up a Data Protection Mode

        3.4.1 Choosing a Data Protection Mode
        3.4.2 Configuring Standby Redo Log Files
        3.4.3 Setting the Data Protection Mode of a Data Guard Configuration

    3.5 Managing Archive Gaps

        3.5.1 When Is an Archive Gap Discovered?
        3.5.2 How Is a Gap Resolved?
        3.5.3 Using the Fetch Archive Log (FAL) Process to Resolve Archive Gaps
        3.5.4 Manually Determining and Resolving Archive Gaps

    3.6 Verification

        3.6.1 Monitoring Log File Archival Information
        3.6.2 Monitoring the Performance of Log Transport Services

4->    Log Apply Services

    4.1 Introduction to Log Apply Services
    4.2 Log Apply Services Configuration Options

        4.2.1 Using Real-Time Apply to Apply Redo Data Immediately
        4.2.2 Specifying a Time Delay for the Application of Archived Redo Log Files

    4.3 Applying Redo Data to Physical Standby Databases

        4.3.1 Starting Redo Apply
        4.3.2 Starting Real-Time Apply
        4.3.3 Stopping Log Apply Services
        4.3.4 Monitoring Log Apply Services on Physical Standby Databases

    4.4 Applying Redo Data to Logical Standby Databases

        4.4.1 Starting SQL Apply
        4.4.2 Starting Real-time Apply
        4.4.3 Stopping Log Apply Services on a Logical Standby Database
        4.4.4 Monitoring Log Apply Services for Logical Standby Databases

    5.5 Tuning the Log Apply Rate for a Physical Standby Database

5-> Role Management

    5.1 Introduction to Role Transitions

        5.1.1 Which Role Transition to Use
        5.1.2 Switchovers
        5.1.3 Failovers

    5.2 Role Transitions Involving Physical Standby Databases

        5.2.1 Switchovers Involving a Physical Standby Database
        5.2.2 Failovers Involving a Physical Standby Database

    5.3 Role Transitions Involving Logical Standby Databases

        5.3.1 Switchovers Involving a Logical Standby Database
        5.3.2 Failovers Involving a Logical Standby Database

6-> Managing a Physical Standby Database

    6.1 Starting Up and Shutting Down a Physical Standby Database

        6.1.1 Starting Up a Physical Standby Database
        6.1.2 Shutting Down a Physical Standby Database

    6.2 Using a Standby Database That Is Open for Read-Only Access

        6.2.1 Assessing Whether or Not to Open a Standby Database for Read-Only Access
        6.2.2 Opening a Physical Standby Database for Read-Only Access
        6.2.3 Sorting Considerations for Standby Databases Open for Read-Only Access

    6.3 Managing Primary Database Events That Affect the Standby Database

        6.3.1 Adding a Datafile or Creating a Tablespace
        6.3.2 Dropping a Tablespace in the Primary Database
        6.3.3 Using Transportable Tablespaces with a Physical Standby Database
        6.3.4 Renaming a Datafile in the Primary Database
        6.3.5 Adding or Dropping Online Redo Log Files
        6.3.6 Altering the Primary Database Control File
        6.3.7 NOLOGGING or Unrecoverable Operations

    6.4 Using RMAN to Back Up and Restore Files on a Physical Standby Database

        6.4.1 Backup Procedure
        6.4.2 Effect of Switchovers, Failovers, and Control File Creation on Backups
        6.4.3 Additional Backup Situations
        6.4.4 Deletion Policy for Archived Redo Log Files In Flash Recovery Areas

    6.5 Recovering Through the OPEN RESETLOGS Statement
    6.6 Monitoring the Primary and Standby Databases

        6.6.1 Alert Log
        6.6.2 Dynamic Performance Views (Fixed Views)
        6.6.3 Monitoring Recovery Progress
7->  Managing a Logical Standby Database

    7.1 Configuring and Managing a Logical Standby Database

        7.1.1 Managing SQL Apply
        7.1.2 Controlling User Access to Tables in a Logical Standby Database
        7.1.3 Deleting Archived Redo Log Files No Longer Needed By SQL Apply
        7.1.4 Modifying a Logical Standby Database
        7.1.5 How Triggers and Constraints Are Handled on a Logical Standby Database
        7.1.6 Skipping SQL Statements on a Logical Standby Database
        7.1.7 Adding or Re-creating Tables on a Logical Standby Database
        7.1.8 Viewing and Controlling Logical Standby Events
        7.1.9 Understanding and Viewing SQL Apply Activity
        7.1.10 Enabling Real-Time Apply
        7.1.11 Determining How Much Redo Data Was Applied
        7.1.12 Recovering from Errors
        7.1.13 Refreshing Materialized Views



Click here to register or any further query