Explore >> Select a destination
|
You are here 
|
tanelpoder.com | ||
| | | | |
littlekendra.com
|
|
| | | | | Kendra Little writes and draws comics about SQL Server, Data Platforms, and Database DevOps. | |
| | | | |
blog.tanelpoder.com
|
|
| | | | | In my last AOT post I published my LatchProf script which is able to sample detailed latchholder data from V$LATCHHOLDER. Latchprof allows you to drill down into your latching problems at session level (which V$LATCH, V$LATCH_PARENT and V$LATCH_CHILDREN can't do). It allows you to get valuable details about individual sessions who are holding a latch the most, therefore likely contributing to the latch contention problem the most. However after you have discovered the troublemaking session, then what next? One way forward is looking into V$SESSTAT counters using Snapper tool. Depending on what latch is the problematic one, you would look for different stats like various buffer get stats for cache buffers chains latches and parsing/executing stats when looking into library cache latches. However if those stats look "normal", is there any other way do drill down further? Yeah, there is and lets look into it! - Linux, Oracle, SQL performance tuning and troubleshooting - consulting & training. | |
| | | | |
blog.tanelpoder.com
|
|
| | | | | In recent past I've blogged few scripts which use specially crafted ordered nested loop for sampling contents of V$ and X$ views fast, with plain SQL. If you haven't read them yet, here are the links: WaitProf LatchProf LatchProfX I wrote the above scripts having special purposes in mind (e.g. profile session waits or latching activity). Now I introduce a simple but powerful sqlplus script for ad-hoc sampling of any V$ view. It's called.... (drumroll) .... sample.sql :) When you look into it, the script ... | |
| | | | |
boonaree.wordpress.com
|
|
| | | This is the excerpt for your very first post. | ||
