暂时无法在支持网站上提交享有定期维护的产品表单。 如果您需要我们立即提供帮助，请与技术支持部门联系。 对于由此给您带来的不便，我们深表歉意。
获得即时帮助
完成注册
登录
请求定价
联系销售人员
您已选择一个产品捆绑包。 您能否选择单个产品以便我们更好地满足您的请求。 *
技术支持工程师目前正忙，无法回应您的消息。 如果需要即时服务，请通过我们的服务请求表提交请求。
以下文章可根据您的描述解决您的问题。
Cluster wait events take place when the session waits for all types of cluster resources, such as Interconnect hardware, shared disks, and Oracle instances.
When SQL statements and other types of calls are made to Oracle, processing the calls requires spending a certain amount of CPU time. Whereas processing average calls requires a small amount of CPU time, a SQL statement involving a large amount of data or a runaway query can consume a much larger amount, thereby reducing the CPU time available for other processing.
CPU utilization is a key operating system statistic in the tuning process. Excessive CPU usage can result from an inadequately-sized system, untuned SQL statements, or inefficient application programs.
CPU wait events take place when the session is waiting in the system's run queue to be granted for CPU cycles. The length of these wait events (the amount of time spent) depends upon the number of concurrent processes and threads requesting CPU time.
This metric’s value should be inspected in conjunction with the value of the Run Queue Length.
Extensions to result sets that provide the mechanism for working with individual rows, or a small block of rows, in a table.
Because a cursor points to a currently selected set of records, they can be used by only one connection at a time. However, the compiled plan to which the cursor is linked can be used simultaneously by multiple connections.
您可以在附属支持站点上查找适用于戴尔*产品*的在线支持帮助。单击“继续”，转至适用于*产品*的正确支持内容和帮助。
The document was helpful.
选择评级
I easily found the information I needed.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
Quest Software门户不再支持IE 8、9和10，建议将您的浏览器升级到最新版本的Internet Explorer或Chrome。
要升级到IE 11，请单击此处
要升级到Chrome，请单击此处
如果继续使用IE 8、9和10，您将无法充分利用我们所有出色的自助服务功能。
