Oracle 视图 DBA_HIST_APPLY_SUMMARY 官方解释，作用，如何使用详细说明
本站中文解释
Oracle中的视图DBA_HIST_APPLY_SUMMARY是一个用于查询保持状态和应用时间概要信息的视图。它由数据库层收集的数据统计组成。它主要提供实例保持时间，恢复点应用时间和恢复点日志应用时间。
只有选择了受支持的特定痕迹（如Automatic Workload Repository）的实例，才能获取DBA_HIST_APPLY_SUMMARY视图的详细信息。
使用此视图可以查询在每个恢复点时期的实例保持时间（INSTANCE_RECOVERY_ELAPSED_TIME），恢复点应用时间（RESTORE_POINT_ELAPSED_TIME）以及在特定事件的恢复点日志应用时间（LOG_POINT_ELAPSED_TIME）等信息，从而可以获取关于系统恢复状态和应用时间的重要信息。
例如，下面的SQL查询可以用于查询特定时段内活动恢复点（ACTIVE_RESTORE_POINT）的概要信息：
SELECT * FROM dba_hist_apply_summary where trunc(begin_time) between ‘&start_date’ and ‘&end_date’;
此外，DBA_HIST_APPLY_SUMMARY视图也可以用于查询特定事件（如SCN）的实例恢复状态和应用时间：
SELECT * FROM dba_hist_apply_summary where active_restore_point = ‘&restore_point_name’ and resetlogs_scn_number
官方英文解释
DBA_HIST_APPLY_SUMMARY displays historical statistics information about each apply process for Oracle GoldenGate, and Oracle XStream. This view is intended for use with Automatic Workload Repository (AWR).
| Column | Datatype | NULL | Description |
|---|---|---|---|
|
|
|
|
Unique snapshot ID |
|
|
|
|
Database ID for the snapshot |
|
|
|
|
Instance number for the snapshot |
|
|
|
|
Name of the apply process |
|
|
|
|
The time that the apply process was last started |
|
|
|
Total number of messages dequeued since the apply process was last started |
|
|
|
|
For captured messages, the delay (in seconds) between the creation of the last message and it being received by the apply process. For user enqueued messages, the delay between the message being enqueued in the local database and being received by the apply process. |
|
|
|
|
Total number of transactions received by the coordinator process since the apply process was last started |
|
|
|
|
Total number of transactions applied by the apply process since the apply process was last started |
|
|
|
|
Number of transactions which were rolled back due to unexpected contention |
|
|
|
|
Number of times since the apply process was last started that an apply server waited to apply a logical change record (LCR) in a transaction until another apply server applied a transaction because of a dependency between the transactions |
|
|
|
|
Number of times since the apply process was last started that an apply server waited to commit a transaction until another apply server committed a transaction to serialize commits |
|
|
|
|
For captured messages, the delay (in seconds) between the creation of the message corresponding to the low watermark and it being applied by the apply process. For user enqueued messages, the delay between the message being enqueued in the local database and being applied by the apply process. |
|
|
|
|
Total number of messages applied by all the apply servers since the apply process was last started |
|
|
|
|
Time elapsed (in hundredths of a second) dequeuing messages by all the apply servers since the apply process was last started |
|
|
|
|
Time elapsed (in hundredths of a second) applying messages by all the apply servers since the apply process was last started |
|
|
|
|
The database ID of the PDB |
|
|
|
|
The name of the replicat group created from GGSCI using GoldenGate |
|
|
|
|
Total number of complete transactions that the coordinator has not assigned to any apply servers |
|
|
|
|
Total number of LCRs retried by this server |
|
|
|
|
Total transactions retried by this server |
|
|
|
|
Number of transactions applied by the apply process that resulted in an apply error since the apply process was last started |
|
|
|
|
|
Session module. Valid values:
|
|
|
|
The ID of the container to which the data pertains. Possible values include:
|
