parallel recovery push change
A stuck nanosleep call impairs a parallel recovery process. The affected parallel recovery process spends 100% of its time in the undocumented parallel recovery push change wait event. Continue Reading
DTrace
A stuck nanosleep call impairs a parallel recovery process. The affected parallel recovery process spends 100% of its time in the undocumented parallel recovery push change wait event. Continue Reading
MTTR advisor data gathering can cause redo copy latch contention on servers with many CPUs. Checkpoint queue internals. An example of analyzing a compiled function in a proprietary code without disassembling it. Continue Reading
Tracing latches with OS tools, case study: redo copy contention caused by a logon storm Continue Reading
Tracing Library Cache Locks with DTrace Continue Reading
Logon storms may substantionally contribute to DB time which isn’t captured in active session history. Continue Reading
Internal processing of critical Java errors in the Oracle database Continue Reading
Oracle database internals – (redo) “log write elapsed time” instrumentation Continue Reading
IO Sort Cost Calculation: formulae and internals Continue Reading
A DTrace script for capturing the call stack when a line gets written into the trace file. It’s useful, for example, for finding out the functions participating in a particular query transformation. Continue Reading
A crashed process can leave a dead transaction behind. Generally, SMON is the one who’ll be rolling it back. Under certain circumstances, though, a server process might lend a helping hand. That’s exactly the scenario we’ll be focusing on. Continue Reading