LATEST POSTS
-
Asymmetric dataguard with multitenant (part 3/3)
This series concludes with insights on managing PDB behavior in physical dataguard, emphasizing the importance of thoughtful strategies before executing an operation. It discusses proactive steps to address potential problems and works through examples of how to ensure dataguard synchronization without unnecessary downtime. The importance of detailed planning, adjustment of ENABLED_PDBS_ON_STANDBY parameters, and possible alternatives…
-
Asymmetric Dataguard with multitenant (Part 2)
This is the second part of the article series on asymmetric physical dataguard with multitenant. You can find the first part in this link. We begin this second part with a clear understanding of two concepts that we have learned when creating PDBs and performing UNPLUG/PLUG operations in a physical DG primary CDB: PDB operations…
-
Asymmetric Dataguard with multitenant (Part 1)
Following my previous post about PDB hot clones in a Data Guard environment, I received several questions from you about the different scenarios one might encounter in a physical Data Guard setup with PDBs. I believe the best way to address this is by delving into one of the most complex cases, which is the…
-
23c – Hybrid Read-Only PDBs
Several application’s maintenance tasks in an database require keeping users out of it. For instance, performing a parallel recompilation of objects after a code update. In these cases one of the most useful tools is to use dynamic services, which allow us to disconnect clients in a controlled, convenient and centralized manner. However, even today…
-
23c – Simplified PDB hot cloning in a Physical Dataguard environment
In one of the previous articles I superficially mentioned a relevant limitation in the combination of Multitenant + Dataguard in 19c: It simply cannot execute a synchronized hot cloning (primary cloning cascading to the standby). Today we are going to address that issue in detail, and we will discover an important improvement that we find…
-
23c – Floating PDBs – The Lab
The main objective of this laboratory is to understand the behavior of PDBs (Pluggable Databases) and services based on their configuration, particularly focusing on a “floating PDBs” configuration. We are interested in observing if the clusterware properly distributes the PDBs and their services during startup, verifying the behavior in case of a node failure in…
ORACLE AND ME NEWSLETTER
Sign up to receive an email whenever I publish a new post. Eventually several times a month.
