DBA Hub

📋Steps in this guide1/20

Performance Tuning Checklist After Oracle Migration

Optimize your Oracle migration with this complete performance tuning checklist. Learn key steps—parameter validation, statistics gathering, SQL tuning, memory optimization, indexing, and monitoring—to ensure smooth post-migration performance.

oracle configurationintermediate
by OracleDba
19 views
1

Check Hardware & OS Settings

- Validate CPU, RAM, storage, and IOPS match expected values. Validate CPU, RAM, storage, and IOPS match expected values. - Confirm Transparent HugePages are disabled (recommended for Oracle). Confirm Transparent HugePages are disabled (recommended for Oracle). - Verify swap configuration and file system mount options. Verify swap configuration and file system mount options.
2

Validate Kernel Parameters

- Ensure , , , , are correctly configured. Ensure , , , , are correctly configured. - Recheck network settings like , , . Recheck network settings like , , .
3

2. Verify Oracle Initialization Parameters

Many parameters may change when moving between versions or platforms.
4

Important Checks

- Compare old vs new values. Compare old vs new values. - Validate SGA and PGA sizing. Validate SGA and PGA sizing. - Check optimizer-related parameters: Check optimizer-related parameters: - - - - Confirm deprecated parameters are removed. Confirm deprecated parameters are removed.
5

Memory Tuning

- Enable Automatic Memory Management (AMM) or Automatic Shared Memory Management (ASMM) . Enable Automatic Memory Management (AMM) or Automatic Shared Memory Management (ASMM) . - Verify PGA aggregate target and SGA target values. Verify PGA aggregate target and SGA target values.
6

3. Recompile Invalid Objects

After migration, invalid objects can cause sudden performance issues. Run: And validate using:
7

Gather Statistics on Schema Objects

- Ensure table, index, and column stats are updated. Ensure table, index, and column stats are updated. - Compare statistics freshness with pre-migration values. Compare statistics freshness with pre-migration values.
8

5. Validate Execution Plans

Execution plans may change due to a new optimizer version.
9

Action Items

- Compare execution plans before and after migration. Compare execution plans before and after migration. - Capture SQL performance baselines. Capture SQL performance baselines. - Create SQL Plan Baselines (SPM) if needed: Create SQL Plan Baselines (SPM) if needed:
10

6. Check Index Health

Migration can affect index usage or cause fragmentation. Checklist: - Look for unusable indexes. Look for unusable indexes. - Rebuild fragmented indexes. Rebuild fragmented indexes. - Validate bitmap, function-based, and domain indexes. Validate bitmap, function-based, and domain indexes.
11

7. Monitor Top SQL Queries

After migration, track the workload closely.
12

Use tools such as:

- AWR Reports AWR Reports - ASH Reports ASH Reports - SQL Monitor SQL Monitor - OEM Cloud Control OEM Cloud Control
13

Key Metrics to Monitor:

- CPU usage CPU usage - Wait events (db file sequential read, CPU wait, latch waits) Wait events (db file sequential read, CPU wait, latch waits) - I/O latencies I/O latencies - Temp usage Temp usage - Buffer cache hit ratio Buffer cache hit ratio
14

Redo Tuning

- Validate redo log size. Validate redo log size. - Check log switch frequency. Check log switch frequency.
15

Undo Tuning

- Review undo tablespace size. Review undo tablespace size. - Check for ORA-01555 snapshots. Check for ORA-01555 snapshots.
16

Temp Tuning

- Check temp spills. Check temp spills. - Validate size and autoextend settings. Validate size and autoextend settings.
17

Validate Connectivity & Network Performance

- Check TNS, SCAN, listeners, and connection pools. Check TNS, SCAN, listeners, and connection pools. - Validate JDBC or app driver versions. Validate JDBC or app driver versions. - Test network latency between app → DB → storage. Test network latency between app → DB → storage.
18

Validate Jobs, Schedulers & Replication

- Ensure all DBMS_SCHEDULER jobs run as expected. Ensure all DBMS_SCHEDULER jobs run as expected. - Validate Data Guard sync, if used. Validate Data Guard sync, if used. - Check GoldenGate extract/replicat performance. Check GoldenGate extract/replicat performance.
19

Review Alert Logs & Trace Files

Search for: - ORA-errors ORA-errors - Process restarts Process restarts - Memory pressure Memory pressure - I/O related warnings I/O related warnings
20

Perform Load Testing

Run application-level performance tests to confirm: - Response time consistency Response time consistency - End-to-end throughput End-to-end throughput - Concurrent sessions handling Concurrent sessions handling

Comments (0)

Please to add comments

No comments yet. Be the first to comment!