Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Oracle Data Guard 11gR2 Administration : Beginner's Guide

You're reading from   Oracle Data Guard 11gR2 Administration : Beginner's Guide If you're an Oracle Database Administrator it's almost essential to know how to protect and preserve your data. This is the perfect primer to Data Guard that covers all the bases with a totally practical, user-friendly approach.

Arrow left icon
Product type Paperback
Published in Jun 2013
Publisher Packt
ISBN-13 9781849687904
Length 404 pages
Edition 1st Edition
Arrow right icon
Toc

Table of Contents (19) Chapters Close

Oracle Data Guard 11gR2 Administration Beginner's Guide
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Pop Quiz Answers
1. Getting Started FREE CHAPTER 2. Configuring the Oracle Data Guard Physical Standby Database 3. Configuring Oracle Data Guard Logical Standby Database 4. Oracle Data Guard Broker 5. Data Guard Protection Modes 6. Data Guard Role Transitions 7. Active Data Guard, Snapshot Standby, and Advanced Techniques 8. Integrating Data Guard with the Complete Oracle Environment 9. Data Guard Configuration Patching 10. Common Data Guard Issues 11. Data Guard Best Practices Index

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


Follow these steps to complete a failover on the physical standby Data Guard environment:

  1. If you're able to mount a primary database, perform the following command to flush the redo from the primary online redo logfiles:

    SQL> alter system flush redo to INDIA_UN;

    Use DB_UNIQUE_NAME of the standby database so that redo will be sent to the respective standby database.

  2. Check the status of both the primary and standby databases. With the primary database in the MOUNT state, check the maximum archive log sequence that has been generated as shown in the following code:

    SQL> select max(sequence#) from v$archived_log;
    MAX(SEQUENCE#)
    --------------
               462
  3. If the primary database is inaccessible, refer to the alert logfile for the latest log switch sequence or go to the archive log location and check the maximum sequence number as shown in the following command:

    Fri Oct 12 22:20:30 2012
    Thread 1 advanced to log sequence...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image