Explore >> Select a destination
|
You are here 
|
nenadnoveljic.com | ||
| | | | |
tanelpoder.com
|
|
| | | | | or rather thread stack as nowadays decent operating systems execute threads (or tasks as theyre called in Linux kernel). Anyway, stack trace gives you the ultimate truth on what your program is doing, exactly right now. There are couple of buts like stack corruptions and missing symbol information which may make the traces less useful for us, but for detailed hang & performance troubleshooting the stack traces are a goldmine. So, I present another case study how to diagnose a complete database hang when... | |
| | | | |
antognini.ch
|
|
| | | | | ||
| | | | |
jonathanlewis.wordpress.com
|
|
| | | | | Here's a little thing that Dan Morgan mentioned to me some time ago. It's a little routine from a package (owned by sys) that appeared in 11.2.0.3 that gives you some idea of the mess hidden behind a query that uses views. The procedure is called dbms_sql2.expand_sql_text and it takes two (CLOB) parameters: an IN | |
| | | | |
antognini.ch
|
|
| | | |||
