My Oracle Support Banner

Streams Capture Process Running Extremely Slowly With 'CPU Time' as the Top Wait Event (Doc ID 458214.1)

Last updated on MARCH 04, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 11.2.0.3 [Release 10.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product.  Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner. 

The Streams capture process is observed to be running extremely slowly in 10.1 and 10.2 Streams.  An AWR report reveals that the top wait event for the instance is 'CPU time'.  When investigating the SQL that is the biggest contributor to the CPU time, execution of a procedure called SYS.LOGMNR_GTLO3 is the top contributor to both CPU time and elapsed time.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.