Skip Headers

Oracle® Fail Safe Concepts and Administration Guide
Release 3.3.3 for Windows
Part No. B12070-01
  Go To Index
Index

Next  

Contents

List of Figures

List of Tables

Title and Copyright Information

Send Us Your Comments

Preface

Intended Audience
Documentation Accessibility
Organization
Related Documents
Conventions
Documentation Sales

1 Introduction to Oracle Fail Safe

1.1 What Is 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 Ease of Integration with Applications
1.3 A Typical Oracle Fail Safe Configuration
1.4 Deploying Oracle Fail Safe Solutions

2 Cluster Concepts

2.1 Cluster Technology
2.1.1 How Clusters Provide High Availability
2.1.2 System-Level Configuration
2.1.3 Disk-Level Configuration
2.1.4 The Quorum Resource
2.2 Resources, Groups, and High Availability
2.2.1 Resources
2.2.2 Groups
2.2.3 Resource Dependencies
2.2.4 Resource Types
2.3 Groups, Virtual Addresses, and Virtual Servers
2.4 Allocating IP Addresses for Virtual Addresses
2.5 Cluster Group and Cluster Alias
2.6 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 How a Resource Failure Is Detected
2.6.5 Resource Restart Policy
2.6.6 Resource Failover Policy
2.6.7 Resource Possible Owner Nodes List
2.6.8 Group Failover Policy
2.6.9 Effect of Resource Restart Policy and Group Failover Policy on Failover
2.6.10 Group Failover and the Preferred Owner Nodes List
2.6.11 Determining the Failover Node for a Group
2.7 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 What Does It Mean to Configure Failover?
4.2 How Does Oracle Fail Safe Use the Wizard Input?
4.3 Managing Cluster Security
4.3.1 Oracle Services for MSCS
4.3.1.1 Account Updates Using the Oracle Fail Safe Security Setup Tool
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 Virtual Addresses
4.8 Adding a Node to an Existing Cluster

5 The FSCMD Command-Line Interface

FSCMD

6 Troubleshooting Tools

6.1 Verify Operations
6.1.1 Verify Cluster
6.1.2 Verify Group
6.1.3 Verify Standalone Database
6.2 Dump Cluster
6.3 Finding Additional Troubleshooting Information

7 Configuring Single-Instance Databases for High Availability

7.1 Discovering Standalone Single-Instance Databases
7.2 Oracle Net Configuration for Standalone Single-Instance Databases
7.2.1 Updating the Oracle Net Configuration for a Database Created Using DBCA
7.2.2 Listener Must Use IP Address, Not Host Name
7.2.3 SID List Entries and Upgrades to Oracle Database Software
7.2.4 Configuring Oracle Net on Nodes with Multiple Listeners
7.2.5 Shared Server Configuration and a Standalone Database
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 Choose Nodes
7.3.3.2 Virtual Address
7.3.3.3 Database Identity
7.3.3.3.1 Parameter File and Oracle9i and Later Databases That Use an SPFILE
7.3.3.3.2 Parameter File and Oracle9i and Later Databases Created with DBCA
7.3.3.4 Database Authentication
7.3.3.5 Database Password
7.4 Oracle Net Listener Resource Creation and Configuration
7.4.1 Using Shared Sockets in Dedicated Server Mode
7.4.2 Client Connections to Highly Available Single-Instance Databases
7.4.3 Updated Oracle Net Configuration After Adding a Database to a Group
7.4.3.1 Updates That Oracle Fail Safe Makes to the tnsnames.ora File
7.4.3.2 Updates That Oracle Fail Safe Makes to the listener.ora File
7.4.3.3 Updates That Oracle Fail Safe Makes to the sqlnet.ora File
7.4.4 Using External Procedures with Databases Configured for High Availability
7.4.5 Support for Databases Using Shared Servers
7.4.5.1 Shared Servers for Oracle8 Databases
7.4.5.2 Shared Servers for Oracle8i or Later Databases
7.5 Security Requirements for Single-Instance Databases
7.5.1 Synchronizing Password Files on Cluster Nodes
7.5.2 Changing the SYSDBA Account Password
7.5.3 Upgrading a Fail-Safe Database with the Oracle Database Upgrade Assistant
7.6 Integrating with Oracle Enterprise Manager
7.6.1 Adding an Oracle Intelligent Agent to a Group
7.7 Optimizations for Single-Instance Database Recovery
7.8 Performing Administrative Tasks on a Single-Instance Fail-Safe Database
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 Database Authentication
7.10.7 Problems with Sample Databases
7.10.8 Problems with Virtual Server Configurations
7.10.8.1 Problems Configuring the Virtual Address
7.10.8.2 Problems Creating Listeners
7.10.8.3 Archived listener.ora or tnsnames.ora Files
7.10.8.4 Rollback Files
7.10.9 Security Access and Authentication Problems
7.10.10 Clients Cannot Access a Database

8 Configuring Oracle HTTP Servers for High Availability

8.1 Discovering Standalone Oracle HTTP Servers
8.2 Adding Oracle HTTP Servers to a Group
8.2.1 Before You Get Started
8.2.2 Oracle HTTP Server Configuration Steps
8.2.3 Configuration Data for Oracle HTTP Servers
8.2.3.1 Choose Nodes
8.2.3.2 Oracle HTTP Server Identity
8.2.3.3 Oracle HTTP Server Directories
8.2.3.4 Oracle HTTP Server Virtual Address
8.3 Client Connection to Oracle HTTP Servers
8.4 Removing an Oracle HTTP Server from a Group
8.5 Security Requirements for Oracle HTTP Servers
8.6 Troubleshooting Problems with Oracle HTTP Servers
8.6.1 Problems Adding an Oracle HTTP Server to a Group
8.6.2 Users Cannot Access the Oracle HTTP Server
8.6.3 Users Are Unable to Connect to the Oracle HTTP Server Web Site
8.6.4 Users Cannot Access Documents on the Web Site

9 Configuring Generic Services for High Availability

9.1 Introduction
9.1.1 Advantages of Using Oracle Fail Safe
9.1.2 Generic Resources That Should Not Be Configured for High Availability
9.2 Discovering Standalone Generic Services
9.3 Adding Generic Services to a Group
9.3.1 Configuration Steps
9.3.2 Configuration Data for Generic Services
9.3.2.1 Choose Nodes
9.3.2.2 Generic Service Identity
9.3.2.3 Generic Service Startup Parameters
9.3.2.4 Disks Used by a Generic Service
9.3.2.5 Generic Service Dependencies
9.3.2.5.1 Specifying Generic Service Dependencies
9.3.2.5.2 Generic Services and Virtual Address Dependencies
9.3.2.6 Generic Service Registry Keys
9.4 Security Requirements for Generic Services
9.5 Configuring the Sample Generic Service
9.6 Troubleshooting Problems with Generic Services

A Network Configuration Considerations

A.1 Registering Host Names and IP Addresses
A.2 Validating Proper Name Resolution in the Cluster
A.3 Changing IP Addresses of Cluster Nodes
A.4 Troubleshooting Problems with Improper Name Resolution

B Contacting Oracle Support Services

B.1 Reporting a Problem
B.2 Finding Your Version Information
B.3 Tracing Oracle Fail Safe Problems
B.4 Locating Trace and Alert Files

Glossary

Index