Oracle Data Guard 11gR2 Administration : Beginner's Guide

Book Image

Oracle Data Guard 11gR2 Administration : Beginner's Guide

Book Image

Oracle Data Guard 11gR2 Administration : Beginner's Guide

Overview of this book

Data Guard is the high availability, disaster recovery and data replication solution for Oracle Databases. With the huge growth of Data Guard it's getting harder to encounter an Oracle DBA not dealing with Data Guard. Since it's a common DBA task to provide high availability of databases, Data Guard is a must-know topic for every Oracle Database Administrator."Oracle Data Guard 11g R2 Beginner's Administration Guide" is a practical guide that provides all the information you will need to configure and maintain Data Guard. This book will show you what Data Guard can really do.By following the practical examples in this book, you'll learn to set up your Data Guard Broker, the management framework for Data Guard configurations. Learn and implement different data protection modes, perform role transitions between databases (switchover and failover) and configure Active Data Guard. Next, we will dive into the features of Snapshot Standby. The book progresses into looking at Data Guard configuration with other Oracle products (such as EM, RAC, and RMAN) and patch databases in Data Guard. The final chapters will cover commonly encountered Data Guard issues and Data Guard best practices, which are very important to make a Data Guard configuration perfect and take maximum advantage of Data Guard properties.

Oracle Data Guard 11gR2 Administration Beginner's Guide

Oracle Data Guard 11gR2 Administration Beginner's Guide

Credits

About the Authors

About the Authors

About the Reviewers

About the Reviewers

www.PacktPub.com

www.PacktPub.com

Preface

Pop Quiz Answers

Pop Quiz Answers

Free Chapter

Getting Started

Getting Started

What is Data Guard?

Standby database

Oracle Data Guard evolution

Oracle Data Guard architecture

Time for action – monitoring Redo Apply

Time for action – using interfaces to monitor Data Guard

Other replication solutions and Data Guard

Configuring the Oracle Data Guard Physical Standby Database

Configuring the Oracle Data Guard Physical Standby Database

Preconfiguration for Data Guard

Time for action – enabling the archive log mode

Time for action – enabling force logging

Time for action – configuring standby redo logs on primary

Time for action – enabling FRA

Creating the physical standby database

Time for action – starting the physical standby instance and making it ready for the RMAN duplicate

Time for action – running an RMAN duplicate

Post-installation steps

Time for action – verifying the standby database configuration

Time for action – starting, stopping, and monitoring MRP

Time for action – verifying synchronization between the primary and standby databases

Time for action – testing real-time apply

Configuring Oracle Data Guard Logical Standby Database

Configuring Oracle Data Guard Logical Standby Database

Logical standby database characteristics

Preparation for the configuration

Time for action – checking for the unsupported data types

Time for action – searching for and fixing any table row uniqueness problem

Creating a logical standby database

Time for action – making a physical standby database environment ready for conversion

Time for action – converting a physical standby database into a logical standby database

Verifying the logical standby database

Time for action – checking the redo transport service status

Time for action – checking the SQL Apply service status

Customization and management in a logical standby database

Time for action – working with skip rules on a logical standby database

Time for action – changing the Database Guard setting

Time for action – creating objects on the logical standby database

Oracle Data Guard Broker

Oracle Data Guard Broker

Introduction to Data Guard broker

Data Guard broker features and benefits

Data Guard broker components

Implementation of Oracle Data Guard broker

Time for action – initial setup of Data Guard broker

Time for action – connecting to Data Guard broker

Time for action – basic monitoring with Data Guard broker

Management with Data Guard broker

Time for action – disabling broker configuration

Time for action – disabling and enabling database

Time for action – changing the database name

Most Common Data Guard broker issues

Oracle Data Guard fast-start failover

Time for action – configuring fast-start failover

Data Guard Protection Modes

Data Guard Protection Modes

The Maximum Protection mode

The Maximum Performance mode

The Maximum Availability mode

Choosing the correct mode for your requirements

Changing Data Guard protection mode

Time for action – changing the protection mode with SQL*Plus

Time for action – changing the protection mode with Data Guard broker

Time for action – changing the protection mode with Enterprise Manager Cloud Control

Data Guard Role Transitions

Data Guard Role Transitions

Role transition considerations

Time for action – preliminary tests before performing switchover

Time for action – switchover with a physical standby using SQL*Plus

Time for action – switchover with a physical standby using broker

Time for action – switchover with a physical standby using EM Cloud Control

Time for action – switchover with a logical standby database using SQL*Plus

Time for action – switchover with a logical standby using broker

Time for action – failover with a physical standby database using SQL*Plus

Time for action – failover with a logical standby using broker

Active Data Guard, Snapshot Standby, and Advanced Techniques

Active Data Guard, Snapshot Standby, and Advanced Techniques

Oracle Active Data Guard

Time for action – enabling Active Data Guard if Redo Apply is running using SQL *PLUS

Time for action – enabling Active Data Guard if the standby database is shut down

Time for action – enabling Active Data Guard using broker

Time for action – Active Data Guard with PeopleSoft

Time for action – exporting a database backup from Active Data Guard

Time for action – using the ASH report from the standby database

Using a snapshot standby database

Time for action – converting to a snapshot standby database

Time for action – converting to a physical standby database

Cascade standby databases

Time for action – cascade standby database

Advanced compression in Data Guard

Time for action – enabling advanced compression

Preparation of standby on a cross-platform Data Guard

Time for action – creating a cross-platform Data Guard setup

Data Guard tuning and wait events

Integrating Data Guard with the Complete Oracle Environment

Integrating Data Guard with the Complete Oracle Environment

The Oracle Enterprise Manager Cloud Control integration

Time for action – adding the Data Guard configuration into Cloud Control

Time for action – enabling/disabling fast-start failover

Time for action – setting the threshold and creating an incident for estimated failover time metric

RMAN integration

Time for action – recovering a primary database using a standby database disk backup

RAC integration

Data Guard Configuration Patching

Data Guard Configuration Patching

What is patch and what are patch types?

Best practices of patching

Upgrading OPatch

Performing prerequisite checks of patch

How to clean up patch history?

Patching on Data Guard configuration

Time for action – applying a patch on logical standby

Time for action – applying PSU on a physical standby database

Time for action – patch set upgrade of physical standby

Common Data Guard Issues

Common Data Guard Issues

Recreating the standby control file

Time for action – recreating the standby control file

Dealing with redo transport authentication problems

Time for action – changing the SYS password in a Data Guard environment

Time for action – changing the redo transport user

Dealing with UNNAMED datafiles

Time for action – resolving UNNAMED datafile errors

Closing a gap with an RMAN incremental backup

Time for action – closing a gap with an RMAN incremental backup

Fixing NOLOGGING changes on the standby database

Time for action – fixing NOLOGGING changes on a standby database with incremental datafile backups

Time for action – fixing NOLOGGING changes in the standby database with incremental database backups

Turning on Data Guard tracing

Gathering diagnostic data

Time for action – monitoring the database alert log using ADRCI

Data Guard Best Practices

Data Guard Best Practices

Configuring a connection failover

Time for action – configuring FCF for JDBC connections

The archived log deletion policy on the standby database

Time for action – the recommended configuration for archived log maintenance on a standby database

Using flashback on a standby database

Time for action – using flashback on a standby database

Database rolling upgrade using the transient logical standby database

Time for action – performing a rolling upgrade using the transient logical standby database

Corruption detection, prevention, and automatic repair with Oracle Data Guard

Index

Customer Reviews

5 star

0

4 star

0

3 star

0

2 star

0

1 star

0

Time for action – verifying the standby database configuration

Run the following actions to verify the standby database configuration and redo transport services:

Connect the standby database using SQL*Plus and check for the database role and status to ensure the database role is the physical standby.

SQL> select db_unique_name,database_role,open_mode from v$database;
DB_UNIQUE_NAME  DATABASE_ROLE    OPEN_MODE
--------------- ---------------- --------------------
india_un        PHYSICAL STANDBY MOUNTED

Check the standby database, SPFILE.

SQL> show parameter spfile
NAME   TYPE    VALUE
------ ------- --------------------------------------------------
spfile string  /u01/app/oracle/product/11.2.0/db_1/dbs/spfileINDIA.ora

Tip

If you have started the standby instance with PFILE, you should create an SPFILE and start an instance again using the new SPFILE.

Use the v$datafile view to check the location of the datafiles in the standby database. The standby database datafile must be under the...