Oracle Database 10g: Data Guard Administration

Transcription

1 Oracle Database 10g: Data Guard Administration Volume I Student Guide D17316GC20 Edition 2.0 October 2006 D47657

2 Author Donna K. Keesling Technical Contributors and Reviewers Christopher D. Andrews Harald van Breederode Larry Carpenter Michael Cebulla Joel Goodman Editors Arijit Ghosh Daniel Milne Graphic Designer Satish Bettegowda Publishers Srividya Rameshkumar Jobi Varghese Copyright 2006, Oracle. All rights reserved. Disclaimer This document contains proprietary information and is protected by copyright and other intellectual property laws. You may copy and print this document solely for your own use in an Oracle training course. The document may not be modified or altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download, upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part without the express authorization of Oracle. The information contained in this document is subject to change without notice. If you find any problems in the document, please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California USA. This document is not warranted to be error-free. Restricted Rights Notice If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS The U.S. Government s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract. Trademark Notice Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

3 Contents Preface 1 Oracle Data Guard: Overview Objectives 1-2 Causes of Data Loss 1-3 Understanding the Causes of Downtime 1-4 What Is Oracle Data Guard? 1-5 Types of Standby Databases 1-6 Oracle Data Guard Broker Framework 1-7 Types of Services 1-8 Role Transitions: Switchover and Failover 1-9 Data Protection Modes 1-11 Benefits of Implementing Oracle Data Guard 1-13 Role of Data Guard in a High-Availability Architecture 1-14 Oracle Data Guard and Real Application Clusters 1-16 Maximum Availability Architecture 1-17 Summary 1-18 Practice 1: Overview Understanding the Oracle Data Guard Architecture Objectives 2-2 Data Guard Operational Requirements: Hardware and Operating System 2-3 Data Guard Operational Requirements: Oracle Database Software 2-4 Oracle Data Guard: Architecture 2-6 Primary Database Flow 2-7 Standby Database Flow 2-8 Standby Redo Logs 2-9 Physical Standby Database: Redo Apply Architecture 2-10 Logical Standby Database: SQL Apply Architecture 2-12 SQL Apply Process: Architecture 2-13 Real-Time Apply 2-14 Setting the DB_UNIQUE_NAME Parameter 2-16 Specifying Role-Based Destinations 2-17 Combinations for VALID_FOR 2-19 Identifying Destination Settings 2-20 iii

4 Standby Redo Log Configuration 2-21 Using SQL to Add Standby Redo Logs 2-22 Using Enterprise Manager to Add Standby Redo Logs 2-23 Standby Database Modes 2-24 Summary 2-26 Practice 2-1: Architecture Review 2-27 Practice 2-2: Installing the Oracle Management Agent 2-28 Practice 2-3: Configuring Your Primary Database Using Data Guard Broker and Enterprise Manager Objectives 3-2 Features of Data Guard Broker 3-3 Data Guard Broker: Components 3-4 Data Guard Broker: Configurations 3-5 Data Guard Broker: Management Model 3-6 Data Guard Broker: Architecture 3-7 Life Cycle of a Broker Configuration 3-8 Data Guard Broker: Requirements 3-9 Data Guard Broker and the SPFILE 3-11 Data Guard Monitor: DMON Process 3-13 Data Guard Monitor: Configuration File 3-14 Benefits of Using the Data Guard Broker 3-15 Data Guard Broker Interfaces 3-17 Using Oracle Enterprise Manager 10g Grid Control 3-19 Data Guard Overview Page 3-20 Enterprise Manager Metrics and Alerts 3-21 Using Data Guard Metrics 3-22 Managing Data Guard Metrics 3-23 Benefits of Using Enterprise Manager 3-24 Using the Command-Line Interface of the Data Guard Broker 3-25 Summary Creating a Configuration and Physical Standby Database by Using Enterprise Manager Objectives 4-2 Enabling FORCE LOGGING Mode 4-3 Using Enterprise Manager to Create a Broker Configuration 4-5 Creating a Configuration 4-6 Using the Add Standby Database Wizard 4-8 Step 1: Specify the Backup Type 4-9 Step 2: Specify the Backup Options 4-10 iv

5 Step 3: Select the Standby Database Location Instance Name 4-11 Step 3: Select the Standby Database Location Oracle Home 4-12 Step 4: Specify the Standby Database File Locations Access Method 4-13 Step 4: Specify the Standby Database File Locations File Locations 4-14 Step 5: Specify Standby Database Configuration Parameters 4-15 Step 6: Review the Configuration Information 4-16 Standby Database Creation: Processing 4-17 Standby Database Creation: Progress 4-19 Standby Database Creation: Job Details 4-20 Verifying a Configuration 4-21 Reviewing Results of the Verify Operation 4-22 Creating Standby Redo Logs 4-23 Viewing the Data Guard Configuration Status 4-24 Viewing Data Guard Performance 4-25 Summary 4-26 Practice 4: Overview Creating a Physical Standby Database by Using SQL Objectives 5-2 Steps to Create a Physical Standby Database 5-3 Preparing the Primary Database 5-4 Setting Initialization Parameters on the Primary Database 5-5 LOG_ARCHIVE_CONFIG 5-6 LOG_ARCHIVE_DEST_n 5-8 LOCATION and SERVICE Attributes 5-9 LOG_ARCHIVE_DEST_STATE_n 5-10 Specifying Values for DB_FILE_NAME_CONVERT 5-11 Specifying Values for LOG_FILE_NAME_CONVERT 5-12 Specifying a Value for LOG_ARCHIVE_FORMAT 5-13 Specifying a Value for STANDBY_FILE_MANAGEMENT 5-14 ARCHIVE_LAG_TARGET 5-15 LOG_ARCHIVE_TRACE Parameter 5-16 Example: Setting Initialization Parameters on the Primary Database 5-18 Backing Up the Primary Database by Using RMAN 5-19 Creating a Control File for the Standby Database 5-20 Copying Files to the Standby Database System 5-21 Oracle Managed Files (OMF) and Automatic Storage Management (ASM) 5-22 Setting Initialization Parameters on the Standby Database 5-23 Specifying a Value for STANDBY_ARCHIVE_DEST 5-25 Setting Up the Environment to Support the Standby Database 5-26 v

6 Starting the Physical Standby Database 5-28 Additional Configuration Tasks 5-29 Special Note: Standby Database on the Same System 5-31 Summary Configuring Data Protection Modes and Redo Transport Services Objectives 6-2 Data Protection Modes and Redo Transport Modes 6-3 Defining the Redo Transport Mode 6-4 Setting the Redo Transport Mode 6-6 Data Protection Modes 6-8 Maximum Protection 6-9 Maximum Availability 6-10 Maximum Performance 6-11 Setting the Data Protection Mode 6-12 Setting the Data Protection Mode by Using the CLI 6-14 Setting the Protection Mode by Using SQL 6-15 Delaying the Application of Redo 6-16 Using Enterprise Manager to Delay the Application of Redo 6-17 Setting LOG_ARCHIVE_DEST_n to Delay the Application of Redo 6-18 Using Flashback Database Instead of Apply Delay 6-19 Additional Attributes That Affect Redo Transport Services 6-20 Using the ALTERNATE Attribute 6-21 Using the MAX_FAILURE Attribute 6-22 Using the NET_TIMEOUT Attribute 6-23 Using the REOPEN Attribute 6-24 Optimized Asynchronous Redo Transmission 6-25 Enabling Multiple Connections for Remote Archival of Redo 6-26 Summary 6-27 Practice 6: Overview Creating a Logical Standby Database by Using Enterprise Manager Objectives 7-2 Benefits of Implementing a Logical Standby Database 7-3 Securing Your Logical Standby Database 7-5 Preparing to Create a Logical Standby Database 7-6 Unsupported Objects 7-7 Unsupported Data Types 7-8 Checking for Tables with Unsupported Data Types 7-9 Unsupported DDL Commands 7-10 vi

7 Ensuring Unique Row Identifiers 7-11 Adding a Disabled Primary Key RELY Constraint 7-13 Supplemental Logging 7-14 Enabling Supplemental Logging 7-15 Verifying Values of Initialization Parameters 7-16 Creating a Logical Standby Database with Enterprise Manager 7-17 Using the Add Standby Database Wizard 7-18 Step 1: Specifying the Backup Type 7-19 Step 2: Specifying the Backup Options 7-20 Step 3: Selecting the Database Location Instance Name 7-21 Step 4: Specifying the Standby Database File Locations Access Method 7-22 Step 4: Specifying the Standby Database File Locations File Locations 7-23 Step 5: Specifying Standby Database Configuration Parameters 7-24 Step 6: Reviewing the Configuration Information 7-25 Standby Database Creation Processing 7-26 Automatic Deletion of Redo Log Files by SQL Apply 7-27 Enabling and Disabling the Auto-Delete Feature 7-28 Summary 7-29 Practice 7: Overview Creating a Logical Standby Database by Using SQL Objectives 8-2 Preparing to Create a Logical Standby Database 8-3 Creating a Logical Standby Database 8-4 Step 1: Create a Physical Standby Database 8-5 Step 2: Stop Redo Apply on the Physical Standby Database 8-6 Step 3: Prepare the Primary Database to Support a Logical Standby Database 8-7 Step 4: Build a LogMiner Dictionary in the Redo Data 8-8 Step 5: Transition to a Logical Standby Database 8-9 Step 6: Open the Logical Standby Database 8-10 Step 7: Verify That the Logical Standby Database Is Performing Properly 8-11 Additional Configuration Tasks 8-13 Summary Performing Switchover and Failover Objectives 9-2 Types of Roles in an Oracle Data Guard Configuration 9-3 Role Management Services 9-4 Role Transitions: Switchover and Failover 9-5 Choosing the Best Role Transition Operation 9-7 Switchover 9-8 vii

8 Switchover: Before 9-9 Switchover: After 9-10 Standby Redo Logs and Switchovers 9-11 Preparing for a Switchover 9-12 Performing a Switchover by Using Enterprise Manager 9-13 Performing a Switchover to a Physical Standby by Using SQL 9-16 Performing a Switchover to a Logical Standby by Using SQL 9-18 Considerations When Performing a Switchover to a Logical Standby Database 9-23 Situations That Prevent a Switchover 9-24 Failover 9-25 Failover Considerations 9-26 Performing a Failover by Using Enterprise Manager 9-27 Performing a Failover to a Physical Standby Database 9-31 Performing a Failover to a Logical Standby Database 9-32 Performing a Failover to a Physical Standby Database by Using SQL 9-33 Performing a Failover to a Logical Standby Database by Using SQL 9-36 Activating a Standby Database 9-38 Restoring Databases After a Role Transition 9-39 Flashback Through Standby Database Role Transitions 9-40 Using Flashback Database After Failover 9-41 Summary 9-44 Practice 9: Overview Enabling Fast-Start Failover Objectives 10-2 Fast-Start Failover: Overview 10-3 When Will Fast-Start Failover Occur? 10-4 Installing the Observer 10-5 Configuring Fast-Start Failover 10-6 Step 1: Specifying the Target Standby Database 10-7 Step 2: Setting the Fast-Start Failover Threshold 10-8 Step 3: Enabling Fast-Start Failover 10-9 Step 4: Starting the Observer Step 5: Verifying the Configuration Viewing Information Prohibited Operations After Enabling Fast-Start Failover Disabling Fast-Start Failover Using the FORCE Option Stopping the Observer Performing Role Changes Performing a Manual Failover viii

9 Automatic Reinstatement After Fast-Start Failover Manually Reinstating the Database Using Enterprise Manager to Enable Fast-Start Failover Changing the Protection Mode and Disabling Fast-Start Failover Using Enterprise Manager to Disable Fast-Start Failover Using Enterprise Manager to Suspend Fast-Start Failover Summary Practice 10: Overview Using Data Guard in a Real Application Clusters Configuration Objectives 11-2 Real Application Clusters and Data Guard 11-3 Configuration Considerations with RAC 11-4 Multi-Instance Primary Database with a Single-Instance Standby Database 11-6 Multi-Instance Primary Database with a Multi-Instance Standby Database 11-7 Redo Transport with RAC to RAC 11-8 Setting Up a Primary Database with RAC 11-9 Setting Up a Standby Database with RAC Assigning Threads to Standby Redo Log Groups Apply Instance Failover Role Transitions with RAC Troubleshooting Summary Other Considerations for Oracle Data Guard Objectives 12-2 Offloading Backups to a Physical Standby 12-3 Using RMAN to Back Up a Physical Standby Database 12-4 Restrictions and Usage Notes 12-5 Backup and Recovery of a Logical Standby Database 12-6 Flashback Across Database Changes 12-7 Using Flashback Database and Real-Time Apply 12-8 Using Flashback Database After RESETLOGS 12-9 Enabling Redo Encryption Activating a Physical Standby Database for Reporting Cascaded Redo Log Destinations Configuring Cascaded Redo Log Destinations: Physical Standby Role Transitions with Cascaded Redo Log Destinations Summary ix

10 13 Workshop Objectives 13-2 Workshop Premise 13-3 Workshop Flow 13-4 Workshop Scenarios 13-5 Summary 13-8 Appendix A: Practices and Solutions x