Tài liệu Oracle Database 10g : New Features For Administrators ppt

Database Control and Data Pump 3-18Using EM to Monitor Data Pump Jobs 3-19 Parallel Full Export and Import: Examples 3-20 Limited Schema Export: Example 3-21 Network Mode Import: Example

Oracle Database 10g: New

Features for AdministratorsVolume III • Student Guide

D17079GC20

Edition 2.0

August 2005

D19871

Copyright © 2005, 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 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 Retek are registered trademarks of Oracle Corporation and/or its affiliates Other names may be trademarks of their respective owners.

I Introduction

Overview I-2

Today’s IT Infrastructure I-3

How DBAs Spent Their Time Before Oracle Database 10g I-4

Grid Computing I-5

Oracle Ecosystem I-6

Enterprise Grid Computing I-7

Implement One from Many I-8

Manage Many as One I-10

Readily Available Product Controls I-12

Oracle Enterprise Manager 10g Grid Control I-13

Oracle Database 10g: The Database for the Grid I-14

Suggested Additional Courses I-15

Oracle Database 10g Manageability Goals I-16

Database Management Challenges I-17

Oracle Database 10g Solution: Self-Managing Database I-18 How Oracle Database 10g DBAs Spend Their Time I-19

Further Information I-20

Suggested Schedule I-21

1 Installation

Objectives 1-2

Installation Methods 1-3

Installation: New Feature Support 1-4

Performance Enhancements to Installation 1-5

Checking the Preinstallation Requirements 1-6

Miscellaneous Installation Enhancements 1-7

Response File Improvements 1-8

CD Pack Contents 1-9

Management Options 1-10

File Storage Options 1-11

Backup and Recovery Options 1-12

Passwords 1-13

Grid Control Components 1-14

Managed Targets for Grid Control 1-16

Oracle Management Service 1-17

Oracle Management Repository 1-18

Grid Control Console: Home 1-19

Grid Control Console: Targets 1-20

Managing Very Large Grids 1-21

Summary 1-22

Contents

iii

2 Server Configuration

Objectives 2-2

Database Configuration Assistant (DBCA) Enhancements 2-3 Using Database Control for Management 2-5

SYSAUX and DBCA 2-6

Database Control: Overview 2-7

Important EM Agent Directories 2-8

Configuring Database Control 2-9

Managing Database Control Components 2-10

Database Home Page: Overview 2-11

Database Control Setup Pages 2-13

Database Control Preferences Pages 2-14

Net Services Administration Pages 2-15

Database Feature Usage: Statistics Collection 2-16

Database Feature Usage: EM Interface 2-17

Database Feature Usage: HWM Page 2-18

Policy Framework 2-19

Policy Violations Page 2-20

Manage Policy Violations Page 2-22

Rule Violation Page 2-24

Manage Policy Library Page 2-25

Simplified Initialization Parameters 2-26

Viewing Initialization Parameters 2-27

Irreversible Data File Compatibility 2-28

Enabling iSQL*Plus DBA Access 2-29

Accessing iSQL*Plus DBA from EM 2-30

Summary 2-31

Practice 2: Overview 2-32

3 Data Pump, SQL*Loader, and External Tables

Objectives 3-2

Data Pump: Overview 3-3

Data Pump: General Architecture 3-4

Data Pump Export and Import: Overview 3-5

Data Pump Export and Import: Benefits 3-6

General Implementation: Overview 3-8

Data Pump Direct Path: Considerations 3-9

Data Pump File Locations 3-10

Data Pump File Naming and Size 3-12

Data Pump Utility: Interfaces and Modes 3-13

Database Control and Data Pump 3-18

Using EM to Monitor Data Pump Jobs 3-19

Parallel Full Export and Import: Examples 3-20

Limited Schema Export: Example 3-21

Network Mode Import: Example 3-22

Attaching to Existing Job: Example 3-23

Restarting a Stopped Job: Example 3-24

Data-Only Unload: Example 3-25

Loading Data from Flat Files by Using EM 3-26

External Table Population: Overview 3-27

External Table Population Operation 3-28

External Table Parallel Populate Operation 3-29

External Table Population: Example 3-30

External Table Projected Columns 3-31

External Table Projected Column: Examples 3-32

Summary 3-33

Practice 3: Overview 3-34

4 Database and Tablespace Data Movements

Objectives 4-2

Cross-Platform Transportable Tablespaces 4-3

Minimum Compatibility Level 4-4

Transportable Tablespace Procedure 4-5

Determining the Endian Format of a Platform 4-6

Data File Conversion: Examples 4-7

CLOB Exception 4-8

Using Database Control to Transport Tablespaces 4-9 Generating Transportable Tablespace Sets 4-10

Specifying Destination Characteristics 4-11

Specifying Conversion Information 4-12

Specifying the Files Transfer Mode 4-13

Database Transportation: Overview 4-14

Database Transportation Procedure 4-15

Database Transportation: Conversion 4-16

Database Transportation: Example 1 4-17

Database Transportation: Example 2 4-18

Database Transportation: Generated Pfile 4-19

Database Transportation: Generated SQL Script 4-20 Database Transportation: Generated RMAN Script 4-22 Database Transportation: Considerations 4-23

DBMS_TDB Package 4-24

Database Cloning Using Database Control 4-25

Transport Tablespace from Backup: Overview 4-26 Transport Tablespace from Backup: Implementation 4-27

v

Transport Tablespace from Backup: Example 4-28

Managing a File Group Repository 4-38

File Group Repository Catalog 4-41

File Group Repository Catalog Views 4-42

File Group Repository Privileges 4-43

Privileges for Versioning Tablespaces 4-45

Summary 4-46

Practice 4: Overview 4-47

5 Automatic Management

Objectives 5-2

Oracle Database 10g Solution: Self-Managing Database 5-3

Automatic Database Diagnostic Monitor: Overview 5-4 ADDM Performance Monitoring 5-5

ADDM Methodology 5-6

Top Performance Issues Detected 5-7

Database Control and ADDM Findings 5-8

ADDM Analysis Results 5-9

ADDM Recommendations 5-10

Database Control and ADDM Task 5-11

Changing ADDM Attributes 5-12

Retrieving ADDM Reports by Using SQL 5-13

Automatic Shared Memory Management: Overview 5-14 SGA Tuning Principles 5-15

Benefits of Automatic Shared Memory Management 5-16 Automatic Shared Memory Management 5-17

SGA Advisor 5-18

Manual Configuration 5-19

Behavior of Autotuned SGA Parameters 5-20

Behavior of Manually Tuned SGA Parameters 5-21

Using the V$PARAMETER View 5-22

Changing the Default Schedule 5-33

Automatic Undo Retention Tuning 5-34

Automatic Checkpoint Tuning 5-35

Automatically Tuned Multiblock Reads 5-36

Summary 5-37

Practice 5: Overview 5-38

6 Manageability Infrastructure

Objectives 6-2

Oracle Database 10g Solution: Self-Managing Database 6-3

Automatic Workload Repository 6-4

Automatic Workload Repository: Overview 6-5

Automatic Workload Repository Data 6-6

Active Session History 6-7

Generate ASH Reports 6-8

Base Statistics and Metrics 6-9

Workload Repository 6-10

Statistic Levels 6-11

AWR Snapshot Sets 6-12

AWR Snapshot Purging Policy 6-13

Database Control and AWR 6-14

Generating AWR Reports 6-15

Snapshot Sets and Period Comparisons 6-16

Compare Periods: Results 6-17

Statspack and AWR 6-18

Server-Generated Alerts 6-19

Server-Generated Alerts: Overview 6-20

Alert Models Architecture 6-21

Server-Generated Alert Types 6-22

Readily Available Server-Generated Alerts 6-23

Database Control Usage Model 6-24

Database Control Interface to Alerts 6-25

Setting Alert Thresholds 6-26

Alerts Notification 6-27

Metric Details Severity History 6-28

Metric and Alert Views 6-29

PL/SQL Interface for Threshold Settings 6-30

Alert Consumption: Manual Configuration 6-31

vii

User-Defined SQL Metrics 6-32

Automatic Routine Administration Tasks 6-33

DBCA and Automated Tasks 6-34

Common Manageability Infrastructure: Advisory Framework 6-35 Advisory Framework: Overview 6-36

Typical Advisor Tuning Session 6-37

Database Control and Advisors 6-38

Cyclic Nature of Workloads 7-3

Thresholds and Metric Baselines Overview: Fixed Thresholds 7-4 Thresholds and Metric Baselines Overview: Adaptive Thresholds 7-5 Metric Baselines and Thresholds Concepts 7-6

Metric Baselines and Time Groups 7-8

Enabling Metric Baselining 7-9

Activating the Moving Window Metric Baseline 7-10

Setting Adaptive Alert Thresholds 7-11

Visualizing Metric Baseline Statistics 7-12

Creating Static Metric Baselines 7-13

Time Grouping: Considerations 7-14

Metric Baseline and Adaptive Threshold: Considerations 7-15

Classification of Eligible Metrics 7-16

Metric Baseline: Normalized View 7-17

Configuring Normalization Metrics 7-19

Adaptive Thresholds and the All Metrics Page 7-20

Summary 7-21

Practice 7: Overview 7-22

8 Application Tuning

Objectives 8-2

Oracle Database 10g Solution: Self-Managing Database 8-3

Automatic Statistics Gathering 8-4

Enhanced Query Optimization 8-5

Statistics on Dictionary Objects 8-6

Dictionary Statistics: Best Practices 8-7

History of Optimizer Statistics 8-12

Managing Historical Optimizer Statistics 8-13 Managing Optimizer Statistics Using EM 8-14 DML Table Monitoring Changes 8-15

Rule-Based Optimizer Obsolescence 8-16 Automatic SQL Tuning: Overview 8-17

Application Tuning Challenges 8-18

SQL Tuning Advisor: Overview 8-19

Stale or Missing Object Statistics 8-20

SQL Tuning Advisor: Usage Model 8-26

Database Control and SQL Tuning Advisor 8-27 Implementing Recommendations 8-28

DBMS_SQLTUNE Package 8-29

DBMS_SQLTUNE: Examples 8-30

Exporting or Importing SQL Profiles 8-31

Automatic SQL Tuning Categories 8-32

SQL Access Advisor: Overview 8-33

SQL Access Advisor: Usage Model 8-34

Database Performance Page 8-45

Active Sessions Waiting Pages 8-46

Traditional Workload Dispatching 9-3

Grid Workload Dispatching 9-4

What Is a Service? 9-5

ix

High Availability of Services in RAC 9-6

Possible Service Configuration with RAC 9-7

Service Attributes 9-8

Service Types 9-9

Service Goodness 9-10

Fast Application Notification for Continuous Service 9-11

Fast Connection Failover: Overview 9-12

Load Balancing Advisory 9-13

JDBC Runtime Connection Load Balancing: Benefit 9-14

Connection Load Balancing in RAC 9-15

Load Balancing Workflow in RAC 9-16

Creating Services 9-17

Managing Services in a Single-Instance Environment 9-18

Everything Switches to Services 9-19

Using Services with Client Applications 9-20

Using Services with the Resource Manager 9-21

Services and Resource Manager with EM 9-22

Services and the Resource Manager: Example 9-23

Using Services with the Scheduler 9-24

Services and the Scheduler with EM 9-25

Services and the Scheduler: Example 9-27

Using Services with Parallel Operations 9-28

Using Services with Metric Thresholds 9-29

Changing Service Thresholds by Using EM 9-30

Services and Metric Thresholds: Example 9-31

Service Aggregation and Tracing 9-32

Top Services Performance Page 9-33

Service Aggregation Configuration 9-34

Service Aggregation: Example 9-35

trcsess Utility 9-36

Service Performance Views 9-37

Generalized Trace Enabling 9-38

Summary 9-39

Practice 9: Overview 9-40

10 System Resource Management

Objectives 10-2

Oracle Database 10g Solution: Self-Managing Database 10-3

Database Resource Manager 10-4

Switching Plans at Scheduler Window Boundaries 10-5

Assigning Priorities by Using DBMS_RESOURCE_MANAGER 10-11 Changes to the DBMS_RESOURCE_MANAGER Package 10-13 Using the RATIO Allocation Method 10-15

Monitoring the Database Resource Manager 10-16

Monitoring the Resource Manager by Using EM 10-17

Creating a Program by Using EM 11-7

Creating and Using Schedules 11-8

Using EM to Create Schedules 11-9

Calendaring Expressions 11-10

Creating a Job 11-12

Creating a Time-Based Job 11-13

Setting the Repeat Interval for a Job 11-15

Using Events with Jobs 11-16

Event-Based Scheduling 11-17

Creating an Event-Based Job 11-18

Events Raised by the Scheduler 11-19

Using Events Raised by Jobs 11-21

Using EM to Create Event-Based Schedules 11-22

Creating Complex Schedules 11-23

Privileges for Scheduler Components 11-24

Enabling and Disabling Scheduler Components 11-26

Managing Scheduler Components 11-27

Managing Scheduler Components with EM 11-29

Viewing Attributes of Scheduler Components 11-30

Viewing Job Execution Details 11-31

Viewing Job Logs 11-32

Scheduler Job Chain Concepts 11-33

Creating Chains 11-34

Creating a Chain Object 11-36

Defining Chain Steps 11-37

Defining Chain Rules 11-39

Specifying Chain Rule Conditions 11-40

Starting the Chain 11-42

Creating a Job Chain with EM 11-43

Managing Job Chains 11-45

xi

Managing Job Chains with EM 11-46

Monitoring Job Chains 11-47

Advanced Scheduler Concepts 11-48

Creating a Window 11-49

Prioritizing Jobs Within a Window 11-50

Creating a Job Class 11-52

Summary 11-53

Practice 11: Overview 11-54

12 Space Management

Objectives 12-2

Oracle Database 10g Solution: Self-Managing Database 12-3

Proactive Tablespace Monitoring: Overview 12-4

Tablespace Space Usage Monitoring 12-5

Edit Tablespace Space Usage Thresholds 12-6

Edit Tablespace Page 12-7

PL/SQL and Tablespace Space Usage Thresholds 12-8 Proactive Undo Tablespace Monitoring 12-10

Shrinking Segments: Overview 12-11

Shrinking Segments: Considerations 12-12

Shrinking Segments by Using SQL 12-13

Segment Shrink: Basic Execution 12-14

Segment Shrink: Execution Considerations 12-15

Database Control and Segment Shrink 12-16

Segment Advisor: Overview 12-17

Running the Segment Advisor Manually 12-18

Using the Segment Advisor with EM 12-19

Growth Trend Report 12-20

Segment Resource Estimation 12-21

Undo Management Page 12-22

Undo Advisor Page 12-23

Fast Ramp-Up 12-24

Sorted Hash Cluster: Overview 12-25

Sorted Hash Cluster: Example 12-26

Sorted Hash Cluster: Basic Architecture 12-27

Sorted Hash Cluster: Considerations 12-28

Viewing Tablespace Contents 12-29

Summary 12-30

Practice 12: Overview 12-31

13 Improved Very Large Database (VDLB) Support

Bigfile Tablespace: Usage Model 13-5

Creating Bigfile Tablespaces 13-6

SQL Statement Changes and Additions 13-7

BFTs and SQL Statements: Examples 13-8

Data Dictionary Changes and Additions 13-9

Bigfile Tablespaces and DBVERIFY 13-10

DBMS_UTILITY Package and BFTs 13-11

Migration and Bigfile Tablespaces 13-12

Extended ROWID Format and BFTs 13-13

DBMS_ROWID Package Changes 13-14

Temporary Tablespace Group: Overview 13-15

Temporary Tablespace Group: Benefits 13-16

Creating Temporary Tablespace Groups 13-17

Maintaining Temporary Tablespace Groups 13-18

Temporary Tablespace Group SQL: Examples 13-19

Data Dictionary Changes 13-21

Database Control: Creating a Partition 13-22

Database Control: Partition Maintenance 13-23

Partitioned IOT Enhancements 13-24

Local Partitioned Index Enhancements 13-25

Skipping Unusable Indexes 13-26

Hash-Partitioned Global Indexes: Overview 13-27

Contention Scenario 13-28

Hash-Partitioned Global Indexes: Benefits 13-29

Creating Hash-Partitioned Global Indexes 13-30

Adding and Coalescing Partitions 13-31

Range and Hash Global Index Commands 13-32

Operations Not Supported 13-33

Usage Example 13-34

Bitmap Index Storage Enhancements 13-35

DML Error Logging: Overview 13-36

DML Error Logging: Example 13-37

Oracle Database 10g Solution: Self-Managing Database 14-3

Flash Recovery Area 14-4

Defining Flash Recovery Area by Using Database Control 14-6 Defining a Flash Recovery Area by Using SQL 14-7

Flash Recovery Area Space Management 14-8

xiii

Backing Up Data Files to a Flash Recovery Area 14-9

Modifying the Flash Recovery Area 14-10

Backing Up the Flash Recovery Area 14-11

Dynamic Flash Recovery Area Views 14-12

Flash Recovery Area Columns in Other Views 14-14

Best Practices for the Database and Flash Recovery Area 14-15 Changes in SQL Statement Behavior 14-16

Fast Incremental Backup 14-18

Enabling Fast Incremental Backup 14-19

Monitoring Block Change Tracking 14-20

Incrementally Updated Backups 14-21

Oracle-Suggested Strategy 14-22

Incremental Roll Forward of a Database Copy 14-23

RMAN Backup Command Changes 14-24

Backup Type Enhancements by Using Database Control 14-26 Backup Maintenance 14-27

Backing Up the Entire Database 14-28

Backing Up Individual Tablespaces 14-29

Backing Up Data Files and Control Files 14-30

Implementing Fast Recovery 14-31

Automated Instance Creation and TSPITR 14-32

Auxiliary Location in EM 14-33

Creating Compressed Backups 14-34

Monitoring Compressed Backups 14-35

Simplified Recovery Through RESETLOGS 14-36

Recovery Through RESETLOGS: Changes 14-37

Recovering Data Files Not Backed Up 14-38

Dropping a Database 14-39

Placing All Files in Online Backup Mode 14-40

How Does File Status Affect BEGIN BACKUP? 14-41

Changes to the END BACKUP Command 14-42

RMAN and Configuration Changes 14-43

Automatic Channel Failover 14-44

RMAN Channel Support for the Grid 14-45

Enhanced RMAN Scripts 14-46

Setting Duration and Throttling Option 14-47

Database Control: Backup Reports 14-48

Oracle Secure Backup for Centralized Tape Backup Management 15-5 Oracle Secure Backup Administrative Domain 15-6

Oracle Secure Backup: Backup Management Overview 15-7

Oracle Secure Backup Catalog 15-8

Oracle Secure Backup Users 15-9

Predefined Classes 15-10

Oracle Secure Backup Interface Options 15-11

Managing Data to Be Protected 15-12

Oracle Secure Backup Media Concepts 15-13

Volume Set Recycling 15-14

Automated Device Management 15-15

Library Management Operations 15-16

Oracle Secure Backup: Installation 15-17

Installing Oracle Secure Backup Software 15-18

Administrative Server Installation: Example 15-19

Defining Your Administrative Server in EM 15-20

The Oracle Secure Backup Device and Media Page 15-21

Adding Devices 15-22

Manage Devices by Using EM 15-23

RMAN and Oracle Secure Backup 15-24

Accessing Oracle Secure Backup from RMAN 15-25

User Preauthorization 15-26

Database Backup Storage Selector 15-27

RMAN and Oracle Secure Backup Usage Model 15-28

Defining Database Storage Selector 15-29

Testing Your Tape Drives 15-30

Scheduling Backups by Using EM Database Control 15-31

Oracle-Suggested Strategy for Backups 15-32

Managing Tape Backups 15-33

Performing Database Recovery by Using Tape Backups 15-34

Backing Up File-System Files with Oracle Secure Backup 15-35 Oracle Secure Backup Web Tool 15-36

Oracle Secure Backup Data Set Scripts 15-37

Data Set Script: Examples 15-38

Data Set Organization 15-39

Creating Data Sets Using the Web Interface 15-40

File-System Files Backup Concepts 15-41

Oracle Secure Backup Jobs 15-42

Creating On-Demand Backup Requests 15-43

Sending Backup Requests to the Scheduler 15-44

Creating Backup Schedules 15-45

Creating Backup Triggers 15-46

Viewing Job Properties and Transcripts 15-47

xv

Restoring File-System Files with Oracle Secure Backup 15-48

Creating a Catalog-Based Restore Request 15-49

Sending Catalog-Based Restore Requests to the Scheduler 15-51

Listing All Backups of a Client 15-52

Summary 15-53

Practice 15: Overview 15-54

16 Flash Back Any Error

Objectives 16-2

Flashback Time Navigation 16-3

Flashback Error Correction 16-4

Flashback Database: Overview 16-5

Flashback Database: Eliminating Restore Time 16-6

Flashback Database Architecture 16-7

Configuring Flashback Database Using EM 16-8

Flashing Back Your Database by Using EM 16-9

Manually Configuring Flashback Database 16-10

Flashback Database: Examples 16-11

Monitoring Flashback Database 16-12

Excluding Tablespaces from Flashback Database 16-13

Flashback Database: Considerations 16-14

Flashing Back RESETLOGS 16-15

Flashback Drop: Overview 16-16

Recycle Bin 16-17

Flashing Back Dropped Tables by Using EM 16-18

Querying the Recycle Bin 16-19

Restoring Tables from the Recycle Bin 16-20

Recycle Bin: Automatic Space Reclamation 16-21

Recycle Bin: Manual Space Reclamation 16-22

Bypassing the Recycle Bin 16-23

Querying Dropped Tables 16-24

Flashback Drop: Considerations 16-25

Flashback Versions Query: Overview 16-26

Flashback Versions Query Using EM 16-27

Flashback Versions Query Syntax 16-28

Flashback Versions Query: Example 16-29

Flashback Versions Query: Considerations 16-30

Flashback Transaction Query: Overview 16-31

Flashback Transaction Query Using EM 16-32

Querying FLASHBACK_TRANSACTION_QUERY 16-33

Flashback Table: Example 16-38

Rolling Back a Flashback Table Operation 16-39

Flashback Table: Considerations 16-40

Restore Points: Overview 16-41

Guaranteed Restore Points 16-42

Guaranteed Restore Points: Properties 16-43

Restore Point Creation and Usage 16-44

Guaranteed Undo Retention 16-45

SCN and Time Mapping Enhancements 16-46

Granting Flashback Privileges 16-47

When to Use Flashback Technology 16-48

Flashback Technology: Benefits 16-49

Summary 16-50

Practice 16: Overview 16-51

17 General Space Management Enhancements

Objectives 17-2

Oracle Database 10g Solution: Self-Managing Database 17-3

SYSAUX Tablespace: Overview 17-4

SYSAUX Tablespace: Benefits 17-5

SYSAUX Occupants 17-6

CREATE DATABASE 17-7

ALTER TABLESPACE SYSAUX 17-8

SYSAUX Tablespace: General Usage 17-9

SYSAUX Occupants: Visualization 17-10

SYSAUX Occupants: Relocation 17-11

SYSAUX Occupants: Relocation Using SQL 17-12

Tablespace Rename: Overview 17-13

Tablespace Rename: Usage Example 17-14

Tablespace Rename: Considerations 17-15

Tablespace Rename: Best Practices 17-16

Default Permanent Tablespace: Overview 17-17

Designating a Default Permanent Tablespace 17-18

Default Permanent Tablespace: SQL Examples 17-19

Copying Files by Using the Database Server 17-20

Local Copy: Example 17-21

Transferring Files: Example 17-22

Copying Files: Considerations 17-23

Redo Logfile Size Advisor 17-24

Dropping an Empty Data File 17-26

Summary 17-27

Practice 17: Overview 17-28

xvii

18 Automatic Storage Management

Objectives 18-2

What Is Automatic Storage Management? 18-3

ASM: Key Features and Benefits 18-4

ASM: New Concepts 18-5

ASM: General Architecture 18-6

ASM Administration 18-8

ASM Instance Functionalities 18-9

Installing ASM: Overview 18-10

Transparent Multiversion Support 18-11

Creating a Database on ASM 18-12

Creating an ASM Instance on Its Own 18-13

ASM Instance Initialization Parameters 18-14

Accessing an ASM Instance 18-15

Dynamic Performance View Additions 18-16

ASM Home Page 18-17

ASM Performance Page 18-18

ASM Configuration Page 18-19

Starting Up an ASM Instance 18-20

Shutting Down an ASM Instance 18-21

ASM Administration 18-22

ASM Disk Group 18-23

Failure Group 18-24

Disk Group Mirroring 18-25

Disk Group Dynamic Rebalancing 18-26

ASM: Administration Page 18-27

Create Disk Group Page 18-28

Creating or Deleting Disk Groups 18-29

Adding Disks to Disk Groups 18-30

Miscellaneous Alter Commands 18-31

Monitoring Long-Running Operations by Using V$ASM_OPERATION 18-33 ASM Administration 18-34

ASM Files 18-35

ASM File Names 18-36

ASM File Name Syntax 18-37

ASM File Name Mapping 18-39

ASM File Templates 18-40

Template and Alias: Examples 18-41

Retrieving Aliases 18-42

SQL Commands and File Naming 18-43

Migrate Database To ASM Wizard 18-48

Manually Migrating Your Database to ASM 18-49 ASM and Transportable Tablespaces 18-50

ASM and XML DB: Overview 18-51

ASM Virtual Folder Hierarchy 18-52

ASM Virtual Folder: Typical Use 18-53

Summary 18-54

Practice 18: Overview 18-55

19 Maintaining Software

Objectives 19-2

Oracle Database 10g Upgrade Paths 19-3

Choosing an Upgrade Method 19-4

Advantages of Using DBUA 19-5

Manual Upgrade: Advantages and Disadvantages 19-6 New Preupgrade Information Utility 19-7

Oracle Database 10g: Simplified Upgrade 19-8

New Postupgrade Status Utility 19-9

Properly Prepared Upgrade 19-10

Using Database Upgrade Assistant 19-11

Recompiling Invalid Objects 19-12

Backing Up the Database Before Upgrade 19-13 Upgrade Summary 19-14

Performing the Manual Upgrade 19-15

Downgrading Using a Single Script 19-20

MetaLink Integration 19-21

OPatch Utility 19-22

OPatch Operations 19-24

Support for RAC Environments 19-25

OPatch Process Flow 19-26

Patch Conflict Detection 19-28

Summary 19-29

20 Security

Objectives 20-2

Virtual Private Database: Overview 20-3

Virtual Private Database: Enhancements 20-4

Column-Level VPD: Example 20-5

Creating a Column-Level Policy 20-6

Policy Types: Overview 20-7

Static Policies 20-8

Context-Sensitive Policies 20-9

Sharing Policy Functions 20-10

Auditing Mechanisms: Overview 20-11

xix

Uniform Audit Trails 20-12

Enhanced Enterprise User Auditing 20-13

Audit EM Page 20-14

Audit Enhancements 20-15

Fine-Grained Auditing: Enhancements 20-16

Fine-Grained Auditing Policy: Example 20-17

Audited DML Statement: Considerations 20-18

Transparent Data Encryption: Overview 20-19

Implementing Transparent Data Encryption 20-20 Existing Tables and Transparent Data Encryption 20-22 Transparent Data Encryption: Considerations 20-23 Data Pump and Transparent Data Encryption 20-24 RMAN Encrypted Backups: Overview 20-25

Transparent Mode Setup 20-26

Password Mode Setup 20-27

Dual Mode Setup 20-28

RMAN Encrypted Backups: Considerations 20-29 CONNECT Role Change 20-30

Wallet Support for Usernames and Passwords 20-31 Summary 20-32

Configurationless Client Connect 21-6

Simplified Shared-Server Configuration 21-8

Viewing the Dispatcher Configuration 21-9

Resumable Space Allocation Enhancements 21-10 Flushing the Buffer Cache 21-11

MAXTRANS and Maximum Concurrency 21-12

Large Object (LOB) Data Type Changes 21-13

Implicit Conversion Between CLOB and NCLOB 21-14 Regular Expression Support 21-15

UTL_MAIL: Examples 21-24

LogMiner Enhancements 21-25

Enhanced Initialization Parameters 21-26

Faster Instance Startup for Ultralarge Buffer Caches 21-27 Asynchronous COMMIT 21-28

How to Use Asynchronous COMMIT 21-29

Diagnosis of Hung or Extremely Slow Databases 21-30 Using Memory Access Mode 21-31

Using the Hang Analysis Page 21-32

Copyright © 2005, Oracle All rights reserved.

Oracle Secure Backup Overview

Copyright © 2005, Oracle All rights reserved.

15-2

Objectives

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

and how it benefits your environment

management concepts

and restore the Oracle database

file-system files

Oracle Database 10g: New Features for Administrators 15-3

Copyright © 2005, Oracle All rights reserved.

• Versions Oracle9i and later

• Real Application Clusters

Oracle Application Server configuration files

Oracle Collaboration Suite configuration files

Tape Library

Oracle Secure Backup Centralized Tape Backup Management

Backup and Restore

Data Protection to Tape for the Oracle Stack

Some of the options available for protecting your Oracle data are: backing up solely to disk, backing up to disk as a staging area for tape backups, or backing up directly to tape Disk backup and restore operations are generally faster than those of tape However, tape backups provide some advantages for long-term backup requirements, off-site storage, and portability

to move backups from one data center to another

Oracle Secure Backup provides tape backup management for the Oracle ecosystem, which includes:

• Oracle database protection to tape through integration with Recovery Manager

• Seamless support of Oracle Real Application Clusters (RAC)

• Central administration of distributed clients and media servers including:

- Oracle Application Servers

- Oracle Collaboration Suites

- Oracle Home and binaries

Copyright © 2005, Oracle All rights reserved.

15-4

The Customer Advantage Complete Oracle Solution

end-to-end backup solution for Oracle environments:

– Centralized backup management to tape for file system data and the Oracle database

– Provides most well-integrated media management layer for RMAN backups

– Backup of any data anywhere on the network

• A single technical support resource for the entire

backup solution expedites problem resolution.

• This ensures reliable data protection at lower cost

and complexity.

The Customer Advantage Complete Oracle Solution

Oracle’s current backup and recovery product for the database is Recovery Manager (RMAN),

a utility that has been part of the Oracle server since Oracle 8.0 Oracle Secure Backup

complements existing functionality in the following ways:

• Complete backup solution: Oracle Secure Backup provides data protection for the

database and nondatabase data to protect the whole Oracle environment

• Media management: Oracle Secure Backup provides the media management layer for

RMAN database backups to tape Before Oracle Secure Backup, customers had to

purchase expensive third-party media management products offering integration with RMAN tape backups

• Anywhere on the network: Oracle Secure Backup backs up data from multiple

network-attached computer systems to tertiary storage resources on the network Oracle Secure Backup supports diverse configurations of servers, clients, Network Attached Storage (NAS) servers, and tertiary storage devices and protects network storage

environments

Oracle Database 10g: New Features for Administrators 15-5

Copyright © 2005, Oracle All rights reserved.

15-5

Oracle Secure Backup for Centralized Tape Backup Management

Multivendor clients backed up over the network

LAN

Tape library

NAS

UNIX Linux Windows

Media servers locally backed up

Oracle Backup

Oracle Secure Backup:

Oracle Secure Backup for Centralized Tape Backup Management

The Oracle Secure Backup software offers centralized backup management of heterogeneous clients and servers through a single point of administration called the Oracle Secure Backup Administrative Server Through a central console that uses a consolidated backup catalog, you can easily manage backup policies, schedule backups for multiple platforms, and manage local and remote tape devices The configured machines and devices managed by an

administrative server make up the Oracle Secure Backup Administrative Domain as shown in the slide

The Oracle Secure Backup tape management system minimizes the complexity of managing diverse architectures and provides:

• Unified heterogeneous data protection for multiple platforms including UNIX (HP-UX, Tru64, AIX, and Solaris), Linux (Red Hat, SuSE), Windows (2000, XP, 2003) and NAS servers

• Flexible tape device configuration with options for single and multihosted libraries or Storage Area Networks (SAN) offering dynamic drive sharing for optimal resource utilization

• Support for major tape libraries and drives in SAN, GbE, and SCSI environments

• Client or server architecture providing centralized administration of distributed media servers over a local area network (LAN) or wide area network (WAN)

Copyright © 2005, Oracle All rights reserved.

– Has standard access mode only

• Media or SAN server:

– Transfers data to or from attached devices

– Has standard (OB) or NDMP access modes

Data to back up

Oracle Secure Backup Administrative Domain

An administrative domain has one administrative server, one or more clients, and one or more media servers

• An administrative server is a machine in your administrative domain that contains a

copy of the Oracle Secure Backup software and the catalog files that contain

configuration settings and store backup history The administrative server runs the

Scheduler, which starts and monitors jobs within the administrative domain

• A media server or SAN server is a machine that has one or more secondary storage

devices, such as a tape library, connected to it A media server transfers data to or from attached devices

• A client is a machine whose locally accessed data is backed up by Oracle Secure Backup.

Each configured machine is characterized by the following access modes:

• Standard (OB): A standard, configured machine runs the Oracle Secure Backup

daemons that manage the client or server from a backup and restore perspective

• NDMP: A Network Data Management Protocol host is a storage appliance from a

third-Oracle Database 10g: New Features for Administrators 15-7

Copyright © 2005, Oracle All rights reserved.

15-7

Oracle Secure Backup:

Backup Management Overview

domain:

– Consolidated catalog

– Users and privileges

• Ease of administration with multiple interface

options, backup policies, and much more

– File system and Oracle database

– Management through policies

• Flexible configuration options

Oracle Secure Backup: Backup Management Overview

Oracle Secure Backup provides data protection to tape for the Oracle database and file-system data Addressing the needs of DBAs and system administrators, Oracle Secure Backup

delivers reliability, scalability, and ease of use ideally suited for workgroups and Oracle

ecosystems

• Typical IT environments are heterogeneous and need the same level of protection to tape Oracle Secure Backup minimizes the complexity of managing those diverse

architectures from a central administrative server

• Providing maximum flexibility and ease of use, Oracle Secure Backup is integrated with Oracle Enterprise Manager (EM) for database backups and most administrative tasks File system backups are effectively managed using an intuitive Web tool and/or a

uniform command interface

• Security to control unauthorized access to backups is key in protecting the data Oracle Secure Backup provides password protection and user classes to govern backup and recovery operation permissions Oracle Secure Backup is hardened against buffer

overflow attacks

• Tightly integrated with RMAN, Oracle Secure Backup provides performant database backup and recovery through familiar Oracle Enterprise Manager and/or RMAN

interfaces

• With configurable management policies and flexible device configuration and

scheduling options, Oracle Secure Backup delivers a cohesive data protection tape

management tool

Copyright © 2005, Oracle All rights reserved.

Oracle Secure Backup Catalog

Oracle Secure Backup maintains its own centralized catalog on the administrative server The Oracle Secure Backup catalog contains all the information used to define your configuration

It also includes metadata relating to your backup and restore operations The slide shows you the tree structure of directories installed by Oracle Secure Backup on an administrative server Oracle Secure Backup organizes its catalog in a hierarchical manner The admin directory contains the administrative domain catalogs As shown in the slide, the config directory contains many subdirectories representing objects that Oracle Secure Backup maintains In each of these directories, Oracle Secure Backup maintains files containing the characteristics

of the corresponding objects

As shown in the slide, it is recommended to back up the Oracle Secure Backup installation tree on your administrative server on a regular basis That way, your Oracle Secure Backup data will not be lost in case you loose your administrative server

Note: For formatting reasons, the slide does not represent the complete set of directories used

Oracle Database 10g: New Features for Administrators 15-9

Copyright © 2005, Oracle All rights reserved.

15-9

Oracle Secure Backup Users

Name and password

Class privileges

UNIX username and group

Windows domain account and password Email address

NDMP access authorization

Given name

Preauthentication

user information

Oracle Secure Backup user

Oracle Secure Backup Users

Oracle Secure Backup manages its own catalog of users and their corresponding rights to maintain a consistent user identity across the various hosts (UNIX, Linux, and Windows) of your administrative domain Although you can assign user names and passwords that are identical to those of existing OS users, the namespace for Oracle Secure Backup users is distinct from the namespaces of existing OS users Here is a description of the parameters that must be specified when creating Oracle Secure Backup users:

• The name of the Oracle Secure Backup user as well as its password

• The Oracle Secure Backup class associated to this user

• A UNIX or Windows user name and the corresponding information This user name is used by Oracle Secure Backup’s unprivileged operations to access file-system data on your clients An unprivileged operation is constrained by the rights of the UNIX user or Windows account having that identity

• Whether the Oracle Secure Backup user is permitted to log in to an NDMP server This login is done using an external client program

• An e-mail address used to send Oracle Secure Backup operation notifications and

reports

• A given name This is more like a comment

• Possibility to specify preauthorized user information This allows the use of Oracle Secure Backup without going through the normal Oracle Secure Backup login

requirements

Note: Configuring users is best accomplished using the Web tool or command-line interface.

Copyright © 2005, Oracle All rights reserved.

15-10

Predefined Classes

User can perform Oracle database backups and restores

Access Oracle Secure Backups (database)

Modify any job, regardless of its owner

List any job, regardless of its owner

Manage devices and change device state

Query and display information about devices

Receive e-mail describing internal errors

Receive e-mail requesting operator assistance

Perform restores as privileged user

Perform restores as self

Modify any jobs, owned by user

List any jobs, owned by user

Perform backups as privileged user

Perform backups as self

Modify administrative domain’s configuration

Modify own user name and password

Display administrative domain's configuration

Browse backup catalogs with this access

READER ORACLE

USER OPERATOR

ADMIN Rights

• Admin: Class used for overall administration of a domain The admin class has all the

rights and privileges needed to modify domain configurations and perform backup and restore operations

• Operator: Class used for standard day-to-day operations The operator class lacks

configuration privileges but has all the rights needed for backup and restore operations

as well as device management browsing capabilities

• User: Class assigned to specific users giving them permission to interact in a limited

way with their domains This class is reserved for users who need to browse their own data within an index and perform user-based restores

• Oracle: Similar to the operator class with specific privileges to modify Oracle database

configuration settings as well as to perform Oracle database backups

Oracle Database 10g: New Features for Administrators 15-11

Copyright © 2005, Oracle All rights reserved.

15-11

Oracle Secure Backup Interface Options

Oracle Secure Backup

obtool RMAN

Web tool

EM

Database operations

File system operations

Oracle Secure Backup Interface Options

As shown in the slide, you can access Oracle Secure Backup in four different ways depending

on what you want to do:

• Management operations for administering the domain, such as adding or managing devices, is best accomplished using Enterprise Manager The Oracle Secure Backup Web tool or command line is also available for administrative management tasks

including adding clients, and configuring users and classes

• Oracle database backup and restore operations are managed using the Oracle Enterprise Manager or RMAN interface

• File system backup and restore operation are managed using the Oracle Secure Backup Web tool or the command-line interface

Note: In terms of backup and recovery operations, the difference between the Oracle Secure

Backup Web interface and obtool is the same as the difference between the EM interface and RMAN

Copyright © 2005, Oracle All rights reserved.

15-12

Managing Data to Be Protected

Intuitive Enterprise Manager scheduling interface

Use RMAN backup levels: Full and incremental

RMAN backup sets

Oracle Database

Flexible date/time calendar–based scheduling

File System Data

Managing Data to Be Protected

Managing the backup infrastructure of file-system data and Oracle database data is easily administered with Oracle Secure Backup and RMAN Defining what data to backup is

conceptually similar for file-system and database data Both require that you, the user, define what to include in the backup For the database, you use the RMAN backups sets created using RMAN or Enterprise Manager For file systems, Oracle Secure Backup uses data sets Defining file system data sets is easily accomplished using the Oracle Secure Backup Web tool

After defining what data to back up, you must determine what type of backups are most appropriate to meet your backup and restore requirements Oracle Secure Backup offers multiple backup levels for file-system backups including full backup levels, multiple

incremental levels, and an off-site backup level The off-site level is actually a full backup performed without interfering with any incremental backup strategies Oracle Secure Backup also provides flexible scheduling options enabling you to determine ongoing backup

Oracle Database 10g: New Features for Administrators 15-13

Copyright © 2005, Oracle All rights reserved.

15-13

Oracle Secure Backup Media Concepts

Media family Volume set Volume Backup image

Set of tapes containing backup images

Product of one backup operation

Tape

Means to manage the content of a volume set

Oracle Secure Backup Media Concepts

Oracle Secure Backup organizes backups that it creates in a simple hierarchy that comprises the following concepts:

• A backup image (archive) is the product of a backup operation Basically, it can be seen

as the list of files that are backed up in one operation

• A volume is a single unit of media such as an 8 mm tape

• A volume set is a group of volumes that a backup image spans

• A media family is a named classification of volumes that share some common attributes, such as the way volumes are named, and the policies used to write and keep data stored

in the media family volumes

So, when you back up files by using Oracle Secure Backup, you generate a volume set that has some common characteristics defined by the corresponding media family you have

associated with your backup operation

Note: The graphic illustrates these concepts from the most logical one to the most physical

one

Copyright © 2005, Oracle All rights reserved.

Volume set closed

Time Updates allowed Updates forbidden

Recycling File-System File Volumes

Exceed expire duration

Volume set

Recycling Backup Pieces Volumes

Backup piece

Backup piece

Backup piece

Backup piece

Expired Expired Expired Expired

Manually deleted

Or

Volume Set Recycling

Oracle Secure Backup has two volume-recycling concepts:

• Recycling volumes containing file-system file backups: The retention period for file

system backups is managed at the volume level in that a volume (tape) or volume set containing one or more file system backups may not be overwritten until the retention period for the volume has expired Oracle Secure Backup continues to append backups

to the volume set until its write window period has expired, at which time it considers the volume set closed to further updates After the volume set is closed, its data are kept for the retention duration, then expired and automatically available to be overwritten The retention period is the total time of the user-defined write window plus retain

duration

• Recycling volumes containing backup pieces: Oracle Secure Backup uses

content-managed volume recycling for Oracle Database backups, where each backup piece is managed discretely, not at the volume level There are two ways in which backup pieces may expire:

1 A backup administrator manually deletes the piece from the backup catalog

Oracle Database 10g: New Features for Administrators 15-15

Copyright © 2005, Oracle All rights reserved.

15-15

Automated Device Management

tape libraries.

– Accepts SCSI commands from the library to:

– Manage the tapes inventory – Move tapes to or from storage elements and drives

– Automates tape drive cleaning

– Supports bar code readers and media verification

NDMP v3 and v4 capable servers

Automated Device Management

Oracle Secure Backup automates the management of tape libraries, enabling efficient and reliable use of its capabilities (including bar code readers) Oracle Secure Backup

communicates with a tape library controlling the robotics to facilitate the management of tapes within the library A tape library is often referred to as a robotic tape device,

autochanger, or medium changer A list of supported tape drives and libraries is available on OTN

A library accepts SCSI (small computer system interface) commands to move media between storage locations and drives Oracle Secure Backup uses the following SCSI terms to describe basic components of libraries:

• A storage element (se) contains a volume when it is not in use

• An import-export element (iee) or mail slot is used to move volumes into and out of the library without opening the door Availability of an iee is dependent by library Some offer a media access port, whereas some require manual action by the operator to open the door, and remove a tape from a slot in the library

• A medium transport element (mte) moves a volume from a storage element to another element, such as a drive

• A data transfer element (dte) is, for Oracle Secure Backup’s purposes, a tape drive.Each element has a user-defined name that Oracle Secure Backup uses to identify it The first storage element, for example, is usually called se1, the first tape drive is dte1

Copyright © 2005, Oracle All rights reserved.

15-16

Library Management Operations

Storage elements insertvol

Tape drives

Loadvol unloadvol

movevol

Library extractvol

Library Management Operations

The illustration in the slide shows you a library with its storage elements and drives The following are some basic operations that you can perform on the components of a library

• You can express that you have inserted one or more volumes into the library’s storage elements

• Similarly, you can extract one or more volumes from a tape library’s storage elements This command notifies Oracle Secure Backup that you are removing a volume manually from the library

• You can also load a volume from a storage element into a drive, to be ready to start backup operations

• Similarly, you can unload a volume from a drive to a particular storage element

• You can also move one volume from one storage element to another

Note: For more information about the possible library commands, refer to the Oracle Secure

Backup Reference guide.

Oracle Database 10g: New Features for Administrators 15-17

Copyright © 2005, Oracle All rights reserved.

15-17

Oracle Secure Backup: Installation

Media servers

Software installation

Administrative domain definition

Device definition/

discovery

Administrative server

Oracle Secure Backup only

Administrative

server server Media Client

Oracle Secure Backup/NDMP

Oracle Secure Backup: Installation

The installation and configuration of your administrative domain is generally done in three steps:

1 Install the Oracle Secure Backup software on each of your hosts except the ones on which NDMP daemons are already running This can be done by either using a CD-ROM or by downloading the software from OTN

2 Make sure that your complete administrative domain is defined on the administrative server This involves defining all media servers, client servers, and NAS (Network Attached Storage) filers You do this directly from the administrative server, which is defined during the software installation process

3 Make the administrative server aware of the tape devices that exist in your

administrative domain This third step is reserved for media servers only, and it allows you to configure the SCSI and Fiber Channel devices (libraries and tape drives) directly attached to an Oracle Secure Backup host in your administrative domain, or it allows you to discover the libraries and tape drives attached to a Network Attached Storage (NAS) Filer so that the filer can communicate with Oracle Secure Backup