Real Application Testing: Database Capture FAQ
(Doc ID 1920275.1)
Last updated on OCTOBER 11, 2021
Oracle Database Backup Service - Version N/A and later Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Oracle Database Exadata Express Cloud Service - Version N/A and later Oracle Database Cloud Exadata Service - Version N/A and later Information in this document applies to any platform.
Real Application Testing
The purpose of this FAQ is to provide answers to commonly asked questions. Many of the answers are based upon real world customer experience.
The first step in using Database Replay is to capture a production workload. Capturing a workload involves recording all requests made by external clients to the Oracle Database.
When workload capture is enabled, all external client requests directed to Oracle Database are tracked and stored on the file system in binary files called capture files. The location where the capture files will be stored can be specified. Once workload capture begins, all external database calls are written to the capture files. The capture files contain all relevant information about the client request, such as SQL text, bind values, and transaction information. Background activities and database scheduler jobs are not captured. The capture files are platform independent and can be transported to another system for replay.
Questions and Answers
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!