When using RAT in an 11g environment please note that the capture is to a SQL Tuning Set and can be done using OEM

 

The capture process is made by DB Control (EM Express in 12c), Grid Control (or Cloud Control) or using the DBMS_WORKLOAD_CAPTURE package.

The capture files are saved to a directory that we created and configured in the capture process.

How to judge how much impact on the prod system or whatever source system.

 

RAT can be used to:
  • Evaluate new hardware, including migration from one platform to something completely different.
  • Verify execution of SQL from today’s production on a newer version of the database
  • Analyze the effect of changes in configuration
  • Scaling up, see how current system works with higher load; this works best for queries / reporting and not so well for data manipulation (DML).
A project involving RAT can be divided into these activities:
  1. Capture workload from a production system, can be done via OEM
  2. Create a clone of production system with flashback database enabled and a restore point created.
  3. Prepare for replay on test database and with agents on application servers or other client machines.
  4. Execute replay
  5. Generate reports (RAT and AWR)
  6. Flashback database
  7. If you haven’t reached a conclusion yet, repeat from 4.

 

Real Application Testing Users Guide

 

Real Application Testing 12c Webpage

 

RAT .pdf

Ready for Action?

LET'S GO!
Copyright 2024 IT Remote dot com
linkedin facebook pinterest youtube rss twitter instagram facebook-blank rss-blank linkedin-blank pinterest youtube twitter instagram