Oracle Database / Multitenant, Patching & Deployment
Read PDB plug-in violations before opening an imported PDB
A plugged or upgraded PDB can carry compatibility violations that need resolution before normal use. Inspect messages rather than forcing open state.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT name, cause, type, message, status, action FROM pdb_plug_in_violations WHERE name = 'APPPDB' ORDER BY time;Read the result
Messages distinguish warnings from errors and include suggested action. Resolved historical rows must not be mistaken for current unresolved blockers.
Resolve and verify
Compare unresolved issues with source and target release, options and patch state. Follow the documented corrective path and validate the PDB afterward.
Operational precautions
Do not delete violation records or ignore an incompatibility simply because a restricted open succeeds.