SMON Consumes High CPU With Excessive Redo Log Generation
Last updated on JULY 20, 2017
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 to 10.2.0.3 [Release 9.2 to 10.2]
Information in this document applies to any platform.
***Checked for relevance on 21-Jul-2017***
After dropping some schema and deleting some objects, SMON process is consuming a high amount of CPU.
Also a high redo-log generation rate and increase in UNDO tablespace size may also be observed.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms