D47658-Oracle dataguard student guide

Trang 1

Oracle Database 10g: Data Guard

Trang 2

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 94065 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.

Trang 3

Oracle Data Guard: Overview

Trang 4

• Describe the basic components of Oracle Data Guard

• Explain the differences between physical and logical standby databases

• Explain the benefits of creating a Data Guard

environment

• Explain the use of Data Guard in high-availability

architectures

Trang 5

1 - 3

Causes of Data Loss

Source: Disaster Recovery Journal

Trang 6

1 - 4

Understanding the Causes of Downtime

Planned downtime

Unplanned

downtime

System changes

Data changes

Data failures

Computer failures

Corruption

Human error

Site failure Storage failure

Trang 7

1 - 5

What Is Oracle Data Guard?

Primary database

Standby database

copy Redo transport

Trang 8

1 - 6

Types of Standby Databases

There are two types of standby databases:

• Physical standby database

basis

application of redo data received from the primary database

• Logical standby database

the data in the redo received from the primary database into SQL statements and then executing the SQL

statements

Trang 9

1 - 7

Oracle Data Guard Broker Framework

CLI management client Enterprise Manager

Repository

Primary database Data

Guard

broker

Oracle Management Server

Data Guard broker

Agent

Standby database Agent

Trang 10

1 - 8

Types of Services

There are three types of services provided with Data Guard:

• Redo transport services

• Log apply services

• Role-management services

Trang 11

1 - 9

Role Transitions: Switchover and Failover

• Oracle Data Guard supports two role-transition

operations:

of data protection mode

enabled

• Role-transition operations are not automatically

invoked.

Trang 12

Trang 13

1 - 13

Benefits of Implementing

Oracle Data Guard

Oracle Data Guard provides the following benefits:

• Continuous service through disasters or crippling data failures

• Complete data protection against corruptions and data loss

• Efficient use of system resources

• Elimination of idle standby systems

• Flexible configuration of your system to meet business protection and recovery requirements

• Centralized management

Trang 14

Data failures

Computer

failures

Corruption

Human error

Site failure

Storage failure

Oracle HARD RMAN

Data Guard

Trang 15

1 - 15

Role of Data Guard in a High-Availability Architecture

Data changes

System changes

• Online schema and data reorganization

• Partitioned tables and indexes

• Dynamic resource provisioning

• Rolling patch updates

• Rolling release upgrade using Data Guard

SQL Apply Planned

downtime

Trang 16

• Real Application Clusters provides high availability.

• Oracle Data Guard provides disaster protection and prevents data loss.

Trang 17

1 - 17

Maximum Availability Architecture

RAC production database

RAC physical standby database

Oracle Application Server

Oracle

Application

Server

WAN traffic manager

Clients

logical standby database

Trang 18

1 - 18

Summary

In this lesson, you should have learned how to:

• Describe the basic components of Oracle Data Guard

• Describe the differences between physical and logical standby databases

• Determine when Oracle Data Guard is an appropriate solution in your Oracle Database configuration

• Explain the use of Data Guard in high-availability

architectures

Trang 19

1 - 19

Practice 1: Overview

This practice covers the following topics:

• Reviewing the factors that affect planned and

Trang 20

Understanding the Oracle Data Guard Architecture

Trang 21

2 - 2

Objectives

After completing this lesson, you should be able to do the following:

• Describe the Data Guard architecture

• Explain the operational requirements of Data Guard

• Describe how Data Guard processes, transports, and applies redo logs

• Describe standby database modes

Trang 22

2 - 3

Data Guard Operational Requirements: Hardware

and Operating System

• The hardware can be different for the primary and

standby databases.

• The operating system and platform architecture for the primary and standby databases must be the same

• The operating system releases for the primary and

standby databases can be different.

• If all databases are on the same system, verify that the

OS allows you to mount more than one database with the same name.

Trang 23

2 - 4

Data Guard Operational Requirements: Oracle

Database Software

• Same release of Oracle Database Enterprise Edition

must be installed for all databases

• SYSDBA privileges are required for the accounts used to manage the database instances.

• Each database must have its own control file.

• Primary database must operate in ARCHIVELOG mode.

• Enable FORCE LOGGING on the primary database before taking data file backups for standby creation.

• If any databases use ASM and/or OMF, all should use the same combination.

Trang 24

ARC0

FAL

RFS

MRP or LSP

Archived redo

logs ARC0

Reports

(MRP only)

Standby redo logs

Trang 25

ARC0

FAL

RFS

MRP or LSP

Archived redo

logs ARC0

Reports

(MRP only)

Trang 26

ARC0

FAL

RFS

MRP or LSP

Archived redo

logs ARC0

Reports

(MRP only)

Trang 27

Archived redo logs

MRP/LSP

Trang 28

2 - 10

Physical Standby Database:

Redo Apply Architecture

Physical standby

database Redo

apply

Redo stream

Redo transport

Backup

Trang 29

SQL

SQL Apply

Reports

Production database

Logical standby database

Trang 30

2 - 13

Redo records

LCR LCR : Shared pool

Transaction groups

Transactions sorted in dependency order

Log Mining Apply processing

Logical change records not grouped into transactions

Transactions to

be applied

Analyzer Coordinator

Trang 31

2 - 14

Real-Time Apply

RFS

Standby redo log files

Archived redo log files

Trang 32

Trang 33

2 - 17

Specifying Role-Based Destinations

Trang 34

2 - 19

Combinations for VALID_FOR

Valid Valid

Valid ALL_LOGFILES , ALL_ROLES

Valid Valid

Ignored ALL_LOGFILES , STANDBY_ROLE

Ignored Ignored

Valid ALL_LOGFILES , PRIMARY_ROLE

Valid Valid

Ignored STANDBY_LOGFILE , ALL_ROLES

Valid Valid

Ignored STANDBY_LOGFILE , STANDBY_ROLE

Ignored Ignored Ignored

Physical

Valid Valid

ONLINE_LOGFILE , ALL_ROLES

Valid Ignored

ONLINE_LOGFILE , STANDBY_ROLE

Ignored Valid

ONLINE_LOGFILE , PRIMARY_ROLE

Logical Primary

Combination

Trang 35

-1 ALL_LOGFILES ALL_ROLES YES

2 STANDBY_LOGFILE STANDBY_ROLE WRONG VALID_TYPE

3 ONLINE_LOGFILE STANDBY_ROLE WRONG VALID_ROLE

4 ALL_LOGFILES ALL_ROLES UNKNOWN

11 ALL_LOGFILES ALL_ROLES YES

11 rows selected.

Trang 36

2 - 21

Standby Redo Log Configuration

Redo shipment

RFS

Online redo logs

Trang 37

2 - 22

Using SQL to Add Standby Redo Logs

• Use the ALTER DATABASE statement to create the

standby redo log files:

• Add members to a group with the following statement:

• View information about the groups as follows:

SQL> ALTER DATABASE ADD STANDBY LOGFILE MEMBER

2 '/oracle/oradata/orcl/log2b.rdo' TO GROUP 2;

SQL> ALTER DATABASE ADD STANDBY LOGFILE

2 ('/oracle/oradata/orcl/log1c.rdo',

3 '/oracle/oradata/orcl/log2c.rdo') SIZE 500K;

SQL> SELECT * FROM v$standby_log;

SQL> SELECT * FROM v$logfile

2 WHERE type = 'STANDBY';

Trang 38

2 - 23

Using Enterprise Manager

to Add Standby Redo Logs

Trang 39

2 - 24

Standby Database Modes

You can maintain the standby data in one of the following modes:

• For physical standby databases

• For logical standby databases

Trang 40

2 - 26

Summary

In this lesson, you should have learned how to describe the following:

• Data Guard architecture processes

• Operational requirements of a Data Guard environment

• How Data Guard processes, transports, and applies redo logs

• Modes of standby databases and when to use each mode

Trang 41

2 - 27

Practice 2-1: Architecture Review

• Reviewing the Oracle Data Guard architecture

• Reviewing the processes that Data Guard uses to transport and apply redo logs

• Reviewing the modes that are used to recover a primary database

Trang 42

2 - 28

Practice 2-2: Installing the Oracle Management Agent

• Installing the Oracle Management Agent

• Configuring monitoring credentials for your database

Trang 43

2 - 29

Practice 2-3: Configuring Your Primary Database

• Reviewing your primary database configuration

• Configuring your primary database in preparation for creating a Data Guard configuration

Trang 44

Using Data Guard Broker and Enterprise Manager

Trang 45

3 - 2

Objectives

After completing this lesson, you should be able to do the following:

• Describe the Data Guard broker architecture

• Describe the Data Guard broker components

• Explain the benefits of the Data Guard broker

• Explain Data Guard broker configurations

• Use Enterprise Manager to manage your Data Guard configuration

• Invoke DGMGRL to manage your Data Guard

configuration

Trang 46

3 - 3

Features of Data Guard Broker

• The Data Guard broker is a distributed management framework.

• The broker automates and centralizes the creation, maintenance, and monitoring of Data Guard

configurations.

• With the broker, you can perform all management operations locally or remotely through easy-to-use interfaces:

Trang 47

Trang 48

3 - 5

Data Guard Broker: Configurations

The most common configuration is a primary database at one location and a standby database at another location.

Chicago

Primary site

Boston

Standby site Oracle Net

Trang 49

3 - 6

Data Guard Broker: Management Model

Data Guard Broker Configuration

Broker-controlled databases

Standby database Standby database Standby database Standby database Standby database Standby database Standby database Standby database Standby database Instances

Instances

Trang 50

3 - 7

Primary site

Standby site 9 Standby site 2

Data Guard Broker: Architecture

Graphical user interface

or command-line interface

DMON

Online

redo logs

Standby site 1

Oracle Net

Log apply services Data Guard Configuration

Log transport services

Trang 51

3 - 8

Life Cycle of a Broker Configuration

Create configuration

Enable configuration

Make state or role changes

Update database properties

Monitor and tune configuration

Trang 52

3 - 9

Data Guard Broker: Requirements

• Enterprise Edition of Oracle Database 10g

• Single-instance or multi-instance environment

• COMPATIBLE must be set to 9.2.0.1.0 or higher for

primary and standby databases.

• Oracle Net network files must be configured for

databases that you add to the configuration.

• LOCAL_LISTENER on each instance must resolve to an address that is reachable by all members.

• GLOBAL_DBNAME attribute must be set to a

concatenation of:

db_unique_name_DGMGRL.db_domain

Trang 53

3 - 10

Data Guard Broker: Requirements

• DG_BROKER_START = TRUE

• The primary database must be in ARCHIVELOG mode.

• All databases must be in MOUNT or OPEN mode.

• Configure DG_BROKER_CONFIG_FILEn for any RAC

databases.

• START_OPTIONS for any RAC databases must be set to MOUNT in the Oracle Cluster Repository (OCR).

Trang 54

3 - 11

Data Guard Broker and the SPFILE

• You must use a server parameter file (SPFILE) for initialization parameters.

• Using the SPFILE enables the Data Guard broker to keep its configuration file and the database SPFILE consistent.

• If you use the broker, use Enterprise Manager or DGMGRL to update database parameter values.

Tiêu đề	Oracle Data Guard Administration
Tác giả	Donna K. Keesling, Christopher D. Andrews, Harald Van Breederode, Larry Carpenter, Michael Cebulla, Joel Goodman
Người hướng dẫn	Arijit Ghosh, Daniel Milne
Trường học	Oracle University
Thể loại	Bài giảng
Năm xuất bản	2006
Thành phố	Redwood Shores

Định dạng
Số trang	300
Dung lượng	3,82 MB