Moving to Oracle Database@AWS places Exadata infrastructure within AWS data centers, which can alter SQL*Net latency profiles for connected applications. The new CRET methodology leverages AWR, Active Session History, and SQL Trace to identify latency-sensitive SQL before migration. This three-phase approach allows teams to quantify the specific impact on their existing workloads.
- Oracle Database@AWS changes network topology, making pre-migration latency characterization critical.
- Use the CRET methodology to systematically identify SQL*Net bottlenecks in your application.
- Leverage AWR, Active Session History, and SQL Trace for granular latency quantification.
- Validate performance impacts before cutover to avoid unexpected application degradation.
Fleet impact: For ExaCC/RAC fleets, this change in network path between app and database tier requires validating round-trip times for critical transactions. Check AWR reports for SQL*Net message waits to baseline current performance and adjust connection pooling or retry logic if latency spikes occur in the new AWS-hosted Exadata environment.
