OracleMultitenant

Unresolved plug-in violations

Why a PDB opened in restricted mode: patch mismatches, parameter conflicts and missing options, with Oracle's suggested fix in the message.

12c+Run on CDB root

Not yet verified. How scripts are tested

ora-pdb-violations.sql

1CLEAR COLUMNS2SET LINESIZE 180 PAGESIZE 100 TRIMOUT ON TAB OFF3COLUMN name    HEADING "PDB" FORMAT A204COLUMN type    FORMAT A95COLUMN status  FORMAT A106COLUMN message FORMAT A100 WORD_WRAPPED7 8SELECT name, type, status, message9FROM pdb_plug_in_violations10WHERE status <> 'RESOLVED'11ORDER BY name, time;

Save it as ora-pdb-violations.sql and run it with SQL> @ora-pdb-violations.

Open in denrepo

Part of these runbooks

After patching

More Oracle scripts: Multitenant

Pluggable databases and their stateEvery PDB with its open mode, whether it's restricted, when it opened and its size. RESTRICTED = YES usually means a plug-in violation.
Tablespace usage across all PDBsThe tablespace report for every container at once, fullest first, so you don't have to switch into each PDB.
Open PDBs and keep them open after restartOpens every PDB, then saves the state so they reopen automatically when the CDB restarts. The first query shows what's currently saved.