Oracle教程 2023-02-27

Oracle 视图 DBA_HIST_STREAMS_APPLY_SUM 官方解释，作用，如何使用详细说明

本站中文解释

MARY

Oracle视图DBA_HIST_STREAMS_APPLY_SUMMARY用于查看基于流复制技术的应用服务器执行情况的总体概览。该视图提供所有正在正确工作的应用服务器以及它们以前花费的总秒数和调用次数。它包含以下列：

• APPLY_NAME：应用程序的名称
• TARGET_NAME：应用计划的目标数据库中的名称
• TOTAL_SECONDS：历史期间总秒数
• TOTAL_CALLS：历史期间的总调用数
• CSTART_TIME：上一个有效运行的开始时间
• CSTOP_TIME：上一个有效运行的停止时间

可以使用以下SQL语句通过DBA_HIST_STREAMS_APPLY_SUMMARY视图来查看Oracle流复制应用服务器执行情况的总体概览：

SELECT
APPLY_NAME，TARGET_NAME，TOTAL_SECONDS，
TOTAL_CALLS，CSTART_TIME，CSTOP_TIME
FROM
DBA_HIST_STREAMS_APPLY_SUMMARY;

在每次定期分析检查中，可以使用此查询来确定回滚段/应用程序的运行情况，并了解有效运行的多长时间，及调用的次数。它还提供了一个重要的信息，即有效的启动和停止时间。

官方英文解释

DBA_HIST_STREAMS_APPLY_SUM displays information about each apply process and its activities.

This view contains a snapshot of V$STREAMS_APPLY_COORDINATOR, V$STREAMS_APPLY_READER, and V$STREAMS_APPLY_SERVER. This view is intended for use with Automatic Workload Repository (AWR).

Column	Datatype	NULL	Description
`SNAP_ID`	`NUMBER`	`NOT NULL`	Unique snapshot ID
`DBID`	`NUMBER`	`NOT NULL`	Database ID for the snapshot
`INSTANCE_NUMBER`	`NUMBER`	`NOT NULL`	Instance number for the snapshot
`APPLY_NAME`	`VARCHAR2(128)`	`NOT NULL`	Name of the apply process
`STARTUP_TIME`	`DATE`	`NOT NULL`	Time that the apply process was last started
`READER_TOTAL_MESSAGES_DEQUEUED`	`NUMBER`		Total number of messages dequeued since the apply process was last started
`READER_LAG`	`NUMBER`		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.
`COORD_TOTAL_RECEIVED`	`NUMBER`		Total number of transactions received by the coordinator process since the apply process was last started
`COORD_TOTAL_APPLIED`	`NUMBER`		Total number of transactions applied by the apply process since the apply process was last started
`COORD_TOTAL_ROLLBACKS`	`NUMBER`		Number of transactions which were rolled back due to unexpected contention
`COORD_TOTAL_WAIT_DEPS`	`NUMBER`		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
`COORD_TOTAL_WAIT_CMTS`	`NUMBER`		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
`COORD_LWM_LAG`	`NUMBER`		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.
`SERVER_TOTAL_MESSAGES_APPLIED`	`NUMBER`		Total number of messages applied by all the apply servers since the apply process was last started
`SERVER_ELAPSED_DEQUEUE_TIME`	`NUMBER`		Time elapsed (in hundredths of a second) dequeuing messages by all the apply servers since the apply process was last started
`SERVER_ELAPSED_APPLY_TIME`	`NUMBER`		Time elapsed (in hundredths of a second) applying messages by all the apply servers since the apply process was last started
`CON_DBID`	`NUMBER`		The database ID of the PDB for the sampled session
`CON_ID`	`NUMBER`		The ID of the container that `CON_DBID` identifies. Possible values include: `0`: This value is used for rows containing data that pertain to the entire CDB. This value is also used for rows in non-CDBs. `1`: This value is used for rows containing data that pertain to only the root n: Where n is the applicable container ID for the rows containing data

本站中文解释

官方英文解释

相关推荐