Dragons are cool. And as DBAs, we’re basically the mothers of dragons—we hold the power to say DRACARYS! and burn it all down. But let’s be honest: dragon fire is a bit outdated... kind of like traditional per-CDB Data Guard, right? One PDB misbehaves, and suddenly the entire CDB goes up in flames. Are we in the Red Wedding? Because that escalated really fast. And the worst part? The PDB that crashed was the one with all the Game of Thrones episodes. Thankfully, Oracle decided to stop writing George R. R. Martin’s disaster recovery scripts.
Before 21c, when one PDB crashed in a multitenant setup, you had no choice but to fail over the entire CDB. Total overkill. It was like declaring war on the whole realm because one lord forgot to pay his taxes.
Oracle 21c introduced Per-PDB Data Guard, and 23ai makes it even more powerful and practical. Now you can gracefully exile the rogue PDB while the rest of your realm keeps humming along like nothing ever happened
In this talk, we’ll dive into how DGPDB works, what’s new in Oracle 23ai, and why it’s a game changer for DBAs who are tired of being the Hand of the (CDB) King. Thrones references included—mass casualties not required.