Go to main content
1/24
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 and Storage Capacity Requirements
2.1.2
Use Oracle Storage Grid
2.1.2.1
Oracle Storage Grid Best Practices for Unplanned Outages
2.1.2.2
Oracle Storage Grid Best Practices for Planned Maintenance
2.1.3
Use Automatic Storage Management (ASM) to Manage Database Files
2.1.4
Use ASMLib On Platforms Where It Is Available
2.1.5
Use a Simple Disk and Disk Group Configuration
2.1.6
Use Disk Multipathing Software to Protect from Path Failure
2.1.7
Use Redundancy to Protect from Disk Failure
2.1.8
Use Clustered Automatic Storage Management (ASM) to Enable the Storage Grid
2.1.9
Configure a Separate Automatic Storage Management (ASM) Home
2.1.10
Allow Automatic Memory Management with MEMORY_TARGET Parameter
2.1.11
Ensure Disks in the Same Disk Group Have the Same Characteristics
2.1.12
Use SYSASM for ASM Authentication
2.1.13
Use a Single Command to Mount Multiple Disk Groups
2.1.14
Use a Single Command to Add or Remove Storage
2.1.15
Use Failure Groups When Using ASM Redundancy
2.1.16
Increase Allocation Units for Large Databases
2.1.17
Use Disk Labels
2.1.18
Check Disk Groups for Imbalance
2.1.19
Set Rebalance to the Maximum Limit That Will Not Affect Service Levels
2.1.20
Use ASMCMD to Ease Manageability of ASM
2.1.21
Use Oracle Recovery Manager or Oracle Data Guard to Migrate to ASM
2.1.22
Set the DISK_REPAIR_TIME Disk Group Attribute Appropriately
2.1.23
Proactively Mine Vendor Logs for Disk Errors
2.2
Configuring Oracle Database 11
g
2.2.1
Recommendations for High Availability and Fast Recoverability
2.2.1.1
Enable ARCHIVELOG Mode
2.2.1.2
Configure the Size of Redo Log Files and Groups Appropriately
2.2.1.3
Use a Flash Recovery Area
2.2.1.4
Enable Flashback Database
2.2.1.5
Use Fast-Start Fault Recovery to Control Instance Recovery Time
2.2.1.6
Configure to Protect from Data Corruption
2.2.1.7
Use the Data Recovery Advisor
2.2.1.8
Set DISK_ASYNCH_IO
2.2.1.9
Set LOG_BUFFER to at Minimum of 8 MB
2.2.1.10
Use Automatic Shared Memory Management
2.2.1.11
Disable Parallel Recovery for Instance Recovery
2.2.2
Recommendations to Improve Manageability
2.2.2.1
Use Data Recovery Adviser to Detect, Analyze and Repair Data Failures
2.2.2.2
Use Automatic Performance Tuning Features
2.2.2.3
Use a Server Parameter File
2.2.2.4
Use Automatic Undo Management
2.2.2.5
Use Locally Managed Tablespaces
2.2.2.6
Use Automatic Segment Space Management
2.2.2.7
Use Temporary Tablespaces and Specify a Default Temporary Tablespace
2.2.2.8
Use Resumable Space Allocation
2.2.2.9
Use Database Resource Manager
2.3
Configuring Oracle Database 11
g
with Oracle Clusterware
2.3.1
Oracle Clusterware Best Practices
2.3.1.1
Oracle Clusterware Release Compatibility
2.3.1.2
Capacity Planning
2.3.1.3
Use a Local Home for ASM, Oracle Database, and Oracle Clusterware
2.3.1.4
Out-of-Place Patch Set Installation with Cloning
2.3.1.5
Client Configuration and Migration
2.3.1.6
Use Separate Home Directory Locations for ASM and Oracle Database
2.3.1.7
Run the Listener Out of the Most Recent Oracle Home or ASM Home
2.3.1.8
Ensure Services are Highly Available
2.3.1.9
Connect to Database Using Services and Virtual Internet Protocol (VIP) Address
2.3.1.10
Use Client-Side and Server-Side Load Balancing
2.3.1.11
Mirror Oracle Cluster Registry (OCR) and Configure Multiple Voting Disks
2.3.1.12
Regularly Back Up OCR to Tape or Offsite
2.3.1.13
Verify That Oracle Clusterware and Oracle RAC Use the Same Interconnect Network
2.3.2
Cold Failover Cluster Best Practices
2.4
Configuring Oracle Database 11
g
with Oracle RAC
2.4.1
Understand the Instance Recovery Target and Optimize (if Required)
2.4.2
Maximize the Number of Processes Performing Transaction Recovery
2.4.3
Ensure Asynchronous I/O Is Enabled
2.4.4
Redundant Dedicated Connection Between the Nodes
2.5
Configuring Oracle Database 11
g
with Oracle RAC on Extended Clusters
2.5.1
Spread the Workload Evenly Across the Sites in the Extended Cluster
2.5.2
Configure the Nodes to Be Within the Proximity of a Metropolitan Area
2.5.3
Use Host-Based Storage Mirroring with ASM Normal or High Redundancy
2.5.4
Add a Third Voting Disk to Host the Quorum Disk
2.5.5
Additional Deployment Considerations for Extended Clusters
2.6
Configuring Oracle Database 11
g
with Oracle Data Guard
2.6.1
Determine Which Type of Standby Database Is Best for Your Application
2.6.2
Choose the Appropriate Level of Data Protection
2.6.3
Implement Multiple Standby Databases
2.6.4
General Configuration Best Practices for Data Guard
2.6.4.1
Use Recovery Manager to Create Standby Databases
2.6.4.2
Enable Flashback Database for Reinstatement After Failover
2.6.4.3
Use FORCE LOGGING Mode
2.6.4.4
Use the Data Guard Broker
2.6.4.5
Use a Simple, Robust Archiving Strategy and Configuration
2.6.4.6
Use Standby Redo Logs and Configure Size Appropriately
2.6.5
Redo Transport Services Best Practices
2.6.5.1
Conduct Performance Assessment with Proposed Network Configuration
2.6.5.2
Best Practices for Primary Database Throughput
2.6.5.3
Best Practices for Network Configuration and Highest Network Redo Rates
2.6.5.4
Best Practices for Redo Transport Compression
2.6.6
Log Apply Services Best Practices
2.6.6.1
Redo Apply Best Practices for Physical Standby Databases
2.6.6.2
SQL Apply Best Practices for Logical Standby Databases
2.6.7
Role Transition Best Practices
2.6.7.1
Switchovers
2.6.7.2
Failovers
2.6.8
Best Practices for Snapshot Standby Database
2.6.9
Best Practices for Deploying Multiple Standby Databases
2.6.10
Best Practices for Real-Time Query (Oracle Active Data Guard Option)
2.6.10.1
Enabling Real-Time Query On a Consistent Standby Database
2.6.10.2
Monitoring Real-Time Query
2.6.11
Recommendations for Protecting Data Outside of the Database
2.6.12
Assess Data Guard Performance
2.7
Configuring Backup and Recovery
2.7.1
Use Oracle Database Features and Products
2.7.1.1
Use Recovery Manager to Back Up Database Files
2.7.1.2
Use Oracle Secure Backup for Backups to Tape
2.7.1.3
Use Restore Points
2.7.2
Configuration and Administration
2.7.2.1
Understand When to Use Backups
2.7.2.2
Determine a Backup Frequency
2.7.2.3
Use an RMAN Recovery Catalog
2.7.2.4
Create Backups in NOCATALOG Mode and RESYNC CATALOG Afterwards
2.7.2.5
Enable Block Change Tracking for Incremental Backups
2.7.2.6
Enable Autobackup for the Control File and Server Parameter File
2.7.2.7
Offload Backups to a Physical Standby Database
2.7.3
Backup to Disk
2.7.4
Backup to Tape
2.7.4.1
Create Tape Backups from the Flash Recovery Area
2.7.4.2
Create Fast Tape Backups Using Oracle Secure Backup
2.7.4.3
Maintain Offsite Backups
2.7.5
Backup and Recovery Maintenance
2.7.5.1
Regularly Check Database Files for Corruption
2.7.5.2
Periodically Test Recovery Procedures
2.7.5.3
Regularly Backup the Recovery Catalog Database
2.8
Configuring Oracle Streams
2.8.1
Preparing Oracle Streams Configurations
2.8.2
Finalizing and Verifying the Oracle Streams Configuration
2.9
Configuring Fast Connection Failover
2.9.1
Configure JDBC and OCI Clients for Failover
2.9.2
Configure Client Failover in an Oracle RAC Environment
2.9.3
Configure Failover in an Oracle Data Guard Environment
2.9.4
Prevent Login Storms
2.10
Using Oracle Enterprise Manager Grid Control
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
Oracle Grid Control Home Page
3.2.2
Set Up Default Notification Rules for Each System
3.2.3
Use Database Target Views to Monitor Health, Availability, and Performance
3.2.4
Use Event Notifications to React to Metric Changes
3.2.5
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 Grid Control to Manage Oracle Patches and Maintain System Baselines
3.3.3
Manage Database Availability with the High Availability Console
3.3.4
Configure High Availability Solutions with MAA Advisor
4
Managing Unscheduled Outages
4.1
Overview of Unscheduled Outages
4.1.1
Managing Unscheduled Outages on the Primary Site
4.1.2
Managing Unscheduled Outages on the Standby 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 Fast-Start Failover
4.2.2.3
Best Practices for Performing Manual Failover
4.2.3
Oracle RAC Recovery for Unscheduled Outages
4.2.3.1
Automatic Instance Recovery for Failed Instances
4.2.3.2
Automatic Service Relocation
4.2.3.3
Oracle Cluster Registry
4.2.4
Application Failover
4.2.5
ASM Recovery After Disk and Storage Failures
4.2.5.1
ASM Instance Failure
4.2.5.2
ASM Disk Failure
4.2.5.3
Data Area Disk Group Failure
4.2.5.4
Flash Recovery Area Disk Group Failure
4.2.6
Recovering from Data Corruption (Data Failures)
4.2.6.1
Use Data Recovery Advisor to Automate Failure Diagnosis and Repair
4.2.6.2
Use Data Guard to Recover From Data Corruption and Data Failure
4.2.6.3
Use RMAN Block Media Recovery
4.2.6.4
Use RMAN Data File Media Recovery
4.2.6.5
Re-Create Objects Manually
4.2.7
Recovering from Human Error
4.2.7.1
Resolving Table Inconsistencies
4.2.7.2
Resolving Row and Transaction Inconsistencies
4.2.7.3
Resolving Database-Wide Inconsistencies
4.2.7.4
Resolving One or More Tablespace Inconsistencies
4.2.8
Recovering Databases in a Distributed Environment
4.3
Restoring Fault Tolerance
4.3.1
Restoring Failed Nodes or Instances in Oracle RAC
4.3.1.1
Recovering Service Availability
4.3.1.2
Considerations for Client Connections After Restoring an Oracle RAC Instance
4.3.2
Restoring a Standby Database After a Failover
4.3.2.1
Reinstating the Original Primary 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 Cluster
4.3.5
Restoring Fault Tolerance After a Standby Database Data Failure
4.3.6
Restoring Fault Tolerance After the Primary Database Was Opened Resetlogs
4.3.7
Restoring Fault Tolerance After Dual Failures
5
Managing Scheduled Outages
5.1
Overview of Scheduled Outages
5.1.1
Managing Scheduled Outages on the Primary Site
5.1.2
Managing Scheduled Outages On the Secondary Site
5.2
Eliminating or Reducing Downtime for Scheduled Outages
5.2.1
Site, Hardware, and Software Maintenance Using Database Switchover
5.2.1.1
When to Perform a Data Guard Switchover
5.2.1.2
Best Practices for Configuring Data Guard Switchover
5.2.1.3
How to Perform Data Guard Switchover
5.2.2
Online Patching
5.2.3
Oracle RAC Database Patches
5.2.3.1
Best Practices to Minimize Downtime for All Database Patch Upgrades
5.2.3.2
Best Practices to Minimize Downtime for Database Rolling Upgrades
5.2.4
Storage Maintenance
5.2.4.1
Migrating to ASM Storage
5.2.4.2
Adding and Removing Storage
5.2.4.3
Upgrading ASM Nodes
5.2.5
Database Upgrades
5.2.5.1
Database Upgrade Assistant
5.2.5.2
Data Guard SQL Apply or Transient Logical Standby Database
5.2.5.3
Oracle Streams
5.2.5.4
Transportable Tablespaces
5.2.6
Database Platform or Location Migration
5.2.6.1
Physical Standby Databases for Platform Migration
5.2.6.2
Transportable Database for Platform Migration
5.2.6.3
Oracle Streams for Platform Migration
5.2.6.4
Oracle Data Pump for Platform Migration
5.2.6.5
Transportable Tablespaces for Platform Migration
5.2.6.6
Data Guard Redo Apply (Physical Standby Database) for Location Migration
5.2.7
Oracle Streams for Online Database Upgrade
5.2.8
Oracle Streams for Online Application Upgrades
5.2.9
Data Reorganization and Redefinition
5.2.10
System Maintenance
6
Migrating to an MAA Environment
6.1
Moving Your Configuration to MAA
6.2
Using Oracle Enterprise Manager Grid Control
6.3
Using Manual Step-by-Step Instructions
6.3.1
Converting a Single-Instance Database to an Oracle RAC Database
6.3.2
Adding an Oracle Data Guard Configuration to an Oracle RAC Primary Database
6.3.2.1
Creating an Oracle RAC Physical Standby Database for an Oracle RAC Primary Database
6.3.2.2
Creating a Single-instance Standby Database for an Oracle RAC Primary
6.3.2.3
Creating an Oracle RAC Logical Standby for an Oracle RAC Primary Database
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.