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.
Table of Contents (19 chapters)
Oracle Data Guard 11gR2 Administration Beginner's Guide
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Pop Quiz Answers
Index

Database rolling upgrade using the transient logical standby database


To perform upgrade of a production database from 11gR1 to 11gR2 or to perform any patch set upgrade (for example, from 11.2.0.1 to 11.2.0.3), we need downtime. When upgrading a production database that includes movement of the database to new binaries, database upgrade, and post upgrade tasks, we may need a few hours or more downtime depending on the database size, runtime errors, and so on. However, with the feature of Rolling Upgrade Using Transient Logical Standby, we may only need a few minutes of downtime. We can also run load tests to check the performance on the upgraded logical standby database when keeping the primary database with the old version without any upgrade. If the performance test results in a good response, we can go ahead to perform the further steps.