Skip Headers
Oracle® Application Server High Availability Guide
10
g
Release 3 (10.1.3)
B15977-02
Home
Solution Area
Index
Next
Contents
Title and Copyright Information
Preface
Intended Audience
Documentation Accessibility
Related Documentation
Conventions
Part I Overview
1
Introduction to High Availability
1.1
What is High Availability
1.1.1
High Availability Problems
1.1.2
High Availability Solutions
1.2
Oracle Application Server High Availability Concepts
1.2.1
Terminology
1.2.2
Oracle Application Server Base Architecture
1.2.3
Using Oracle Identity Management with Oracle Application Server Release 3 (10.1.3)
1.2.4
Oracle Application Server High Availability Architectures
1.2.5
Choosing the Best High Availability Architecture
1.3
High Availability Information in Other Documentation
2
Oracle Application Server High Availability Framework
2.1
Process Management through OPMN
2.2
Replication of State Information
2.3
Load Balancing in Oracle Application Server
2.4
OracleAS Clusters
2.5
External Load Balancers
2.6
Backup and Recovery
2.6.1
Oracle Application Server Backup and Recovery Tool
2.7
Disaster Recovery
2.7.1
Oracle Application Server Guard
2.8
High Availability Topologies: Overview
2.8.1
Active-Active Topologies
2.8.2
Active-Passive Topologies: OracleAS Cold Failover Clusters
Part II Middle-tier High Availability
3
Active-Active Topologies
3.1
About Active-Active Topologies
3.1.1
OracleAS Clusters in Active-Active Topologies
3.1.2
Application-Level Clustering in Active-Active Topologies
3.1.2.1
Stateful Session EJB State Replication with OracleAS Cluster (OC4J)
3.1.3
Properties of Oracle Application Server Instances in Active-Active Topologies
3.1.4
About Groups
3.1.4.1
Creating Additional OC4J Instances
3.1.4.2
Managing Instances in a Group
3.1.4.3
Deploying Applications to a Group Using admin_client.jar
3.1.5
How Oracle HTTP Server Routes Requests to OC4J
3.1.6
Using Oracle Identity Management with Active-Active Topologies
3.1.7
Using Oracle HTTP Server 10.1.2 with Active-Active Topologies
3.1.8
Using OracleAS Web Cache Release 2 (10.1.2) with Active-Active Topologies
3.2
Managing the Active-Active Topology
3.2.1
Setting up OracleAS Clusters
3.2.1.1
Dynamic Discovery Method
3.2.1.2
Discovery Server Method
3.2.2
Setting up Multicast Replication
3.2.3
Setting up Peer-to-Peer Replication
3.2.4
Setting up Replication to a Database
3.2.5
Setting the Replication Policy
3.2.6
Specifying the Number of Nodes to Replicate To
3.2.7
Checking Status of Components
3.2.8
Starting / Stopping Components in the Topology
3.2.9
Deploying Applications to a Cluster
3.2.10
Adding Instances to an Active-Active Topology
3.2.11
Removing Instances from an Active-Active Topology
3.2.12
Setting mod_oc4j Load Balancing Options
3.2.13
Configuring Java Message Service (JMS) for High Availability
3.3
Summary of High Availability Features in Oracle HTTP Server and OC4J
3.4
Miscellaneous Topics
3.4.1
JNDI Namespace Replication
3.4.2
EJB Client Routing
3.4.3
OC4J Distributed Caching Using Java Object Cache
4
Active-Passive Topologies
4.1
About Active-Passive Topologies
4.2
Managing Active-Passive Topologies
4.2.1
Managing through Application Server Control Console
4.2.2
Starting / Stopping Components
4.2.3
Deploying Applications
4.3
Summary of High Availability Features in Oracle HTTP Server and OC4J in Active-Passive Topologies
Part III Disaster Recovery
5
OracleAS Disaster Recovery
5.1
Oracle Application Server 10
g
Disaster Recovery Solution
5.1.1
OracleAS Disaster Recovery Requirements
5.1.2
Supported Oracle Application Server Releases and Operating Systems
5.1.3
Supported Topologies
5.1.3.1
Symmetrical Topologies - Strict Mirror of the Production Site with Collocated Oracle Identity Management and OracleAS Metadata Repository Infrastructure
5.1.3.2
Asymmetrical Topologies - Simple Asymmetric Standby Topology with Collocated Oracle Identity Management and OracleAS Metadata Repository Infrastructure
5.1.3.3
Separate OracleAS Metadata Repository for OracleAS Portal with Collocated Oracle Identity Management and OracleAS Metadata Repository Infrastructure (the Departmental Topology)
5.1.3.4
Distributed Application OracleAS Metadata Repositories with Non Collocated Oracle Identity Management and OracleAS Metadata Repository Infrastructure
5.1.3.5
Redundant Multiple OracleAS 10.1.3 Homes J2EE Topology
5.1.3.6
Redundant Single OracleAS 10.1.3 Oracle Home J2EE Topology Integrated with an Existing Oracle Identity Management 10.1.2.0.2 Topology
5.2
Preparing the OracleAS Disaster Recovery Environment
5.2.1
Planning and Assigning Hostnames
5.2.1.1
Physical Hostnames
5.2.1.2
Network Hostnames
5.2.1.3
Virtual Hostname
5.2.2
Configuring Hostname Resolution
5.2.2.1
Using Local Hostnaming File Resolution
5.2.2.2
Using DNS Resolution
5.3
Overview of Installing Oracle Application Server
5.4
Overview of OracleAS Guard and asgctl
5.4.1
Overview of asgctl
5.4.2
OracleAS Guard Client
5.4.3
OracleAS Guard Server
5.4.4
asgctl Operations
5.4.5
OracleAS Guard Integration with OPMN
5.4.6
Supported OracleAS Disaster Recovery Configurations
5.4.7
Configuring OracleAS Guard and Other Relevant Information
5.5
Authentication of Databases
5.6
Discovering, Dumping, and Verifying the Topology
5.7
Dumping Policy Files and Using Policy Files With Some asgctl Commands
5.8
Discovering OracleAS 10.1.3 Instances in Redundant Multiple OracleAS 10.1.3 Homes J2EE Topology
5.9
Adding or Removing OracleAS 10.1.3 Instances to Redundant Single OracleAS 10.1.3 Home J2EE Topology Integrated with an Existing Oracle Identity Management 10.1.2.0.2 Topology
5.10
OracleAS Guard Operations -- Standby Site Cloning of One or More Production Instances to a Standby System
5.10.1
Cloning Single or Multiple Production Instances to a Standby System
5.11
OracleAS Guard Operations -- Standby Instantiation and Standby Synchronization
5.11.1
Standby Instantiation
5.11.2
Standby Synchronization
5.12
Runtime Operations -- OracleAS Guard Switchover and Failover Operations
5.12.1
Outages
5.12.1.1
Scheduled Outages
5.12.1.2
Unplanned Outages
5.13
Monitoring OracleAS Guard Operations and Troubleshooting
5.13.1
Verifying the Topology
5.13.2
Displaying the Current Operation
5.13.3
Displaying a List of Completed Operations
5.13.4
Stopping an Operation
5.13.5
Tracing Tasks
5.13.6
Writing Information About the Topology to a File
5.13.7
Error Messages
5.14
Wide Area DNS Operations
5.14.1
Using a Wide Area Load Balancer
5.14.2
Manually Changing DNS Names
5.15
Using OracleAS Guard Command-Line Utility (asgctl)
5.15.1
Typical OracleAS Guard Session Using asgctl
5.15.1.1
Getting Help
5.15.1.2
Specifying the Primary Database
5.15.1.3
Discovering the Topology
5.15.1.4
Creating and Executing an asgctl Script
5.15.2
Periodic Scheduling of OracleAS Guard asgctl Scripts
5.15.3
Submitting OracleAS Guard Jobs to the Enterprise Manager Job System
5.16
Special Considerations for Some OracleAS Metadata Repository Configurations
5.16.1
Special Considerations for Multiple OracleAS Metadata Repository Configurations
5.16.1.1
Setting asgctl Credentials
5.16.1.2
Specifying the Primary Database
5.16.1.3
Setting OracleAS Guard Port Numbers
5.16.2
Special Considerations for OracleAS Metadata Repository Configurations Created Using OracleAS Metadata Repository Creation Assistant
5.17
Special Considerations for OracleAS Disaster Recovery Environments
5.17.1
Some Special Considerations That Must Be Taken When Setting Up Some OracleAS Disaster Recovery Sites
5.17.2
Handling ons.conf and dsa.conf Configuration Files for Asymmetric Topologies
5.17.3
Other Special Considerations for OracleAS Disaster Recovery Environments
6
OracleAS Guard asgctl Command-line Reference
6.1
Information Common to OracleAS Guard asgctl Commands
6.2
Information Specific to a Small Set of OracleAS Guard Commands
6.2.1
Special Considerations for OracleAS Disaster Recovery Configurations in CFC Environments
6.2.1.1
Special Considerations for Running Instantiate and Failover Operations in CFC Environments
6.2.1.2
A Special Consideration and Workaround for Performing an Instantiate Operation in CFC Environments
6.2.1.3
Special Considerations for Running a Switchover Operations in CFC Environments
6.2.2
Other Special Considerations for OracleAS Disaster Recovery Environments
add instance
asgctl
clone instance
clone topology
connect asg
disconnect
discover topology
discover topology within farm
dump policies
dump topology
exit
failover
help
instantiate topology
quit
remove instance
set asg credentials
set echo
set new primary database
set noprompt
set primary database
set trace
show env
show operation
shutdown
shutdown topology
startup
startup topology
stop operation
switchover topology
sync topology
verify topology
dump farm (Deprecated)
instantiate farm (Deprecated)
shutdown farm (Deprecated)
startup farm (Deprecated)
switchover farm (Deprecated)
sync farm (Deprecated)
verify farm (Deprecated)
7
Manual Sync Operations
7.1
Manually Synchronizing Baseline Installation with Standby Site Without Using OracleAS Guard asgctl Command-line Utility
7.1.1
Manually Backing Up the Production Site
7.1.1.1
Shipping OracleAS Infrastructure Database Archive Logs
7.1.1.2
Backing Up Configuration Files (OracleAS Infrastructure and Middle Tier)
7.1.2
Manually Restoring to Standby Site
7.1.2.1
Restoring Configuration Files (OracleAS Infrastructure and Middle Tier)
7.1.2.2
Restoring the OracleAS Infrastructure Database - Applying Log Files
8
OracleAS Disaster Recovery Site Upgrade Procedure
8.1
Prerequisites
8.2
Disaster Recovery Topology
8.3
High-Level OracleAS Disaster Recovery Upgrade Steps
8.4
Patching an Existing OracleAS Disaster Recovery Environment
9
Setting Up a DNS Server
10
Secure Shell (SSH) Port Forwarding
10.1
SSH Port Forwarding
Part IV Appendices
A
Troubleshooting High Availability
A.1
Troubleshooting OracleAS Disaster Recovery Topologies
A.1.1
Standby Site Not Synchronized
A.1.2
Failure to Bring Up Standby Instances After Failover or Switchover
A.1.3
Switchover Operation Fails At the Step dcmctl resyncInstance -force -script
A.1.4
Unable to Start Standalone OracleAS Web Cache Installations at the Standby Site
A.1.5
Standby Site Middle-tier Installation Uses Wrong Hostname
A.1.6
Failure of Farm Verification Operation with Standby Farm
A.1.7
Sync Farm Operation Returns Error Message
A.1.8
On Windows Systems Use of asgctl startup Command May Fail If the PATH Environment Variable Has Exceeded 1024 Characters
A.2
Troubleshooting Middle-Tier Components
A.2.1
Using Multiple NICs with OracleAS Cluster (OC4J-EJB)
A.2.2
Performance Is Slow When Using the "opmn:" URL Prefix
A.3
Need More Help?
B
OracleAS Guard Error Messages
B.1
DGA Error Messages
B.1.1
LRO Error Messages
B.1.2
Undo Error Messages
B.1.3
Create Template Error Messages
B.1.4
Switchover Physical Standby Error Messages
B.2
Duf Error Messages
B.2.1
Database Error Messages
B.2.2
Connection and Network Error Messages
B.2.3
SQL*Plus Error Messages
B.2.4
JDBC Error Messages
B.2.5
OPMN Error Messages
B.2.6
Net Services Error Messages
B.2.7
LDAP or OID Error Messages
B.2.8
System Error Messages
B.2.9
Warning Error Messages
B.2.10
OracleAS Database Error Messages
B.2.11
OracleAS Topology Error Messages
B.2.12
OracleAS Backup and Restore Error Messages
B.2.13
OracleAS Guard Synchronize Error Messages
B.2.14
OracleAS Guard Instantiate Error Messages
Index
