SELECT NAME,CAUSE,TYPE,MESSAGE,STATUS FROM PDB_PLUG_IN_VIOLATIONS WHERE NAME='PDB$SEED'
NAME | CAUSE | TYPE | MESSAGE | STATUS |
---|---|---|---|---|
PDB$SEED | SQL Patch | ERROR | Interim patch 31424070/24854845 (APPSST19C XTTS PDB - TABLE IMPORT/CREATION FAILED WITH ORA-39083 ORA-14334): Installed in the CDB but not in the PDB | RESOLVED |
PDB$SEED | SQL Patch | ERROR | Interim patch 34086870/24803071 (OJVM RELEASE UPDATE: 19.16.0.0.220719 (34086870)): Not installed in the CDB but installed in the PDB | RESOLVED |
PDB$SEED | SQL Patch | ERROR | '19.16.0.0.0 Release_Update 2207030222' is installed in the CDB but no release updates are installed in the PDB | RESOLVED |
PDB$SEED | SQL patch error | ERROR | Interim patch 34086870/24803071 (OJVM RELEASE UPDATE: 19.16.0.0.220719 (34086870)): ROLLBACK with status INITIALIZE in the CDB. | RESOLVED |
The resolved messages can be easily removed with the procedure DBMS_PDB.CLEAR_PLUGIN_VIOLATIONS:
SYS@CDB$ROOT SQL> exec DBMS_PDB.CLEAR_PLUGIN_VIOLATIONS( pdb_name => 'PDB$SEED');
Useful resources:
Note that there is an Unpublished Bug 16192980 : NO SIMPLE WAY TO CLEAN ROWS FROM PDB_PLUG_IN_VIOLATIONS AFTER DBMS_PDB CALL that prevents you from discarding no-impact warnings.
According to Oracle there should be a fix for this in version 19.10, but I still strugle to remove messages like
Database option DV mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0.which can be ignored. Read more about Database option mismatch errors in Doc ID 2020172.1