Skip Headers
Oracle® Database High Availability Best Practices
10
g
Release 2 (10.2)
Part Number B25159-01
Home
Book List
Index
Master Index
Contact Us
Next
View PDF
Contents
List of Figures
List of Tables
Title and Copyright Information
Preface
Audience
Documentation Accessibility
Related Documents
Conventions
1
Introduction to High-Availability Best Practices
1.1
Oracle Database High-Availability Architecture
1.2
Oracle Database High-Availability Best Practices
1.3
Oracle Maximum Availability Architecture
1.4
Operational Best Practices
2
Configuring for High-Availability
2.1
Configuring Storage
2.1.1
Evaluate Database Performance Requirements and Storage Performance Capabilities
2.1.2
Use Automatic Storage Management (ASM) to Manage Database Files
2.1.3
Use a Simple Disk and Disk Group Configuration
2.1.4
Use Disk Multipathing Software to Protect from Path Failure
2.1.5
Use Redundancy to Protect from Disk Failure
2.1.6
Consider HARD-Compliant Storage
2.2
Configuring Oracle Database 10
g
2.2.1
Requirements for High Availability
2.2.1.1
Enable ARCHIVELOG Mode
2.2.1.2
Enable Block Checksums
2.2.2
Recommendations for High Availability and Fast Recoverability
2.2.2.1
Configure the Size of Redo Log Files and Groups Appropriately
2.2.2.2
Use a Flash Recovery Area
2.2.2.3
Enable Flashback Database
2.2.2.4
Use Fast-Start Fault Recovery to Control Instance Recovery Time
2.2.2.5
Enable Database Block Checking
2.2.2.6
Set DISK_ASYNCH_IO
2.2.2.7
Set LOG_BUFFER to At Least 8 MB
2.2.2.8
Use Automatic Shared Memory Management
2.2.2.9
Increase PARALLEL_EXECUTION_MESSAGE_SIZE
2.2.2.10
Tune PARALLEL_MIN_SERVERS
2.2.2.11
Disable Parallel Recovery
2.2.3
Recommendations to Improve Manageability
2.2.3.1
Use Automatic Performance Tuning Features
2.2.3.2
Use a Server Parameter File
2.2.3.3
Use Automatic Undo Management
2.2.3.4
Use Locally Managed Tablespaces
2.2.3.5
Use Automatic Segment Space Management
2.2.3.6
Use Temporary Tablespaces and Specify a Default Temporary Tablespace
2.2.3.7
Use Resumable Space Allocation
2.2.3.8
Use Database Resource Manager
2.3
Configuring Oracle Database 10
g
with RAC
2.3.1
Connect to Database using Services and Virtual Internet Protocol (VIP) Address
2.3.2
Use Oracle Clusterware to Manage the Cluster and Application Availability
2.3.3
Use Client-Side and Server-Side Load Balancing
2.3.4
Mirror Oracle Cluster Registry (OCR) and Configure Multiple Voting Disks
2.3.5
Regularly Back Up OCR to Tape or Offsite
2.3.6
Verify That CRS and RAC Use Same Interconnect Network
2.3.7
Configure All Databases for Maximum Instances in the Cluster
2.4
Configuring Oracle Database 10
g
with Data Guard
2.4.1
Physical or Logical Standby
2.4.1.1
Benefits of a Physical Standby Database
2.4.1.2
Benefits of a Logical Standby Database
2.4.1.3
Determining Which Standby Type Is Best for Your Application
2.4.2
Data Protection Mode
2.4.3
Number of Standby Databases
2.4.4
General Configuration Best Practices for Data Guard
2.4.4.1
Enable Flashback Database for Easy Reinstantiation After Failover
2.4.4.2
Use FORCE LOGGING Mode
2.4.4.3
Use Data Guard Broker
2.4.4.4
Use a Simple, Robust Archiving Strategy and Configuration
2.4.4.5
Use Standby Redo Logs and Configure Size Appropriately
2.4.4.6
Parameter Configuration Example
2.4.5
Redo Transport Services Best Practices
2.4.5.1
Conduct Performance Assessment with Proposed Network Configuration
2.4.5.2
Best Practices for Primary Database Throughput
2.4.5.3
Best Practices for Network Configuration and Highest Network Redo Rates
2.4.6
Log Apply Services Best Practices
2.4.6.1
Redo Apply Best Practices for Physical Standby Databases
2.4.6.2
SQL Apply Best Practices for Logical Standby Databases
2.4.7
Role Transition Best Practices
2.4.7.1
Role Transition During Switchover
2.4.7.2
Role Transition During Failover
2.4.8
Maintaining a Physical Standby Database as a Clone
2.4.9
Recommendations on Protecting Data Outside of the Database
2.4.10
Assessing Data Guard Performance
2.5
Configuring Backup and Recovery
2.5.1
Use Oracle Database Features and Products
2.5.1.1
Use Recovery Manager to Back Up Database Files
2.5.1.2
Use Oracle Secure Backup
2.5.1.3
Use Restore Points
2.5.2
Configuration and Administration
2.5.2.1
Understand When to Use Backups
2.5.2.2
Determine a Backup Frequency
2.5.2.3
Use an RMAN Recovery Catalog
2.5.2.4
Enable Block Change Tracking for Incremental Backups
2.5.2.5
Enable Autobackup for Control File and Server Parameter File
2.5.3
Backup to Disk
2.5.3.1
Determine Disk Backup Methods
2.5.3.2
Create Backups in NOCATALOG Mode and RESYNC CATALOG Afterwards
2.5.3.3
Create Database Backups on Disk in the Flash Recovery Area
2.5.3.4
In a Data Guard Environment, Back Up to Flash Recovery Area on All Sites
2.5.4
Backup to Tape
2.5.4.1
Create Tape Backups from the Flash Recovery Area
2.5.4.2
Maintain Offsite Backups
2.5.5
Backup and Recovery Maintenance
2.5.5.1
Regularly Check Database Files for Corruption
2.5.5.2
Periodically Test Recovery Procedures
2.5.5.3
Regularly Backup the Recovery Catalog Database
2.6
Configuring Fast Application Failover
2.6.1
Configuring Clients for Failover
2.6.2
Client Failover in a RAC Database
2.6.3
Failover from a RAC Primary Database to a Standby Database
3
Monitoring Using Oracle Grid Control
3.1
Overview of Monitoring and Detection for High Availability
3.2
Using Oracle Grid Control for System Monitoring
3.2.1
Set Up Default Notification Rules for Each System
3.2.2
Use Database Target Views to Monitor Health, Availability, and Performance
3.2.3
Use Event Notifications to React to Metric Changes
3.2.4
Use Events to Monitor Data Guard System Availability
3.3
Managing the High-Availability Environment with Oracle Grid Control
3.3.1
Check Oracle Grid Control Policy Violations
3.3.2
Use Oracle Grid Control to Manage Oracle Patches and Maintain System Baselines
3.3.3
Use Oracle Grid Control to Manage Data Guard Targets
4
Managing Outages
4.1
Outage Overview
4.1.1
Unscheduled Outages
4.1.1.1
Managing Unscheduled Outages on the Primary Site
4.1.1.2
Managing Unscheduled Outages on the Secondary Site
4.1.2
Scheduled Outages
4.1.2.1
Managing Scheduled Outages on the Primary Site
4.1.2.2
Managing Scheduled Outages on the Secondary Site
4.1.2.3
Preparing for Scheduled Outages on the Secondary Site
4.2
Recovering from Unscheduled Outages
4.2.1
Complete Site Failover
4.2.1.1
When to Use Complete Site Failover
4.2.1.2
Best Practices for Complete Site Failover
4.2.1.3
Repair Solution
4.2.2
Database Failover with a Standby Database
4.2.2.1
When To Perform a Data Guard Failover
4.2.2.2
Best Practices for Implementing Data Guard Failover
4.2.3
Database Switchover with a Standby Database
4.2.3.1
When to Perform a Data Guard Switchover
4.2.3.2
Best Practices for Implementing Data Guard Switchover
4.2.4
RAC Recovery for Unscheduled Outages
4.2.4.1
Automatic Instance Recovery for Failed Instances
4.2.4.2
Automatic Service Relocation
4.2.4.3
Oracle Cluster Registry
4.2.5
Application Failover
4.2.6
ASM Recovery After Disk and Storage Failures
4.2.6.1
ASM Instance Failure
4.2.6.2
ASM Disk Failure
4.2.6.3
Data Area Disk Group Failure
4.2.6.4
Flash Recovery Area Disk Group Failure
4.2.7
Recovering from Data Corruption (Data Failures)
4.2.7.1
Use Data Guard to Recover From Data Corruption and Data Failure
4.2.7.2
Use RMAN Block Media Recovery
4.2.7.3
Use RMAN Data File Media Recovery
4.2.7.4
Re-Create Objects Manually
4.2.8
Recovering from Human Error
4.2.8.1
Resolving Table Inconsistencies
4.2.8.2
Resolving Row and Transaction Inconsistencies
4.2.8.3
Resolving Database-Wide Inconsistencies
4.3
Restoring Fault Tolerance
4.3.1
Restoring Failed Nodes or Instances in a RAC Cluster
4.3.1.1
Recovering Service Availability
4.3.1.2
Considerations for Client Connections After Restoring a RAC Instance
4.3.2
Restoring a Standby Database After a Failover
4.3.2.1
Restoring a Standby Database After a Fast-Start Failover
4.3.2.2
Reinstating a Standby Database Using Enterprise Manager After a Failover
4.3.3
Restoring ASM Disk Groups after a Failure
4.3.4
Restoring Fault Tolerance After Planned Downtime on Secondary Site or Clusterwide Outage
4.3.5
Restoring Fault Tolerance After a Standby Database Data Failure
4.3.6
Restoring Fault Tolerance After the Production Database Was Opened Resetlogs
4.3.7
Restoring Fault Tolerance After Dual Failures
4.4
Eliminating or Reducing Downtime for Scheduled Outages
4.4.1
Storage Maintenance
4.4.1.1
Migrating to ASM Storage
4.4.1.2
Adding and Removing Storage
4.4.2
RAC Database Patches
4.4.2.1
Best Practices To Minimize Downtime
4.4.3
Database Upgrades
4.4.3.1
Database Upgrade Assistant
4.4.3.2
Data Guard SQL Apply (Logical Standby)
4.4.3.3
Oracle Streams
4.4.3.4
Transportable Tablespaces
4.4.4
Database Platform or Location Migration
4.4.4.1
Transportable Database
4.4.4.2
Oracle Streams
4.4.4.3
Oracle Data Pump
4.4.4.4
Transportable Tablespaces
4.4.4.5
Data Guard Redo Apply (Physical Standby Database)
4.4.5
Online Database and Application Upgrades
4.4.6
Database Object Reorganization
4.4.7
System Maintenance
5
Migrating to an MAA Environment
5.1
Overview of Migrating to MAA
5.2
Migrating to RAC from a Single Instance
5.3
Adding a Data Guard Configuration to a RAC Primary
A
Database SPFILE and Oracle Net Configuration File Samples
A.1
SPFILE Samples
A.2
Oracle Net Configuration Files
A.2.1
SQLNET.ORA Example for All Hosts Using Dynamic Instance Registration
A.2.2
LISTENER.ORA Example for All Hosts Using Dynamic Instance Registration
A.2.3
TNSNAMES.ORA Example for All Hosts Using Dynamic Instance Registration
Glossary
Index
Scripting on this page enhances content navigation, but does not change the content in any way.
