Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Finding the reasons for excessive logical IOs | Tanel Poder Consulting #21

Open
utterances-bot opened this issue May 21, 2021 · 1 comment

Comments

@utterances-bot
Copy link

Finding the reasons for excessive logical IOs | Tanel Poder Consulting

There’s another interesting thread going on in Oracle-L, about understanding logical IOs and drilling down into their reasons. Of course sometimes (or rather usually) the excessive logical IOs come from a bad execution plan (when a nested loop loops over lots of datablocks again and again or a wrong index is used for driving a query etc), but sometimes the excessive LIOs are caused by some internal issues, like space management etc.
A convenient tool I use for reporting logical IO reasons is (again) my Snapper! It has an option “b” for reporting Buffer get reasons or as I use below – option “a” shows All information Snapper can show.
There are couple of gotchas though which make this approach imperfe

https://tanelpoder.com/2009/11/19/finding-the-reasons-for-excessive-logical-ios/

Copy link

DAV1963 commented May 21, 2021

Hi,
I tried to run snapper on Active DataGuad host and got the message
declare * ERROR on line 1: ORA-16000: database or pluggable database is open for read-only access

Andre

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants