USE_SID_AS_SERVICE_listener_name

Unable To Access EM Express For Non-CDB

Transport Database Over Network

Transportable Database

SQL Management Base Stores Plan Rows too

Solution To Performance Issue With In-database Archiving

Plug in 12c Non-CDB As PDB

Performance Issue With In-database Archiving

Enhancements To Partition Exchange Load

PDB cannot share CDB’s temporary tablespace

Optimizer_dynamic_sampling = 11

Improve Backup Performance Using In-database Archiving

In-database Archiving

Does PDB have an SPfile?

Display CDB/PDB Name In SQL Prompt

Display CDB/PDB Name In SQL Prompt

DDL Log Does Not Identify The Source PDB

Connecting To PDB’s With Same Name

Connecting to CDB/PDB – Set Container vs Connect

Clone An Existing PDB as Non-Sys User

Access Objects Of A Common User Non-existent In Root

In a multitenant environment, a common user is a database user whose identity and password are known in the root and in every existing and future pluggable database (PDB). Common users can connect to the root and perform administrative tasks specific to the root or PDBs. There are two types of common users :

• All Oracle-supplied administrative user accounts, such as SYS and SYSTEM

•  User created common users- Their names  must start with C## or c##.

When a PDB having a user created common user is plugged into another CDB and the target CDB does not have  a common user with the same name, the common user in a newly plugged in PDB becomes a locked account.
To access such common user’s objects, you can do one of the following:

• Leave the user account locked and use the objects of its schema.
• Create a common user with the same name as the locked account