Graceful Application Switchover in RAC with No Application Interruption
(Doc ID 1593712.1)
Last updated on AUGUST 04, 2018
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.1 and laterInformation in this document applies to any platform.
Purpose
This document discusses what is needed to manage a graceful application switchover between RAC nodes with no application interruption.
Scope
This document is intended for architects, database administrators, and application developers.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| Recommended Graceful Application Switchover Procedure |
| Prerequisites |
| Procedure |
| 1. Check current status of the services and related instances to ensure services can be moved successfully |
| 2. Stop services normally (not using FORCE option) on the node to be maintained |
| 3. Disable the service so clusterware does not bring up the service until the proper time should an unplanned outage occur |
| 4. Disconnect long-running sessions after the current transaction completes |
| 5. Repeat Steps 2 - 4 for all services affected by the maintenance |
| 6. Shutdown the database instance |
| 7. Perform desired maintenance |
| 8. Start up instance(s) on the node |
| 9. Enable services that were previously disabled |
| 10. Start services that were stopped |
| 11. Observe that connections are appearing on the service again |
| 12. Repeat this procedure for each node or instances that needs to be shutdown for maintenance |
| Understanding Your Application's Use of Connections |
| Services and Application Configuration Best Practices |
| Community Discussions |
| References |