How to Find the Offending Workload Capture File ( rec file ) when a Replay is Cancelled or Crashes
(Doc ID 1536695.1)
Last updated on JANUARY 12, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.1.0 and laterOracle Database Cloud Schema 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 Backup Service - Version N/A and later
Information in this document applies to any platform.
Purpose
In the case of a WRC crash or replay getting canceled by itself , you will usually need to find the workload capture file that has resulted in the the issue.
This document provides ways that may help to find the offending file more easily.
Please note that the steps below may only help in specific cases where the messages as shown below are present. It does not cover all the possibilities.
This document provides ways that may help to find the offending file more easily.
Please note that the steps below may only help in specific cases where the messages as shown below are present. It does not cover all the possibilities.
Troubleshooting Steps
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Purpose |
Troubleshooting Steps |
Enable Tracing on the WRC Clients |
Search Trace Files for: "DDE: Flood control is not active" |
Send threadfail piggyback |
Necessary Information for Analysis and Debugging |
References |