After applying the binaries for RU 19.28 (Jul 25), we had datapatch failing with this error:
servername/oracle$./datapatch -verbose
....
Current state of release update SQL patches:
Binary registry:
19.28.0.0.0 Release_Update 250705030417: Installed
PDB CDB$ROOT:
Applied 19.27.0.0.0 Release_Update 250410082304 successfully on 16-JUN-25 11.52.26.776066
PDB PDBNAME1:
Applied 19.27.0.0.0 Release_Update 250410082304 successfully on 16-JUN-25 11.56.31.281534
PDB PDB$SEED:
Applied 19.27.0.0.0 Release_Update 250410082304 with errors on 16-JUN-25 11.59.21.779180
Adding patches to installation queue and performing prereq checks...done
Installation queue:
For the following PDBs: CDB$ROOT PDBNAME1
The following interim patches will be rolled back:
37499406 (OJVM RELEASE UPDATE: 19.27.0.0.250415 (37499406))
Patch 37960098 (Database Release Update : 19.28.0.0.250715 (37960098)):
Apply from 19.27.0.0.0 Release_Update 250410082304 to 19.28.0.0.0 Release_Update 250705030417
The following interim patches will be applied:
37847857 (OJVM RELEASE UPDATE: 19.28.0.0.250715 (37847857))
For the following PDBs: PDB$SEED
The following interim patches will be rolled back:
37499406 (OJVM RELEASE UPDATE: 19.27.0.0.250415 (37499406))
Patch 37642901 (Database Release Update : 19.27.0.0.250415 (37642901)):
Rollback from 19.27.0.0.0 Release_Update 250410082304 to 19.1.0.0.0 Feature Release
Patch 37960098 (Database Release Update : 19.28.0.0.250715 (37960098)):
Apply from 19.1.0.0.0 Feature Release to 19.28.0.0.0 Release_Update 250705030417
The following interim patches will be applied:
37847857 (OJVM RELEASE UPDATE: 19.28.0.0.250715 (37847857))
Unsupported named object type for bind parameter at /u01/app/oracle/product/19.0.0/dbhome_1/sqlpatch/sqlpatch.pm line 5339.
Please refer to MOS Note 1609718.1 and/or the invocation log
/u01/app/oracle/cfgtoollogs/sqlpatch/sqlpatch_25595_2025_09_24_13_20_18/sqlpatch_invocation.log
for information on how to resolve the above errors.
SQL Patching tool complete on Wed Sep 24 13:21:17 2025
servername/oracle$There was nothing very clear on PDB_PLUG_IN_VIOLATIONS, but checking DB alert log, we could see this error on PDB$SEED:
PDB$SEED(2):WARNING: The following temporary tablespaces in container(PDB$SEED)
PDB$SEED(2): contain no files.
PDB$SEED(2): This condition can occur when a backup controlfile has
PDB$SEED(2): been restored. It may be necessary to add files to these
PDB$SEED(2): tablespaces. That can be done using the SQL statement:
PDB$SEED(2):
PDB$SEED(2): ALTER TABLESPACE <tablespace_name> ADD TEMPFILE
PDB$SEED(2):
PDB$SEED(2): Alternatively, if these temporary tablespaces are no longer
PDB$SEED(2): needed, then they can be dropped.
PDB$SEED(2): Empty temporary tablespace: TEMP
After we added a temp file, datapatch ran without issues.
Comments