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

The Maximum Availability mode


The Maximum Availability mode is the data protection mode that has the ability to run as a Maximum Protection or Maximum Performance mode depending on the accessibility of standby databases. In a normal operation where the standby is up and able to receive redo data synchronously, the primary database acts like the Maximum Protection mode and waits for acknowledgment from the standby database to complete transactions. However, the key point of the Maximum Availability mode is the behavior of the primary database when it's not able to receive acknowledgment from any standby database. It waits for a predefined period of time and if the connection cannot be established, the primary database continues its operation as a Maximum Performance mode database. The number of seconds that the primary waits before marking a standby inaccessible is defined with the NET_TIMEOUT attribute of the LOG_ARCHIVE_DEST_n parameter. The default value of this parameter is 30 seconds...

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