Oracle Database@AWS colocates Exadata infrastructure within AWS data centers, which alters the network path and potentially the SQL*Net latency experienced by applications. To mitigate migration risks, this post introduces the CRET methodology, a structured approach using AWR, Active Session History, and SQL Trace. This framework helps teams identify latency-sensitive SQL statements and quantify performance impacts prior to cutover.
- Colocation in AWS data centers changes the network topology, affecting SQL*Net round-trip times.
- Use the CRET methodology to systematically profile application database interactions before migration.
- Leverage AWR and Active Session History to isolate high-latency queries and sessions.
- Apply SQL Trace to capture granular timing data for sensitive statements.
- Quantify latency deltas early to adjust application connection pools or retry logic.
Fleet impact: For Oracle ExaCC/RAC fleets, verify that the new AWS interconnect meets or exceeds your current storage network performance metrics. Plan to update connection descriptors or use Oracle Net Services features like TNS Ping and SQL*Net tracing in your pre-migration validation suite to catch regressions in latency-sensitive OLTP workloads.
