Why should you care?

Production outages and slow systems are diagnosed with pdb_dba knowledge — not guesswork.

See it live — copy this example

Run these statements in SQL Developer or SQL*Plus against your lab PDB. Prefer a practice user — not SYS — for application SQL.

SHOW CON_NAME
ALTER SESSION SET CONTAINER = ORCLPDB1;

SELECT name, open_mode FROM v$pdbs;

What happened?

• Multitenant Oracle has a CDB and PDBs.
• App work usually happens inside a PDB.

Practice next

1. Connect to your lab as a user with the needed privileges.
2. Run the read-only checks first.
3. Write the definition of this topic in your own words.
4. Change one literal in the example and re-run.
5. Write a second example from memory without looking.

Remember

You can explain PDB_DBA in plain English. You ran at least one related command or query. You know one real system where it matters.

PDB_DBA on a banking PDB

On-call DBA reviews pdb_dba during a health check before peak traffic.

Outcome: You know which view/command to open first.