Thanks to Rich for this one. I am not a fan of ORACLE_PDB_SID as it is highly error-prone. If you never heard about this environment variable, then stop reading here. You won’t need to learn about it. But in case you are aware of it, then please see what happens when you bring together ORACLE_PDB_SID and AutoUpgrade.

Photo by Taylor Brandon on Unsplash
ORACLE_PDB_SID?
A long while ago, I wrote two blog posts about Can you connext as SYSDBA without the password into a PDB directly? and Pitfalls: Connect to a PDB directly with ORACLE_PDB_SID. I tried to …
Continue reading...









I usually create my container databases for testing with the 
When I changed our Hands-On Lab to Oracle 18c,
This was an interesting question I received from Alain Fuhrer a couple of weeks ago: “Why can’t I drop a tablespace in a PDB whit a Guaranteed Restore Point being active?”. It’s important to note that the GRP is not active in the same but in another PDB.
Interesting case Roy came across a week ago with a customer in the US. The customer received a plugin violation because of different
Since Oracle Database 12.2.0.1 a Multitenant container database can host PDBs with different character sets. This was a huge restriction in Oracle Database 12.1., at least outside the US and Canada. Here in Germany alone you may find plenty of different database character sets, for instance WE8ISO8859P1, WE8ISO8859P9, WE8ISO8859P15, WE8MSWIN1252, maybe still some old WE8DEC – and of course the unicode ones UTF8 and AL32UTF8. But the question is: Can you select a PDB’s character set when you provision a new PDB?
I did blog several times about how to remove an unwanted component from a database. But yesterday I came across this interesting scenario worth a blog post.