5.36 DBA_HIST_REPORTS_TIMEBANDS
DBA_HIST_REPORTS_TIMEBANDS contains bands of time with a new row created every day corresponding to a band of time.
Each band of time represents a period of time, and has a row for every report captured automatically into Automatic Workload Repository (AWR) during that time. If the activity period of a report spans across two bands of time (for example. the activity started before midnight and ended after midnight), then the view contains two rows for that report, with one row for each band of time. The view is partitioned to provide fast access to all reports captured in a given time frame.
| Column | Datatype | NULL | Description |
|---|---|---|---|
|
|
|
|
The AWR snapshot id corresponding to the report |
|
|
|
|
Database ID of the current database for the report |
|
|
|
|
Instance number (for an Oracle RAC system) |
|
|
|
|
CDB ID of the captured report |
|
|
|
|
ID of the component (for example, SQL Monitor) whose report is captured |
|
|
|
|
Name of the component whose report is captured |
|
|
|
|
Starting time of the time band |
|
|
|
|
Length of time band in days (currently unused) |
|
|
|
|
ID of the captured report |
|
|
|
|
Time when the report was generated |
|
|
|
|
Time when the activity period started |
|
|
|
|
Time when the activity period ended |
|
|
|
|
Key1 associated with the captured report |
|
|
|
|
Key2 associated with the captured report |
|
|
|
|
Key3 associated with the captured report |
|
|
|
|
Key4 associated with the captured report |
|
|
|
|
ID of the session corresponding to the captured report (currently used only for SQL Monitor reports) |
|
|
|
|
Session serial number corresponding to the captured report (currently used only for SQL Monitor reports) |
|
|
|
|
The ID of the container that
|