Oracle Database@AWS moves Exadata infrastructure into AWS data centers, altering network paths and potentially impacting SQL*Net latency. To address this, AWS provides the CRET methodology, a three-phase approach using AWR, Active Session History, and SQL Trace. This process helps teams identify latency-sensitive SQL and quantify migration impacts before going live.
- Oracle Database@AWS changes network topology, requiring new latency baselines.
- Use AWR and Active Session History to pinpoint high-latency SQL statements.
- SQL Trace helps quantify the specific performance impact of network changes.
- Characterize latency pre-migration to avoid unexpected application slowdowns.
Fleet impact: For ExaCC/RAC fleets, this methodology is critical for establishing a pre-migration latency baseline to ensure application SLAs are met after moving to the AWS-hosted Exadata infrastructure. Check network path changes and monitor SQL*Net round trips during the CRET analysis phase.
