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... | |
| | | | |
jonathanlewis.wordpress.com
|
|
| | | | | In an earlier articleI described how dbms_xplan.display_cursor() could be used to query memory to find the execution plans (and row source statistics) of recently executed SQL. In 9i, you have to use your own SQL to get the equivalent results. If you do, you should avoid using the "traditional" hierarchical type of query that you... | |
| | | | |
jagjeet.wordpress.com
|
|
| | | | | Recently, I was engaged in Exadata POV for benchmarking for Ebiz R12 on Exa* boxes. We had quarter rack running 11.2.0 db with 2 node RAC Cluster (24 CPU) and all other components/Middle Teir including Form, Web, CM were configured on Exalogic Server. Objective was to achieve best possible scalability numbers on Exa* boxes for | |
| | | | |
nenadnoveljic.com
|
|
| | | Analysis of dataset properties leading to a bad performance problem with a simple fix. | ||
