The connection chip and container switcher

#9.1The connection chip

Centre-right of the top row. It shows a green dot when connected, the connection alias, and username@host. Clicking it opens a dropdown listing the current connection and a New connection… entry.

#9.2The container switcher (Oracle Multitenant)

If the connected database is a container database (CDB), a second chip appears showing the current container — CDB$ROOT in amber, or a PDB name. Clicking it discovers the pluggable databases visible to your session.

Each PDB row shows:

• A coloured dot — green = READ WRITE, amber = READ ONLY, grey = MOUNTED or in migration.
• The PDB name, a padlock if the PDB is in restricted-session mode, the open mode, and its size in MB.
• A tick against the container you are currently in.

Switching containers. Click any open PDB to move the whole IDE into it — every panel, the object browser, and the editor’s session re-target immediately. Because the tool is stateless, "switching" is simply re-pointing the connection at the PDB’s default service. CDB$ROOT is reachable again as long as DBCraft knows which service originally landed you there (it remembers this automatically when you first connect to the root).

Opening and closing PDBs. If you are connected as SYS, each non-current PDB row gains a small control: ▶ to open a mounted PDB, ⏹ to close an open one. Closing asks for confirmation. These controls appear only for SYS because Oracle requires a SYSDBA session for PDB lifecycle operations.

If no PDBs are listed. Oracle hides V$PDBS rows from common users by default. When DBCraft detects this it offers a one-click remedy in the dropdown: Enable PDB visibility — ALTER USER … SET CONTAINER_DATA=ALL. If your account cannot run that statement, the error is shown in place.