Single Tenant duplicates

I recently reported an issue regarding single tenant. In old-time non-cdb, the SID used to be unique on a server. If you connect to srv01:port:sid, then you know where you connect. Unfortunately, this is no longer true. If for instance you have two database sid’s S01 and S02 with a pluggable P01, and both run […]

sid and pluggable

I wrote about SID there. (CONNECT_DATA=(SID=DB01)) is undocumented since Oracle 11gR1 and breaks things with multi-tenant / single-tenant. You create a container CDB01 and a pluggable DB01, you can connect with sqlplus "scott/tiger@   (description=(address=     (host=srv01)(port=1521)(protocol=tcp))     (connect_data=(service_name=DB01.example.com)))" But one of your application has hardcoded SID=DB01 sqlplus "scott/tiger@   (description=(address=     (host=srv01)(port=1521)(protocol=tcp))     (connect_data=(sid=DB01)))" ORA-12514: TNS:listener does not currently know […]

Single-Tenant over bequeath connections

If you follow Oracle recommendation to use SingleTenant CDB instead of Non-CDB, then a lot of things will break. I won’t go into details, but basically, in this new architecture, you have one core container, called CDB$ROOT, which is the default container where you connect to if you connect locally sqlplus / as sysdba SQL> […]