13 Using Consolidated Database Replay

13.1.1 Use Cases for Consolidated Database Replay

Some typical use cases for Consolidated Database Replay include:

• Stress Testing

• Scale-Up Testing

13.1.2 Workload Scale-Up Techniques

This section describes the following workload scale-up techniques:

• About Time Shifting

• About Workload Folding

• About Schema Remapping

13.2.1 Capturing Database Workloads for Consolidated Database Replay

Consolidated Database Replay does not require any special steps for capturing database workloads. The steps for capturing database workloads are exactly the same as for capturing a single workload for Database Replay, as described in Chapter 9, "Capturing a Database Workload".

This section contains the following topics for workload captures that are specific to Consolidated Database Replay:

• Supported Types of Workload Captures

• Capture Subsets

13.2.2 Setting Up the Test System for Consolidated Database Replay

Setting up the test system for Consolidated Database Replay is similar to setting up a test system for Database Replay, as described in "Steps for Replaying a Database Workload". However, there are some additional considerations when setting up a replay database for Consolidated Database Replay.

To minimize divergence during the replay, the test system should contain the same application data and the state of the application data should be logically equivalent to that of the capture system at the start time of each workload capture. However, because a consolidated capture may contain multiple workload captures from different production systems, the test system needs to be set up for all the captures.

For Consolidated Database Replay, all participating workload captures must be placed under a new capture directory on the test system. You can copy all the workload captures into the new capture directory, or create symbolic links pointing to the original workload captures. Before consolidating the workload captures, ensure that the new capture directory has enough disk space to store all participating captures.

Figure 13-1 illustrates how to set up the test system and new capture directory to consolidate three workload captures.

Figure 13-1 Setting Up the Test System for Consolidated Database Replay

Description of "Figure 13-1 Setting Up the Test System for Consolidated Database Replay"

13.2.3 Preprocessing Database Workloads for Consolidated Database Replay

Preprocessing a database workload for Consolidated Database Replay is similar to preprocessing a database workload for Database Replay, as described in Chapter 10, "Preprocessing a Database Workload".

For Consolidated Database Replay, preprocess each captured workload into its own directory. Do not combine different workload captures into one directory for preprocessing. Preprocessing of captured workloads must be performed using a database running the same version of Oracle Database as that of the test system where the workloads will be replayed.

13.2.4 Replaying Database Workloads for Consolidated Database Replay

Replaying consolidated workloads using Consolidated Database Replay is quite different from replaying a single database workload using Database Replay.

This section contains the following topics for replaying workloads that are specific to Consolidated Database Replay:

• Defining Replay Schedules

• Remapping Connections for Consolidated Database Replay

• Remapping Users for Consolidated Database Replay

• Preparing for Consolidated Database Replay

• Replaying Individual Workloads

13.2.5 Reporting and Analysis for Consolidated Database Replay

Reporting and analysis for Consolidated Database Replay is performed using the replay compare period report, as described in "Using Compare Period Reports".

The replay compare period report for Consolidated Database Replay identifies the Active Session History (ASH) data for each individual workload capture and compares the ASH data from the workload capture to the filtered ASH data from the consolidated replay. Use this report to compare replays of the same consolidated workload capture.

The replay compare period report for Consolidated Database Replay treats the consolidated replay as multiple Capture vs. Replay comparisons. The summary section of the report contains a table that summarizes all individual Capture vs. Replay comparisons. Review the information in this section to gain a general understanding of how the consolidated replay ran.

Figure 13-2 shows the summary section of a sample replay compare period report for Consolidated Database Replay.

Figure 13-2 Compare Period Report: Consolidated Replay

Description of "Figure 13-2 Compare Period Report: Consolidated Replay"

The rest of the sections in the report resemble the ASH Data Comparison section of the replay compare period report and are formed by joining all Capture vs. Replay reports in the consolidated replay. For a description of this section, see "ASH Data Comparison".

13.3.1 Generating Capture Subsets Using APIs

This section describes how to generate capture subsets from existing workload captures using the DBMS_WORKLOAD_REPLAY package. For information about capture subsets, see "Capture Subsets".

To generate a capture subset from existing workload captures: 

1. Use the GENERATE_CAPTURE_SUBSET procedure:

   DBMS_WORKLOAD_REPLAY.GENERATE_CAPTURE_SUBSET (
      input_capture_dir        IN VARCHAR2,
      output_capture_dir       IN VARCHAR2,
      new_capture_name         IN VARCHAR2,
      begin_time               IN NUMBER,
      begin_include_incomplete IN BOOLEAN   DEFAULT TRUE,
      end_time                 IN NUMBER,
      end_include_incomplete   IN BOOLEAN   DEFAULT FALSE,
      parallel_level           IN NUMBER    DEFAULT NULL);
   

2. Set the input_capture_dir parameter to the name of the directory object that points to an existing workload capture.

3. Set the output_capture_dir parameter to the name of the directory object that points to an empty directory where the new workload capture will be stored.

4. Set the new_capture_name parameter to the name of the new workload capture that is to be generated.

5. Set the other parameters, which are optional, as appropriate.

   For information about these parameters, see Oracle Database PL/SQL Packages and Types Reference.

Example 13-1 shows how to create a capture subset named peak_wkld at directory object peak_capdir from an existing workload capture at directory object rec_dir. The capture subset includes workload from 2 hours after the start of the workload capture (or 7,200 seconds) to 3 hours after the start of the workload capture (or 10,800 seconds).

EXEC DBMS_WORKLOAD_REPLAY.GENERATE_CAPTURE_SUBSET ('rec_dir', 'peak_capdir',
     'peak_wkld', 7200, TRUE, 10800, FALSE, 1);

13.3.2 Setting the Replay Directory Using APIs

This section describes how to set the replay directory on the test system using the DBMS_WORKLOAD_REPLAY package. Set the replay directory to a directory on the test system that contains the workload captures to be replayed. For information about setting up the test system, see "Setting Up the Test System for Consolidated Database Replay".

To set the replay directory: 

1. Use the SET_REPLAY_DIRECTORY procedure:

   DBMS_WORKLOAD_REPLAY.SET_REPLAY_DIRECTORY (
      replay_dir IN VARCHAR2);
   

2. Set the replay_dir parameter to the name of the directory object that points to the operating system directory containing the workload captures to be used for workload consolidation.

Example 13-2 shows how to set the replay directory to a directory object named rep_dir.

EXEC DBMS_WORKLOAD_REPLAY.SET_REPLAY_DIRECTORY ('rep_dir');

You can also use the DBMS_WORKLOAD_REPLAY package to view the current replay directory that has been set by the SET_REPLAY_DIRECTORY procedure.

To view the current replay directory that has been set: 

• Use the GET_REPLAY_DIRECTORY function:

  DBMS_WORKLOAD_REPLAY.GET_REPLAY_DIRECTORY RETURN VARCHAR2;
  

  If no replay directory has been set, then the function returns NULL.

13.3.3 Defining Replay Schedules Using APIs

This section describes how to define replay schedules using the DBMS_WORKLOAD_REPLAY package. For information about replay schedules, see "Defining Replay Schedules".

Before defining replay schedules, ensure that the following prerequisites are met:

• All workload captures are preprocessed using the PROCESS_CAPTURE procedure on a system running the same database version as the replay system, as described in Chapter 10, "Preprocessing a Database Workload".

• All capture directories are copied to the replay directory on the replay system

• Replay directory is set using the SET_REPLAY_DIRECTORY procedure, as described in "Setting the Replay Directory Using APIs".

• Database state is not in replay mode

To define replay schedules: 

1. Create a new replay schedule, as described in "Creating Replay Schedules Using APIs".

2. Add workload captures to the replay schedule, as described in "Adding Workload Captures to Replay Schedules Using APIs".

3. Add schedule orders to the replay schedule, as described in "Adding Schedule Orders to Replay Schedules Using APIs".

4. Save the replay schedule, as described in "Saving Replay Schedules Using APIs".

EXEC DBMS_WORKLOAD_REPLAY.BEGIN_REPLAY_SCHEDULE ('peak_schedule');

SELECT DBMS_WORKLOAD_REPLAY.ADD_CAPTURE ('peak_wkld')
  FROM dual;

13.3.4 Running Consolidated Database Replay Using APIs

This section describes how to run Consolidated Database Replay using the DBMS_WORKLOAD_REPLAY package. For information about consolidated replay, see "Replaying Database Workloads for Consolidated Database Replay".

Before running Consolidated Database Replay, ensure that the following prerequisites are met:

• All workload captures are preprocessed using the PROCESS_CAPTURE procedure on a system running the same database version as the replay system, as described in Chapter 10, "Preprocessing a Database Workload".

• All capture directories are copied to the replay directory on the replay system

• Replay directory is set using the SET_REPLAY_DIRECTORY procedure, as described in "Setting the Replay Directory Using APIs".

• Database is logically restored to the same application state as that of all the capture systems at the start time of all workload captures.

To run Consolidated Database Replay: 

1. Initialize the replay data, as described in "Initializing Consolidated Database Replay Using APIs".

2. Remap connections strings, as described in "Remapping Connection Using APIs".

3. Remap users, as described in "Remapping Users Using APIs".

   Remapping users is optional.

4. Prepare the consolidated replay, as described in "Preparing for Consolidated Database Replay Using APIs".

5. Set up and start the replay clients, as described in "Setting Up Replay Clients".

6. Start the consolidated replay, as described in "Starting Consolidated Database Replay Using APIs".

7. Generate reports and perform analysis, as described in "Reporting and Analysis for Consolidated Database Replay".

EXEC DBMS_WORKLOAD_REPLAY.INITIALIZE_CONSOLIDATED_REPLAY ('peak_replay',
     'peak_schedule');

EXEC DBMS_WORKLOAD_REPLAY.SET_USER_MAPPING (1001, 'PROD', 'TEST');

13.4.1 Using Time Shifting

This section describes how to use time shifting with Consolidated Database Replay, and assumes a scenario where you want to use time shifting to align the peaks of workloads captured from three applications and replay them simultaneously. The scenario demonstrates how to use time shifting for stress testing. For more information about time shifting, see "About Time Shifting".

This scenario uses the following assumptions:

• The first workload is captured from the Sales application.

• The second workload is captured from the CRM application and its peak time occurs 1 hour before that of the Sales workload.

• The third workload is captured from the DW application and its peak time occurs 30 minutes before that of the Sales workload.

• To align the peaks of these workloads, time shifting is performed by adding a delay of one hour to the CRM workload and a delay of 30 minutes to the DW workload during replay.

To perform time shifting in this scenario: 

1. On the replay system which will undergo stress testing, create a directory object for the root directory where the captured workloads are stored:

   CREATE [OR REPLACE] DIRECTORY cons_dir AS '/u01/test/cons_dir';
   

2. Preprocess the individual workload captures into separate directories:

   • For the Sales workload:

     1. Create a directory object:

        CREATE [OR REPLACE] DIRECTORY sales AS '/u01/test/cons_dir/cap_sales';
        

     2. Ensure that the captured workload from the Sales application is stored in this directory.

     3. Preprocess the workload:

        EXEC DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE ('SALES');
        

   • For the CRM workload:

     1. Create a directory object:

        CREATE [OR REPLACE] DIRECTORY crm AS '/u01/test/cons_dir/cap_crm';
        

     2. Ensure that the captured workload from the CRM application is stored in this directory.

     3. Preprocess the workload:

        EXEC DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE ('CRM');
        

   • For the DW workload:

     1. Create a directory object:

        CREATE [OR REPLACE] DIRECTORY DW AS '/u01/test/cons_dir/cap_dw';
        

     2. Ensure that the captured workload from the DW application is stored in this directory.

     3. Preprocess the workload:

        EXEC DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE ('DW');
        

3. Set the replay directory to the root directory:

   EXEC DBMS_WORKLOAD_REPLAY.SET_REPLAY_DIRECTORY ('CONS_DIR');
   

4. Create a replay schedule and add the workload captures:

   EXEC DBMS_WORKLOAD_REPLAY.BEGIN_REPLAY_SCHEDULE ('align_peaks_schedule');
   SELECT DBMS_WORKLOAD_REPLAY.ADD_CAPTURE ('SALES') FROM dual;
   SELECT DBMS_WORKLOAD_REPLAY.ADD_CAPTURE ('CRM', 3600) FROM dual;
   SELECT DBMS_WORKLOAD_REPLAY.ADD_CAPTURE ('DW', 1800) FROM dual;
   EXEC DBMS_WORKLOAD_REPLAY.END_REPLAY_SCHEDULE;
   

   Note that a delay of 3,600 seconds (or 1 hour) is added to the CRM workload, and a delay of 1,800 seconds (or 30 minutes) is added to the DW workload.

5. Initialize the consolidated replay:

   EXEC DBMS_WORKLOAD_REPLAY.INITIALIZE_CONSOLIDATED_REPLAY ('align_peaks_replay',
                             'align_peaks_schedule');
   

6. Remap connections:

   1. Query the DBA_WORKLOAD_CONNECTION_MAP view for the connection mapping information:

      SELECT schedule_cap_id, conn_id, capture_conn, replay_conn
        FROM dba_workload_connection_map;
      

   2. Remap the connections:

      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 1,
           conn_id => 1, replay_connection => 'inst1');
      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 1,
           conn_id => 2, replay_connection => 'inst1');
      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 2,
           conn_id => 1, replay_connection => 'inst2');
      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 2,
           conn_id => 2, replay_connection => 'inst2');
      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 3,
           conn_id => 1, replay_connection => 'inst3');
      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 3,
           conn_id => 2, replay_connection => 'inst3');
      

      The replay_connection parameter represents the services that are defined on the test system.

   3. Verify the connection remappings:

      SELECT schedule_cap_id, conn_id, capture_conn, replay_conn
        FROM dba_workload_connection_map;
      

7. Prepare the consolidated replay:

   EXEC DBMS_WORKLOAD_REPLAY.PREPARE_CONSOLIDATED_REPLAY;
   

8. Start replay clients:

   1. Estimate the number of replay clients that are required:

      wrc mode=calibrate replaydir=/u01/test/cons_dir/cap_sales
      wrc mode=calibrate replaydir=/u01/test/cons_dir/cap_crm
      wrc mode=calibrate replaydir=/u01/test/cons_dir/cap_dw
      

   2. Add the output to determine the number of replay clients required.

      You will need to start at least one replay client per workload capture contained in the consolidated workload.

   3. Start the required number of replay clients by repeating this command:

      wrc username/password mode=replay replaydir=/u01/test/cons_dir
      

      The replaydir parameter is set to the root directory in which the workload captures are stored.

9. Start the consolidated replay:

   EXEC DBMS_WORKLOAD_REPLAY.START_CONSOLIDATED_REPLAY;
   

13.4.2 Using Workload Folding

This section describes how to use workload folding with Consolidated Database Replay, and assumes a scenario where you want to use workload folding to triple a captured workload. The scenario demonstrates how to use workload folding for scale-up testing. For more information about workload folding, see "About Workload Folding".

This scenario uses the following assumptions:

• The original workload was captured from 2 a.m. to 8 p.m. and folded into three capture subsets.

• The first capture subset contains part of the original workload from 2 a.m. to 8 a.m.

• The second capture subset contains part of the original workload from 8 a.m. to 2 p.m.

• The third capture subset contains part of the original workload from 2 p.m. to 8 p.m.

• To triple the workload during replay, workload folding is performed by replaying the three capture subsets simultaneously.

To perform workload folding in this scenario: 

1. On the replay system where you plan to perform scale-up testing, create a directory object for the root directory where the captured workloads are stored:

   CREATE [OR REPLACE] DIRECTORY cons_dir AS '/u01/test/cons_dir';
   

2. Create a directory object for the directory where the original workload is stored:

   CREATE [OR REPLACE] DIRECTORY cap_monday AS '/u01/test/cons_dir/cap_monday';
   

3. Create directory objects for the directories where you are planning to store the capture subsets:

   1. Create a directory object for the first capture subset:

      CREATE [OR REPLACE] DIRECTORY cap_mon_2am_8am
                                 AS '/u01/test/cons_dir/cap_monday_2am_8am';
      

   2. Create a directory object for the second capture subset:

      CREATE [OR REPLACE] DIRECTORY cap_mon_8am_2pm
                                 AS '/u01/test/cons_dir/cap_monday_8am_2pm';
      

   3. Create a directory object for the third capture subset:

      CREATE [OR REPLACE] DIRECTORY cap_mon_2pm_8pm
                                 AS '/u01/test/cons_dir/cap_monday_2pm_8pm';
      

4. Create the capture subsets:

   1. Generate the first capture subset for the time period from 2 a.m. to 8 a.m.:

      EXEC DBMS_WORKLOAD_REPLAY.GENERATE_CAPTURE_SUBSET ('CAP_MONDAY',
                                'CAP_MON_2AM_8AM', 'mon_2am_8am_wkld',
                                0, TRUE, 21600, FALSE, 1);
      

   2. Generate the second capture subset for the time period from 8 a.m. to 2 p.m.:

      EXEC DBMS_WORKLOAD_REPLAY.GENERATE_CAPTURE_SUBSET ('CAP_MONDAY',
                                'CAP_MON_8AM_2PM', 'mon_8am_2pm_wkld',
                                21600, TRUE, 43200, FALSE, 1);
      

   3. Generate the third capture subset for the time period from 2 p.m. to 8 p.m.:

      EXEC DBMS_WORKLOAD_REPLAY.GENERATE_CAPTURE_SUBSET ('CAP_MONDAY',
                                'CAP_MON_2PM_8PM', 'mon_2pm_8pm_wkld',
                                43200, TRUE, 0, FALSE, 1);
      

5. Preprocess the capture subsets:

   EXEC DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE ('CAP_MON_2AM_8AM');
   EXEC DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE ('CAP_MON_8AM_2PM');
   EXEC DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE ('CAP_MON_2PM_8PM');
   

6. Set the replay directory to the root directory:

   EXEC DBMS_WORKLOAD_REPLAY.SET_REPLAY_DIRECTORY ('CONS_DIR');
   

7. Create a replay schedule and add the capture subsets:

   EXEC DBMS_WORKLOAD_REPLAY.BEGIN_REPLAY_SCHEDULE ('monday_folded_schedule');
   SELECT DBMS_WORKLOAD_REPLAY.ADD_CAPTURE ('CAP_MON_2AM_8AM') FROM dual;
   SELECT DBMS_WORKLOAD_REPLAY.ADD_CAPTURE ('CAP_MON_8AM_2PM') FROM dual;
   SELECT DBMS_WORKLOAD_REPLAY.ADD_CAPTURE ('CAP_MON_2PM_8PM') FROM dual;
   EXEC DBMS_WORKLOAD_REPLAY.END_REPLAY_SCHEDULE;
   

8. Initialize the consolidated replay:

   EXEC DBMS_WORKLOAD_REPLAY.INITIALIZE_CONSOLIDATED_REPLAY (
                             'monday_folded_replay', 'monday_folded_schedule);
   

9. Remap connections:

   1. Query the DBA_WORKLOAD_CONNECTION_MAP view for the connection mapping information:

      SELECT schedule_cap_id, conn_id, capture_conn, replay_conn
        FROM dba_workload_connection_map;
      

   2. Remap the connections:

      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 1,
           conn_id => 1, replay_connection => 'inst1');
      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 1,
           conn_id => 2, replay_connection => 'inst1');
      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 2,
           conn_id => 1, replay_connection => 'inst2');
      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 2,
           conn_id => 2, replay_connection => 'inst2');
      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 3,
           conn_id => 1, replay_connection => 'inst3');
      EXEC DBMS_WORKLOAD_REPLAY.REMAP_CONNECTION (schedule_cap_id => 3,
           conn_id => 2, replay_connection => 'inst3');
      

      The replay_connection parameter represents the services that are defined on the test system.

   3. Verify the connection remappings:

      SELECT schedule_cap_id, conn_id, capture_conn, replay_conn
        FROM dba_workload_connection_map;
      

10. Prepare the consolidated replay:

    EXEC DBMS_WORKLOAD_REPLAY.PREPARE_CONSOLIDATED_REPLAY;
    

11. Start replay clients:

    1. Estimate the number of replay clients that are required:

       wrc mode=calibrate replaydir=/u01/test/cons_dir/cap_monday_2am_8am
       wrc mode=calibrate replaydir=/u01/test/cons_dir/cap_monday_8am_2pm
       wrc mode=calibrate replaydir=/u01/test/cons_dir/cap_monday_2pm_8pm
       

    2. Add the output to determine the number of replay clients required.

       You will need to start at least one replay client per workload capture contained in the consolidated workload.

    3. Start the required number of replay clients by repeating this command:

       wrc username/password mode=replay replaydir=/u01/test/cons_dir
       

       The replaydir parameter is set to the root directory in which the workload captures are stored.

12. Start the consolidated replay:

    EXEC DBMS_WORKLOAD_REPLAY.START_CONSOLIDATED_REPLAY;
    

13.4.3 Using Schema Remapping

This section describes how to use schema remapping with Consolidated Database Replay, and assumes a scenario where you want to use schema remapping to identify possible host bottlenecks when deploying multiple instances of an application. The scenario demonstrates how to use schema remapping for scale-up testing. For more information about schema remapping, see "About Schema Remapping".

This scenario uses the following assumptions:

• A single workload exists that is captured from the Sales application.

• To set up the replay system with multiple schemas from the Sales schema, schema remapping is performed by adding the captured workload multiple times into a replay schedule and remapping the users to different schemas.

To perform schema remapping in this scenario: 

1. On the replay system where you plan to perform scale-up testing, create a directory object for the root directory where the captured workloads are stored:

   CREATE [OR REPLACE] DIRECTORY cons_dir AS '/u01/test/cons_dir';
   

2. Create a directory object for the directory where the captured workload is stored:

   CREATE [OR REPLACE] DIRECTORY cap_sales AS '/u01/test/cons_dir/cap_sales';
   

   Ensure that the captured workload from the Sales application is stored in this directory.

3. Preprocess the captured workload:

   EXEC DBMS_WORKLOAD_REPLAY.PROCESS_CAPTURE ('SALES');
   

4. Set the replay directory to the root directory:

   EXEC DBMS_WORKLOAD_REPLAY.SET_REPLAY_DIRECTORY ('CONS_DIR');
   

5. Create a replay schedule and add the captured workload multiple times:

   EXEC DBMS_WORKLOAD_REPLAY.BEGIN_REPLAY_SCHEDULE ('double_sales_schedule');
   SELECT DBMS_WORKLOAD_REPLAY.ADD_CAPTURE ('CAP_SALES') FROM dual;
   SELECT DBMS_WORKLOAD_REPLAY.ADD_CAPTURE ('CAP_SALES') FROM dual;
   EXEC DBMS_WORKLOAD_REPLAY.END_REPLAY_SCHEDULE;
   

6. Initialize the consolidated replay:

   EXEC DBMS_WORKLOAD_REPLAY.INITIALIZE_CONSOLIDATED_REPLAY (
                             'double_sales_replay', 'double_sales_schedule);
   

7. Remap the users:

   EXEC DBMS_WORKLOAD_REPLAY.SET_USER_MAPPING (2, 'sales_usr', 'sales_usr_2');
   

8. Prepare the consolidated replay:

   EXEC DBMS_WORKLOAD_REPLAY.PREPARE_CONSOLIDATED_REPLAY;
   

9. Start replay clients:

   1. Estimate the number of replay clients that are required:

      wrc mode=calibrate replaydir=/u01/test/cons_dir/cap_sales
      

   2. Add the output to determine the number of replay clients required.

      You will need to start at least one replay client per workload capture contained in the consolidated workload.

   3. Start the required number of replay clients by repeating this command:

      wrc username/password mode=replay replaydir=/u01/test/cons_dir
      

      The replaydir parameter is set to the root directory in which the workload captures are stored.

10. Start the consolidated replay:

    EXEC DBMS_WORKLOAD_REPLAY.START_CONSOLIDATED_REPLAY;