Oracle Database@AWS hosts Exadata infrastructure within AWS data centers, which can alter SQL*Net latency profiles for applications. The CRET methodology leverages AWR, Active Session History, and SQL Trace to identify latency-sensitive SQL and quantify performance impacts prior to migration. This approach enables teams to characterize network behavior changes and plan accordingly.
- ExaCC@AWS changes network topology, potentially affecting SQL*Net response times.
- Use AWR, ASH, and SQL Trace to pinpoint latency-sensitive SQL statements.
- Quantify pre-migration latency baselines to predict post-migration performance.
- Identify application-level bottlenecks before committing to the migration.
Fleet impact: For ExaCC and RAC fleets, validate network routing and packet sizes to ensure SQL*Net paths remain optimal. Monitor AWR reports for increased 'SQL*Net message from client' waits post-migration to adjust application connection pooling or retry logic.
