Moving to Oracle Database@AWS changes network topology, potentially altering SQL*Net latency between applications and the database. The CRET methodology leverages AWR, Active Session History, and SQL Trace to pinpoint latency-sensitive queries before migration. This three-phase approach allows teams to quantify performance impacts proactively rather than reacting to issues post-deployment.
- Use the CRET methodology to characterize baseline latency before migrating to Oracle Database@AWS.
- Leverage AWR and Active Session History to identify SQL statements sensitive to network delays.
- Apply SQL Trace for granular visibility into specific query execution times during the assessment.
- Quantify potential latency shifts to ensure application performance meets SLAs in the new environment.
Fleet impact: For Oracle ExaCC/RAC fleets, this is critical as proximity to compute nodes changes; use CRET to validate that SQL*Net round-trips remain within acceptable thresholds for latency-sensitive workloads before cutover.
