Modernising Oracle RAC: compare requirements, not product names

The key question

RAC may be part of a mature availability and performance architecture. A move to another platform should therefore not be based on node-count comparisons alone.

What to inventory

• Capture services, connection paths and load distribution.
• Define acceptable interruption and tolerated data loss with the business.
• Document maintenance, backups and historical failure scenarios.

Design the target deliberately

First define the write and read workload and the availability objectives that are actually required. A primary/standby design or managed cluster has different properties from Oracle RAC. Also test how the application handles broken connections and transactions whose outcome is uncertain.

A concrete validation step

Do not stop a failover test when the database becomes reachable. Continue a representative business process and check for missing data, duplicates and manual recovery work.

Evidence required before sign-off

• Break a connection during a write transaction.
• Test reconnect and business-level restart.
• Measure failover and return to normal operation.
• Define operational ownership and escalation paths clearly.