1/20

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 Architectures
• 1.2 Oracle Database High Availability Best Practices
• 1.3 Oracle Maximum Availability Architecture

2 Overview of Configuration Best Practices

3 Configuring Storage

• 3.1 Evaluate Database Performance and Storage Capacity Requirements
• 3.2 Use Automatic Storage Management (Oracle ASM) to Manage Database Files
  • 3.2.1 Use Clustered Oracle ASM to Enable the Storage Grid
  • 3.2.2 Use Oracle Restart for Oracle ASM Instances (non-clustered Oracle Database)
• 3.3 Oracle ASM Strategic Best Practices
  • 3.3.1 Use a Simple Disk and Disk Group Configuration
  • 3.3.2 Use Redundancy to Protect from Disk Failure
    • 3.3.2.1 Storage Array Based RAID
    • 3.3.2.2 Oracle ASM Redundancy
  • 3.3.3 Oracle ASM in the Grid Infrastructure Home
  • 3.3.4 Ensure Disks in the Same Disk Group Have the Same Characteristics
  • 3.3.5 Use Failure Groups When Using Oracle ASM Redundancy
  • 3.3.6 Use Intelligent Data Placement
  • 3.3.7 Use Oracle ACFS to Manage Files Outside the Database
• 3.4 Oracle ASM Configuration Best Practices
  • 3.4.1 Use Disk Multipathing Software to Protect from Path Failure
  • 3.4.2 Set the PROCESSES Initialization Parameter
  • 3.4.3 Use Disk Labels
  • 3.4.4 Set the FAILGROUP_REPAIR_TIME or DISK_REPAIR_TIME Disk Group Attribute Appropriately
  • 3.4.5 Use ASMLib On Supported Platforms
  • 3.4.6 Configure LUNs Properly
  • 3.4.7 Use Disks with Similar Characteristics and Capacity
  • 3.4.8 Configure Disk Groups Properly
• 3.5 Oracle ASM Operational Best Practices
  • 3.5.1 Use SYSASM for Oracle ASM Authentication
  • 3.5.2 Set Rebalance Power Limit to the Maximum Limit that Does Not Affect Service Levels
  • 3.5.3 Use a Single Command to Mount Multiple Disk Groups
  • 3.5.4 Use a Single Command to Add or Remove Storage
  • 3.5.5 Check Disk Groups for Imbalance
  • 3.5.6 Proactively Mine Vendor Logs for Disk Errors
  • 3.5.7 Use ASMCMD Utility to Ease Manageability of Oracle ASM
  • 3.5.8 Use Oracle ASM Configuration Assistant (ASMCA)
• 3.6 Use Oracle Storage Grid
  • 3.6.1 Oracle Storage Grid Best Practices for Unplanned Outages
  • 3.6.2 Oracle Storage Grid Best Practices for Planned Maintenance

4 Configuring Oracle Database

• 4.1 Database Configuration High Availability and Fast Recoverability Best Practices
  • 4.1.1 Set the Database ARCHIVELOG Mode and FORCE LOGGING Mode
  • 4.1.2 Configure the Size of Redo Log Files and Groups Appropriately
  • 4.1.3 Use a Fast Recovery Area
  • 4.1.4 Enable Flashback Database
  • 4.1.5 Set FAST START MTTR TARGET Initialization Parameter
  • 4.1.6 Protect Against Data Corruption
    • 4.1.6.1 Preventing Widespread Data Corruption
    • 4.1.6.2 Detecting and Monitoring Data Corruption
  • 4.1.7 Set DISK_ASYNCH_IO Initialization Parameter
  • 4.1.8 Set LOG_BUFFER Initialization Parameter to 8 MB or Higher
  • 4.1.9 Use Automatic Shared Memory Management and Avoid Memory Paging
  • 4.1.10 Disable Parallel Recovery for Instance Recovery
• 4.2 Recommendations to Improve Manageability
  • 4.2.1 Use Oracle Clusterware with Oracle RAC or Oracle Restart
  • 4.2.2 Use Data Recovery Adviser to Detect, Analyze and Repair Data Failures
  • 4.2.3 Use Automatic Performance Tuning Features
  • 4.2.4 Use a Server Parameter File
  • 4.2.5 Use Automatic Undo Management
  • 4.2.6 Use Locally Managed Tablespaces
  • 4.2.7 Use Automatic Segment Space Management
  • 4.2.8 Use Temporary Tablespaces and Specify a Default Temporary Tablespace
  • 4.2.9 Use Resumable Space Allocation
  • 4.2.10 Use Database Resource Manager
  • 4.2.11 Use Oracle Multitenant Best Practices

5 Configuring Oracle Database with Oracle Clusterware

• 5.1 About Oracle Clusterware Best Practices
  • 5.1.1 Client Configuration and Migration Concepts
    • 5.1.1.1 Services
    • 5.1.1.2 Fast Application Notification (FAN)
    • 5.1.1.3 Single Client Access Name (SCAN)
    • 5.1.1.4 Application Continuity and Transaction Guard
• 5.2 Oracle Clusterware Configuration Best Practices
  • 5.2.1 Use the Cluster Verification Utility (CVU)
  • 5.2.2 Use a Local Home for Oracle Database and Oracle Clusterware with Oracle ASM
  • 5.2.3 Ensure Services are Highly Available
  • 5.2.4 Client Configuration and FAN Best Practices
  • 5.2.5 Connect to Database Using Services and Single Client Access Name (SCAN)
  • 5.2.6 Use Client-Side and Server-Side Load Balancing
  • 5.2.7 Mirror Oracle Cluster Registry (OCR) and Configure Multiple Voting Disks with Oracle ASM
  • 5.2.8 Use Company Wide Cluster Time Management
  • 5.2.9 Verify That Oracle Clusterware, Oracle RAC, and Oracle ASM Use the Same Interconnect Network
  • 5.2.10 Use Redundant Interconnect with Highly Available IP (HAIP)
  • 5.2.11 Configure Failure Isolation with Intelligent Management Platform Interface (IPMI)
  • 5.2.12 Use Jumbo Frames for Cluster Interconnect Network
• 5.3 Oracle Clusterware Operational Best Practices
  • 5.3.1 Capacity Planning
  • 5.3.2 Regularly Back Up OCR to Tape or Offsite
  • 5.3.3 Use Cluster Health Monitor for Troubleshooting

6 Configuring Oracle Database with Oracle RAC

• 6.1 Configuring Oracle Database with Oracle RAC
  • 6.1.1 Optimize Instance Recovery Time
  • 6.1.2 Maximize the Number of Processes Performing Transaction Recovery
  • 6.1.3 Ensure Asynchronous I/O Is Enabled
  • 6.1.4 Redundant Dedicated Connection Between the Nodes
• 6.2 Configuring Oracle Database with Oracle RAC One Node
• 6.3 Configuring Oracle Database with Oracle RAC on Extended Clusters
  • 6.3.1 Spread the Workload Evenly Across the Sites in the Extended Cluster
  • 6.3.2 Add a Third Voting Disk to Host the Quorum Disk
  • 6.3.3 Configure the Nodes to Be Within the Proximity of a Metropolitan Area
  • 6.3.4 Use Host-Based Storage Mirroring with Oracle ASM Normal or High Redundancy
  • 6.3.5 Additional Deployment Considerations for Extended Clusters

7 Configuring Backup and Recovery

• 7.1 Oracle Database Backup and Recovery Products and Features
  • 7.1.1 Understand When to Use Backups
  • 7.1.2 Use Zero Data Loss Recovery Appliance to Back Up Database Files
  • 7.1.3 Use Recovery Manager (RMAN) to Backup Database Files
  • 7.1.4 Use Oracle Secure Backup for Backups to Tape
    • 7.1.4.1 Using Oracle Secure Backup for Backups to Amazon S3 Storage
  • 7.1.5 Use Restore Points for Creating Database Snapshots
• 7.2 Backup and Recovery Configuration and Administration Best Practices
  • 7.2.1 Determine a Backup Frequency and Retention Policy
  • 7.2.2 Use an RMAN Recovery Catalog
  • 7.2.3 Create Backups in NOCATALOG Mode and Then RESYNC CATALOG When Not Using Recovery Appliance
  • 7.2.4 Enable Block Change Tracking for Incremental Backups
  • 7.2.5 Enable Autobackup for the Control File and Server Parameter File
  • 7.2.6 Offload Backups to a Physical Standby Database
  • 7.2.7 Set UNDO Retention for Flashback Query and Flashback Table Needs
• 7.3 Backup to Disk Best Practices
• 7.4 Backup to Tape Best Practices
  • 7.4.1 Initial RMAN Oracle Secure Backup Configuration
  • 7.4.2 Define Oracle Secure Backup Media Policies for Tape Backups
  • 7.4.3 Create Tape Backups from the Fast Recovery Area
  • 7.4.4 Managing Offsite Backup Tapes
• 7.5 Backup and Recovery Operations and Maintenance Best Practices
  • 7.5.1 Use Read Only Tablespaces
  • 7.5.2 Do Not Compress Data That Has Already Been Compressed
  • 7.5.3 Use Section Size Parameter to Break Up BigFile DataFiles Backup
  • 7.5.4 Diagnose Data Failures and Present Repair Options
  • 7.5.5 Regularly Check Database Files for Corruption
  • 7.5.6 Periodically Test Recovery Procedures
  • 7.5.7 Back Up the RMAN and Oracle Secure Backup Catalogs on a Regular Basis
  • 7.5.8 Use Procedures to Backup Files Outside the Database
• 7.6 Backup Files Outside the Database
  • 7.6.1 ACFS Snapshots
  • 7.6.2 Oracle ZFS Storage Appliance Snapshots
  • 7.6.3 Tape Backups

8  Configuring Oracle Data Guard

• 8.1 Oracle Data Guard Configuration Best Practices
• 8.2 Determine Protection Mode and Data Guard Transport
  • 8.2.1 Use Redo Transport Services Best Practices
  • 8.2.2 Assess Performance with Proposed Network Configuration
  • 8.2.3 Active Data Guard Far Sync
    • 8.2.3.1 Offloading to Far Sync
    • 8.2.3.2 Far Sync High Availability
• 8.3 General Data Guard Configuration Best Practices
  • 8.3.1 Use Oracle Data Guard Broker with Oracle Data Guard
  • 8.3.2 Use Recovery Manager to Create Standby Databases
  • 8.3.3 Use Flashback Database for Reinstatement After Failover
  • 8.3.4 Use FORCE LOGGING Mode
  • 8.3.5 Use a Simple, Robust Archiving Strategy and Configuration
  • 8.3.6 Use Standby Redo Logs and Configure Size Appropriately
  • 8.3.7 Use Data Guard Transport and Network Configuration Best Practices
    • 8.3.7.1 Set the LOG_ARCHIVE_MAX_PROCESSES Parameter
    • 8.3.7.2 Set the Network Configuration and Highest Network Redo Rates
  • 8.3.8 Use Data Guard Redo Apply Best Practices
    • 8.3.8.1 Maximize I/O Rates on Standby Redo Logs and Archived Redo Logs
    • 8.3.8.2 Assess Recovery Rate
    • 8.3.8.3 Set DB_BLOCK_CHECKSUM=FULL and DB_BLOCK_CHECKING=MEDIUM or FULL
    • 8.3.8.4 Set DB_CACHE_SIZE to a Value Greater than on the Primary Database
    • 8.3.8.5 Assess Database Wait Events
    • 8.3.8.6 Tune I/O Operations
    • 8.3.8.7 Assess System Resources
  • 8.3.9 Implement Multiple Standby Databases
• 8.4 Oracle Multitenant Databases in a Data Guard Environment
• 8.5 Oracle Data Guard Role Transition Best Practices
  • 8.5.1 Oracle Data Guard Switchovers Best Practices
  • 8.5.2 Oracle Data Guard Failovers Best Practices
    • 8.5.2.1 Comparing Fast-Start Failover and Manual Failover
    • 8.5.2.2 Failover Best Practices (Manual Failover and Fast-Start Failover)
    • 8.5.2.3 Fast-Start Failover Best Practices
    • 8.5.2.4 Manual Failover Best Practices
• 8.6 Use Oracle Active Data Guard Best Practices
• 8.7 Use Snapshot Standby Database Best Practices
• 8.8 Assessing Data Guard Performance

9 Configuring Oracle GoldenGate

• 9.1 Oracle GoldenGate Overview
  • 9.1.1 Oracle GoldenGate and Oracle RAC
  • 9.1.2 Oracle GoldenGate and Oracle Data Guard/Oracle Active Data Guard
  • 9.1.3 Oracle GoldenGate and Edition-Based Redefinition
• 9.2 Oracle GoldenGate Configuration Best Practices
  • 9.2.1 Oracle GoldenGate Integrated Extract and Integrated Replicat
  • 9.2.2 Use of a Clustered File System
• 9.3 Oracle GoldenGate Operational Best Practices

10 Client Failover Best Practices for Highly Available Oracle Databases

• 10.1 Automating Client Failover - JDBC, OCI, and ODP.Net
  • 10.1.1 Configuring Fast Connection Failover for JDBC Clients
  • 10.1.2 Configuring Application Continuity
    • 10.1.2.1 Configuring Oracle UCP 12c
    • 10.1.2.2 Configuring Oracle WebLogic Server 12c
    • 10.1.2.3 Configuring Standalone Java Applications or Third-party Connection Pools
    • 10.1.2.4 Configuring Connections for High Availability (Failover and Failback)
    • 10.1.2.5 Configuring Services for Application Continuity
    • 10.1.2.6 Checking Resource Allocation
  • 10.1.3 Configuring Fast Connection Failover for OCI Clients
  • 10.1.4 Configuring Automatic Failover for ODP.Net Clients
• 10.2 Configuring Oracle RAC Databases for Failover
  • 10.2.1 Configuring Database Services
  • 10.2.2 Optionally Configure FAN Server Side Callouts
• 10.3 Configuring the Oracle Data Guard Environment
  • 10.3.1 Configuring Database Services
  • 10.3.2 Use Data Guard Broker
• 10.4 Client Transition During Switchover Operations
• 10.5 Preventing Login Storms
• 10.6 Configuring Global Data Services
  • 10.6.1 Configuring the Database Client

11 Monitoring for High Availability

• 11.1 Overview of Monitoring and Detection for High Availability
• 11.2 Using Enterprise Manager for System Monitoring
  • 11.2.1 Oracle Enterprise Manager Home Page
  • 11.2.2 Configure Metrics and Incident Rule Sets
  • 11.2.3 Use Database Target Views to Monitor Health, Availability, and Performance
  • 11.2.4 Use Metrics to Monitor Data Guard System Availability
• 11.3 Managing the High Availability Environment with Enterprise Manager
  • 11.3.1 Check Enterprise Manager Compliance Results
  • 11.3.2 Use Enterprise Manager to Manage Oracle Patches and Maintain System Baselines
  • 11.3.3 Manage Database Availability with the High Availability Console
  • 11.3.4 Configure High Availability Solutions with MAA Advisor
• 11.4 Using Cluster Health Monitor

12 Recovering from Unscheduled Outages

• 12.1 Overview of Unscheduled Outages
  • 12.1.1 Managing Unscheduled Outages on the Primary Site Best Practices
  • 12.1.2 Managing Unscheduled Outages on the Standby Site Best Practices
• 12.2 Recovering from Unscheduled Outages
  • 12.2.1 Complete Site Failover (Failover to Secondary Site)
    • 12.2.1.1 When to Use Complete Site Failover
    • 12.2.1.2 Best Practices for Complete Site Failover
    • 12.2.1.3 Complete Site Failover
  • 12.2.2 Database Failover with a Standby Database
    • 12.2.2.1 When To Perform a Data Guard Failover
    • 12.2.2.2 Best Practices for Implementing Fast-Start Failover
    • 12.2.2.3 Best Practices for Performing Manual Failover
  • 12.2.3 Oracle RAC Recovery for Unscheduled Outages (for Node or Instance Failures)
    • 12.2.3.1 Automatic Instance Recovery for Failed Instances
    • 12.2.3.2 Automatic Service Relocation
    • 12.2.3.3 Oracle Cluster Registry Recovery
  • 12.2.4 Application Failover
  • 12.2.5 Application Failover with Application Continuity and Transaction Guard
  • 12.2.6 Oracle ASM Recovery After Disk and Storage Failures
    • 12.2.6.1 Oracle ASM Instance Failure
    • 12.2.6.2 Oracle ASM Disk Failure
    • 12.2.6.3 Data Area Disk Group Failure
    • 12.2.6.4 Fast Recovery Area Disk Group Failure
  • 12.2.7 Recovering from Data Corruption
    • 12.2.7.1 Use Data Recovery Advisor
    • 12.2.7.2 Use Active Data Guard
    • 12.2.7.3 Use RMAN and Block Media Recovery
    • 12.2.7.4 Perform a Data Guard Role Transition
    • 12.2.7.5 Use RMAN and Data File Media Recovery
  • 12.2.8 Recovering from Human Error (Recovery with Flashback)
    • 12.2.8.1 Resolving Table Inconsistencies
    • 12.2.8.2 Resolving Row and Transaction Inconsistencies
    • 12.2.8.3 Resolving Database-Wide Inconsistencies
    • 12.2.8.4 Resolving One or More Tablespace Inconsistencies
  • 12.2.9 Recovering Databases in a Distributed Environment
• 12.3 Restoring Fault Tolerance
  • 12.3.1 Restoring Failed Nodes or Instances in Oracle RAC and Oracle RAC One Node
    • 12.3.1.1 Recovering Service Availability for Oracle RAC
    • 12.3.1.2 Recovering Service Availability for Oracle RAC One Node
    • 12.3.1.3 Considerations for Client Connections After Restoring an Oracle RAC Instance
  • 12.3.2 Restoring a Standby Database After a Failover
    • 12.3.2.1 Reinstating the Original Primary Database After a Fast-Start Failover
    • 12.3.2.2 Reinstating a Standby Database Using Enterprise Manager After a Failover
  • 12.3.3 Restoring Oracle ASM Disk Groups after a Failure
  • 12.3.4 Restoring Fault Tolerance After Planned Downtime on Secondary Site or Cluster
  • 12.3.5 Restoring Fault Tolerance After a Standby Database Data Failure
  • 12.3.6 Restoring Fault Tolerance After the Primary Database Was Opened Resetlogs
  • 12.3.7 Restoring Fault Tolerance After Dual Failures

13 Reducing Downtime for Planned Maintenance

• 13.1 Overview of Scheduled Outages
  • 13.1.1 Managing Scheduled Outages on the Primary Site
  • 13.1.2 Managing Scheduled Outages On the Secondary Site
• 13.2 Eliminating or Reducing Downtime for Scheduled Outages
  • 13.2.1 Site, Hardware, and Software Maintenance Using Data Guard Switchover
    • 13.2.1.1 When to Perform a Data Guard Switchover
    • 13.2.1.2 Best Practices for Configuring Data Guard Switchover
    • 13.2.1.3 How to Perform Data Guard Switchover
  • 13.2.2 Online Patching
  • 13.2.3 Data Guard Standby-First Patch Apply
  • 13.2.4 Oracle Database and Grid Infrastructure Patching
    • 13.2.4.1 Rolling Patch Installation
    • 13.2.4.2 Best Practices to Minimize Downtime for All Patch Upgrades
    • 13.2.4.3 Best Practices to Minimize Downtime for Database Rolling Patches
    • 13.2.4.4 Out-of-place Software Installation and Patching
    • 13.2.4.5 Using OPlan for Patching
  • 13.2.5 Grid Infrastructure Upgrade
    • 13.2.5.1 Grid Infrastructure Rolling Upgrade
  • 13.2.6 Storage Maintenance
    • 13.2.6.1 Migrating to Oracle ASM Storage
    • 13.2.6.2 Adding and Removing Storage
  • 13.2.7 Database Upgrades
    • 13.2.7.1 Upgrading with Database Upgrade Assistant (DBUA)
    • 13.2.7.2 Upgrading with Data Guard SQL Apply or Transient Logical Standby Database
    • 13.2.7.3 Upgrading with Oracle GoldenGate
    • 13.2.7.4 Upgrading by Transporting Data
  • 13.2.8 Database Platform or Location Migration
    • 13.2.8.1 Consider Your Options and Your Migration Strategy
    • 13.2.8.2 Plan Your Migration
    • 13.2.8.3 Oracle Features for Platform Migration and Upgrades
    • 13.2.8.4 Physical Standby Databases for Platform Migration
    • 13.2.8.5 Transportable Database for Platform Migration
    • 13.2.8.6 Oracle GoldenGate for Platform Migration
    • 13.2.8.7 Oracle Data Pump for Platform Migration
    • 13.2.8.8 Transportable Tablespaces for Platform Migration
    • 13.2.8.9 Data Guard Redo Apply (Physical Standby Database) for Location Migration
  • 13.2.9 Edition-Based Redefinition for Online Application Maintenance and Upgrades
  • 13.2.10 Oracle GoldenGate for Online Application Upgrades
  • 13.2.11 Data Reorganization and Redefinition
  • 13.2.12 Dynamic Database Services for System Maintenance

Glossary

Index