DBA_WORKLOAD_REPLAY_DIVERGENCE
displays information about data/error divergence for a user call that has been replayed.
Column | Datatype | NULL | Description |
---|---|---|---|
|
|
|
ID (key) for the workload replay |
|
|
Time that the divergence occurred |
|
|
|
|
Reserved for future use |
|
|
Indicates whether the data divergence is from the number of rows fetched by |
|
|
|
Indicates whether the divergence is from the number of rows affected by |
|
|
|
Indicates whether the divergence is from errors seen during capture or replay ( |
|
|
|
Indicates whether the divergence is from sessions that failed during replay ( |
|
|
|
Indicates whether the SQL call contains masked bind data (Y) or not (N). If data masking technology is used at the replay database, the workload capture files need to be masked. Otherwise, SQL statements generated from capture files that contain sensitive bind data will not match the database. When the replay client sends masked bind data to the server, it turns on the |
|
|
|
Number of rows fetched for |
|
|
|
Actual number of rows fetched for |
|
|
|
Error number that was seen during capture ( |
|
|
|
Text of the error message whose number appears in the |
|
|
|
Actual error number seen during replay ( |
|
|
|
Text of the error message whose number appears in the |
|
|
|
|
Stream ID of the session that reported the divergence |
|
|
|
Call counter of the user call that reported the divergence |
|
|
Internal ID of the capture file whose replay produced the divergence |
|
|
|
SQL ID of the SQL that reported the divergence |
|
|
|
|
Session ID of the session that reported the divergence |
|
|
|
Captured session serial number of the session that reported the divergence |
|
|
Service name of the session that reported the divergence |
|
|
|
Module name of the session that reported the divergence |
|
|
|
Action name of the session that reported the divergence |