Ever wondered how exactly Oracle scans child cursors? Going down the rabbit hole 👇 t.ly/5fYsi

A short note on how to identify restricted and undocumented oradebug commands. t.ly/QyOFx

The greatest DBA tool of all time is gdb - change my mind.

A little script and some background information on how to extract v$ definitions directly from the oracle binary. t.ly/NT6L7

Avelio is live! 🚀 We are your Swiss partner for Oracle on‑premises database operations. Our mission: Optimised. Automated. Always Available. From proactive monitoring to 24/7 SLA‑backed support. Your business deserves reliability. Find out more: avelio.ch #Oracle #DatabaseManagement

A closer look at how Oracle 26ai determines and caps the maximum granule size t.ly/MEKOU

1/2 Interesting and undocumented changes in SGA management in Oracle 26ai: - Up to 31 subpools in the shared pool (max seven in 19c defined by _kghdsidx_count) - Subpools are split into thee durations (there were only two in 19c)

Pipelined or parallel? In Adaptive Scalable mode LGWR can assign redo writes to worker processes in different ways. More details in the post below 👇 t.ly/HJi5d

When does lgwr transition from single to scalable mode? t.ly/Ohe7a

Everybody should get rid of tnsnames.ora and use Easy Connect instead. Change my mind.

Just discovered this new blog series by @ludovico.bsky.social explaining Data Guard enhancements in 26ai - must read👇 www.ludovicocaldara.net/dba/dg-26ai-...

I felt like taking a closer look at this new datapatch feature and ended up making some interesting discoveries 🙂 t.ly/Tufob

Woot! By a happy twist of fate, a ticket for the 39th Chaos Communication Congress came may way ... 😀 See you in Hamburg! @ccc.de Thanks @krischan.bsky.social!

#POUG2026 dress code 😜 www.galaxus.ch/en/page/woul... @pougorg.bsky.social

1/11 Everything changes... turns out the age-old rule that lgwr writes out the log buffer when it's 1/3 full no longer applies in recent Oracle versions. Observations below from 19.26 (with RAC on Exadata). 👇

Week end fun: snooping inter-process messaging (ksbasend) in Oracle with bpftrace. 🤓 t.ly/_yDy7

This, so much! 👇

When you plan to geek out over some oracle internals, but end up ftrace’ing bpf the entire week end to chase a funny bug that only occurs on exadata with capacity on demand ...

There's a problem on the oracle-l listserver at present about an insert taking far too much time (and CPU). It's a known issue and there are 47 statistics in v$sysstat (19.11) with names like 'ASSM%' to help diagnose it. How many do you think are described in the database reference manual? None.

Yet another adaptive lgwr optimization: on Exadata X10+, pipelined log writes may defer redo writes until a suitably sized write batch has accumulated in the log buffer. The deferral can involve spinning in a tight loop up to 25 times (maximum hard-coded in kcrfw_defer_write).

Nested loops, baby 😜

In den nächsten Tagen veröffentlichen wir nicht nur die Agenda, sondern am Tag nach dem SOUG Day planen wir noch ein Special für Euch! Schaut rein und meldet Euch an unter soug.ch.

So glad that all new features are documented so well... NOT 😜 Manually enabling and disabling adaptive lgwr evaluation trace for pipelined / overlapped redo writes:

POUG journey started… not even at the airport and lufthansa’s delay notification leaves no hope of making the connecting flight in MUC 🙈

So 23ai replaces ksesecl0(func, loc, err) with kseseclv(err, func, loc, ...) ... Why is it always just a few days before POUG that this kind of low-level discoveries surface? 🙄

A new tool in 0x.tools family: xtop - Top for Wall-Clock Time. It uses eBPF/xcapture v3 and gives you "x-ray vision" into Linux system activity. It will be available on next Tuesday 19 Aug at 1pm EDT when I also run a live demo webinar! tanelpoder.com/posts/xtop-t...

"Slide n of 142".. this is getting out of control... 🙈

Today's discovery (19.26): Oracle derives different log parallelism defaults, depending on platform. Max number of public redo strands is: Exadata: CPU_COUNT <= 256: 16 CPU_COUNT> 256: CPU_COUNT/16 Non-Exadata: CPU_COUNT <= 32: 2 CPU_COUNT > 32: CPU_COUNT/16 Max limit: 256

Oh my, looks like the "ms" in "kso_sched_delay_avg_ms" actually means "microseconds" ... 🤷‍♂️

1/6 The "redo synch time overhead" in Oracle is the difference between a FG's log file sync (LFS) wait end time and LGWR's redo write completion time. LGWR and LG workers track the redo write completion times in the "write info array" in the SGA.

lgwr: You have the control gdb: I have the control

Over the past few weeks, my understanding of undocumented LGWR mechanics has improved quite a bit, and I'm now tempted to write a talk titled "LGWR beyond the docs - what Oracle didn't write to disk" 😉

1/4 In Adaptive Scalable mode, lgwr can dynamically assign multiple lg workers to process a redo write in parallel when these conditions are met: - redo write size > KSFD_MAXIO (usually 1 MB) - _max_log_write_parallelism > 1 - active public redo strands > 1

The trace below shows lg00 submitting a log write at T4 (lwn scn 0x70f14b55773) while lg04's earlier write submitted at T2 (lwn 0x70f14b55768) is still in flight, suggesting Pipelined Log Writes. But the trace is from an X8, not X10, where the feature is documented ...🤔 (I/Os throttled for testing)

1/7 On Exadata with pmemlog, the Fast Log File Sync dynamically tunes the log file sync sleep duration to balance responsiveness vs cpu ovherhead (spinning after wakeup). Oracle tracks three wait variants via different session stat counters: 1. Sleep 2. Spin 3. Backoff Sleeps

If you've ever felt the need to manually control adaptive lgwr features, this gdb script's got you covered: t.ly/lJIW1 😎 It lets you enable and disable adaptive scalable lgwr, fast log file sync, and log parallelism. Highly experimental, of course! Example 👇

Geeky Sunday mission accomplished… 💥✌️😎 The Fast Sync sleep duration used during log file sync waits is an adaptive moving average calculated every 3 sec by ckpt. For the curious, more details in this python script: tinyurl.com/mrycy7zh More explanations will follow some other time.

Week end plan: figure out how Fast Sync calculates the adaptive sleep duration used during log file sync waits. Answer is in the numbers below ... 🤔

Life before dynamic tracing: sleep. Life after: desperately trying not to lose your mind while chasing one more elusive oracle code path … 🐇🕳️

Haven't used good old perf for a while and forgot how cool it actually is. Wondering what process and code paths on your system modify a memory address? perf's got you covered: perf record -a -g -e mem:<addr>:w

Tired: Trust the abstraction Wired: Trace the abstraction