oracle 等待的进程,Oracle 等待事件：ges generic event

在 Oracle 12c 之后，Resource Master 进程成为了主从进程架构，一系列从属进程以 RMV 命名开头，出现在数据库中。

在某些情况下，你可能在 AWR 中看到大量的 ges generic event 等待事件。ges generic event 顾名思义，就是关于 GES 的一个普通事件，属于空闲等待，无事可做的 IDLE 状态。

在 ASH 报告中，可以看到类似如下的输出：

这个事件没有对数据库的直接影响。以下是来自 12.2 版本的一个报告输出：

以下是 MOS 上的简要说明：

CAUSE

A new idle wait metric collection was added in 12c for RMV processes. The gcs generic event wait was reused as the class for this idle wait.

SOLUTION

There is no actual problem.

The metric is showing the time the RMV processes spent idle. In other words, they were not waiting to perform any action; for example they were not waiting because of another blocking process, high CPU usage, etc. The RMV processes were simply not active.  The high wait counts due to "ges generic event" wait event for RMV* processes can be ignored when seen in an AWR.

An request was made to change the type of wait class so that this issue would be more accurately reported in the AWR (and not trigger EM alerts as well).  Patch 30794929 can be applied to make the change in how the metric is reported.   Refer toDoc ID 1091294.1 for instructions on how to find conflict free patches for your environment and request back ports if no conflict free versions are available.

REFERENCES

NOTE:30794929.8- Bug 30794929 - High Waits On 'ges generic event' Showing On AWR Or OEM