Contents

List of Figures

List of Tables

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents
• Conventions

1 Introduction to Oracle Fail Safe

• 1.1 Overview of Oracle Fail Safe
• 1.2 Benefits of Oracle Fail Safe
  • 1.2.1 Highly Available Resources and Applications
  • 1.2.2 Ease of Use
  • 1.2.3 Product Accessibility
  • 1.2.4 Ease of Integration with Applications
• 1.3 Overview of a Typical Oracle Fail Safe Configuration
• 1.4 Deploying Oracle Fail Safe Solutions

2 Cluster Concepts

• 2.1 Cluster Technology
  • 2.1.1 About Clusters Providing High Availability
  • 2.1.2 About System-Level Configuration
  • 2.1.3 About Disk-Level Configuration
• 2.2 Resources, Groups, and High Availability
  • 2.2.1 About Resources
  • 2.2.2 About Groups
  • 2.2.3 About Resource Dependencies
  • 2.2.4 About Resource Types
• 2.3 Groups, Network Names, and Virtual Servers
• 2.4 Allocating IP Addresses for Network Names
• 2.5 Cluster Group and Cluster Alias
• 2.6 About Failover
  • 2.6.1 Unplanned Failover
    • 2.6.1.1 Unplanned Failover Due to a Resource Failure
    • 2.6.1.2 Unplanned Failover Due to Node Failure or Unavailability
  • 2.6.2 Planned Group Failover
  • 2.6.3 Group and Resource Policies That Affect Failover
  • 2.6.4 Detecting a Resource Failure
  • 2.6.5 About Resource Restart Policy
  • 2.6.6 About Resource Failover Policy
  • 2.6.7 About Resource Possible Owner Nodes List
  • 2.6.8 About Group Failover Policy
  • 2.6.9 Effect of Resource Restart Policy and Group Failover Policy on Failover
  • 2.6.10 About Group Failover and the Preferred Owner Nodes List
  • 2.6.11 Determining the Failover Node for a Group
• 2.7 About Failback
  • 2.7.1 Group Failback and the Preferred Owner Nodes List
  • 2.7.2 Client Reconnection After Failover

3 Designing an Oracle Fail Safe Solution

• 3.1 Customizing Your Configuration
  • 3.1.1 Active/Passive Configuration
  • 3.1.2 Active/Active Configuration
• 3.2 Integrating Clients and Applications

4 Management for High Availability

• 4.1 Configuring Resources for Failover
• 4.2 How Does Oracle Fail Safe Use the Wizard Input?
• 4.3 Managing Cluster Security
  • 4.3.1 Oracle Fail Safe
    • 4.3.1.1 Changing the Oracle Fail Safe Server Account
  • 4.3.2 Oracle Fail Safe Manager
• 4.4 Discovering Standalone Resources
• 4.5 Renaming Resources
• 4.6 Using Oracle Fail Safe in a Multiple Oracle Homes Environment
• 4.7 Configurations Using Multiple Network Names
• 4.8 Adding a Node to an Existing Cluster

5 PowerShell Commands

• 5.1 Getting Started
• 5.2 About Common Parameters
• 5.3 Using the Oracle Fail Safe cmdlets in Scripts
• 5.4 FSCMD Equivalent cmdlets
• 5.5 Examples

6 Validating Actions

• 6.1 Validating Operations
  • 6.1.1 Validating Cluster
  • 6.1.2 Validating the Configuration of Oracle Resources
  • 6.1.3 Validating Standalone Database
• 6.2 Dumping Cluster
• 6.3 Finding Additional Troubleshooting Information

7 Configuring Single-Instance Databases for High Availability and Disaster Tolerance

• 7.1 Discovering Standalone Single-Instance Databases
• 7.2 Oracle Net Configuration for Standalone Single-Instance Databases
  • 7.2.1 Listener Must Use IP Address for Local Host, Not Host Name
  • 7.2.2 Shared Server Configuration and a Standalone Database
  • 7.2.3 SID List Entries
  • 7.2.4 Configuring Oracle Net on Nodes with Multiple Listeners
• 7.3 Adding Single-Instance Oracle Databases to a Group
  • 7.3.1 Before You Get Started
  • 7.3.2 Configuration Steps
  • 7.3.3 Configuration Data for Oracle Databases
    • 7.3.3.1 Naming a Cluster Resource
    • 7.3.3.2 Choosing Nodes
    • 7.3.3.3 Selecting Network Names
    • 7.3.3.4 Identifying Database Parameters
    • 7.3.3.5 Database Authentication
    • 7.3.3.6 Database Resource Addition Confirmation
• 7.4 About Oracle Net Listener Resource Creation and Configuration
  • 7.4.1 Client Connections to Highly Available Single-Instance Databases
  • 7.4.2 Updating Oracle Net Configuration After Adding a Database to a Group
    • 7.4.2.1 Updates That Oracle Fail Safe Makes to the tnsnames.ora File
    • 7.4.2.2 Updates That Oracle Fail Safe Makes to the listener.ora File
    • 7.4.2.3 Updates That Oracle Fail Safe Makes to the sqlnet.ora File
  • 7.4.3 Using External Procedures with Databases Configured for High Availability
  • 7.4.4 Support for Databases Using Shared Servers
    • 7.4.4.1 Shared Servers for Databases
• 7.5 Security Requirements for Single-Instance Databases
  • 7.5.1 Synchronizing Password Files on Cluster Nodes
  • 7.5.2 Changing the SYS Account Password
  • 7.5.3 Upgrading a Fail-Safe Database with the Oracle Database Upgrade Assistant
• 7.6 Optimizations for Single-Instance Database Recovery
• 7.7 Performing Administrative Tasks on a Single-Instance Fail-Safe Database
• 7.8 Database Homes
• 7.9 Configuring Transparent Application Failover (TAF)
• 7.10 Handling Errors and Troubleshooting Problems with Databases
  • 7.10.1 Handling Errors That Occur When Bringing a Database Online
  • 7.10.2 Troubleshooting Problems
  • 7.10.3 Problems Adding a Database to a Group
  • 7.10.4 Problems Placing a Group Online
  • 7.10.5 Group Fails Over During Processing-Intensive Operations
  • 7.10.6 About Database Authentication
  • 7.10.7 Problems with Virtual Server Configurations
    • 7.10.7.1 Problems Configuring the Network Name
    • 7.10.7.2 Problems Creating Listeners
    • 7.10.7.3 Archived listener.ora or tnsnames.ora Files
  • 7.10.8 Security Access and Authentication Problems
  • 7.10.9 Clients Cannot Access a Database
• 7.11 Using Highly Available Databases with Oracle Data Guard
• 7.12 Use of Startup Triggers

8 Configuring Oracle Management Agent for High Availability

• 8.1 Prerequisites for High Availability
• 8.2 Procedure for Configuring Oracle Management Agent for High Availability
  • 8.2.1 Configuring Oracle Management Agent for High Availability Step 1: Make the Management Agent Highly Available
  • 8.2.2 Configuring Oracle Management Agent for High Availability Step 2: Add the Highly Available Database as a Target in Oracle Enterprise Manager
  • 8.2.3 Configuring Oracle Management Agent for High Availability Step 3: Test the Highly Available Management Agentv
  • 8.2.4 Configuring Oracle Management Agent for High Availability Step 4: Remove Extraneous Targets from the Oracle Enterprise Manager Environment
• 8.3 Removing Oracle Management Agent from a Group

A Contacting Oracle Support Services

• A.1 Reporting a Problem
• A.2 Finding the Version of Oracle Software
• A.3 Viewing Error Information
• A.4 Tracing Oracle Fail Safe Problems
• A.5 Locating Trace and Alert Files

Glossary

Index