The database Capture/Replay feature of the Real Application Testing (RAT) suite enables you to capture the workload from a production database and replay it on a test or development environment.
In this blog, we’ll explore how to accomplish this when both your production and test databases are configured in a two-node RAC environment.
You should be aware that some workload operations are not supported, such as flashback queries and distributed transactions.
The capture procedure on a RAC database is the same as for a single instance database, you just need to run it on one of the instances, without adding an instance filter.
At the end of the capture, you should generate an html summary, and export related AWR data, for that, you’ll need the ID of you capture.
To prepare the replay you need two things :
The captured raw files must be processed by the database, before the capture could be replayed, this step could take some time depending of the size of the workload raw files.
Then we initiate the replay (just an initiation, the replay is not yet started).
Checking the status of the replay.
Based on this calibration, and after checking the cpu and memory available, I will use 56 clients (56 x 152 MB = 8.5G of minimal memory needed for the clients : Ok for me).