Log Writer Consumes 100% CPU

Log Writer Consumes 100% CPU with the instance going for Hang and the system

WARNING: inbound connection timed out (ORA-3136)

Check the blocking session:

SELECT sid, blocking_session, username, blocking_session_status FROM v$session ORDER BY blocking_session;



Workaround: '_lgwr_async_io=false' to prevent lgwr from spinning

Note: The problem may manifest even after _lgwr_async_io = false has been set and instance bounced

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.