My today morning’s Advanced Oracle Troubleshooting presentation was quite a success. The 400 people room was fully pre-booked and over 300 people showed up. This is a pretty good result considering that a) my presentation was an 9 am one on the last day of conference and b) there was a big party last night :)
Thanks to everyone who attended!
I have uploaded the slides here: http://www.tanelpoder.com/files/Advanced_Oracle_Troubleshooting.pdf
PerfSheet (the Excel based automatic data visualization tool) is uploaded here: http://www.tanelpoder.com/files/PerfSheet.zip
The TPT scripts (scripts like snapper, latchprofx, ostackprof etc I demoed and a lot more) are uploaded here: http://www.tanelpoder.com/files/TPT_public.zip
Few links to my past blog entries about how to use Snapper, LatchProfX and os_explain:
- Advanced Oracle Troubleshooting Guide, part 8: LatchProfX
- Oracle Session Snapper v1.06 released
- Advanced Oracle Troubleshooting Guide, part 6: os_explain
I haven’t blogged about usage of OStackProf yet (as the tool’s very fresh), I will do so in coming week.
Feel free to send any further questions to tanel@tanelpoder.com
Also, if you liked my presentation, you will sure like my 2-day seminar on the same topic. I will go even deeper in there ;-)
Check out this page: http://blog.tanelpoder.com/seminar/. I’ve arranged my seminar in 18 cities already for 2008 and early 2009, if your city is not in the list, let me know and I’ll see what I can do :)
Thanks once more for everyone attending my OOW presentation and also my blog readers for continued support!
Thanks to you, Tanel. It was the best session I attended this OOW.
Comment by Rob van Wijk — September 26, 2008 @ 9:36 am
Thanks Rob!
I wish I had 2 (or 3) times more time to explain stuff there :)
Comment by tanelp — September 26, 2008 @ 3:33 pm
Tanel – I didn’t get to attend OOW (maybe one of these years!), but wanted to thank you for posting your slides. Thanks also for posting/blogging all of your very cool work here, I really appreciate it!
Jerry
Comment by Jerry — September 26, 2008 @ 9:48 pm
Hi Tanel
I attended your version of what I assume is the same presentation at the UKOUG (this one was on a Friday afternoon! )- defintely lots to further investigate/think about.
To me it seems that your whole approach depends on ‘identifying the problem session’. Do you have any further insights into how to do this in a long running batch job type (as opposed to a OLTP) environment?
Thanks
Austen
Comment by Austen Birchall — December 9, 2008 @ 6:43 pm
Your training session in China made me know that I can do my work more efficient and think things in a different way, Thanks for you did for inspiring me a lot!!!
Comment by Betty — December 23, 2008 @ 9:30 pm
wrong email address in my previous comments. gmail one is correct.
Again, Thanks a lot for your sharing…
Comment by Betty — December 23, 2008 @ 9:31 pm
@Austen
Yes, the right troubleshooting approach is identifying the session(s) of the problem end user, as the end user can experience a database problem only through a session. Thus the session level instrumentation is the perfect starting point. Otherwise you might end up troubleshooting the wrong thing…
Its usually easy to identify regular long running batch job sessions as usually these sessions are alive for long time and serve only that batch job.
The hardest part is identifying single problem user requests coming through a connection pool (black box) where there *is no instrumentation* by application itself. Since 10g Oracle has the infrastructure though for gathering end user stats, the application needs to bundle end users CLIENT_IDENTIFIER with any command it sends to database and then with help of DBMS_MONITOR+V$CLIENT_STATS or DBMS_MONITOR.CLIENT_ID_TRACE_ENABLE one can measure/trace only specific end user, no matter through which session/connection it uses.
@Betty
Thanks!!
Comment by Tanel Poder — December 24, 2008 @ 1:44 pm