{"id":15104,"date":"2026-01-13T16:30:15","date_gmt":"2026-01-13T19:30:15","guid":{"rendered":"https:\/\/www.dbarj.com.br\/?p=15104"},"modified":"2026-01-14T17:03:29","modified_gmt":"2026-01-14T20:03:29","slug":"ora-65047-object-is-invalid-or-was-compiled-with-errors-in-the-root","status":"publish","type":"post","link":"https:\/\/www.dbarj.com.br\/en\/2026\/01\/ora-65047-object-is-invalid-or-was-compiled-with-errors-in-the-root\/","title":{"rendered":"ORA-65047: Object is invalid or was compiled with errors in the root."},"content":{"rendered":"

If you have unplugged your PDB from 19c<\/strong> and plugged it back on 23ai\/26ai<\/strong>, and open it, this will automatically trigger the Replay Upgrade. This method of upgrading a database is basically “replaying” all the captured changes that would bring a database from 19c to 23ai\/26ai release.<\/p>\n

However, sometimes objects are changed in the database, and you may end up with an error like this:<\/p>\n

SQL> create pluggable database PDB01 using '\/u01\/app\/oradata\/PDB01.xml' file_name_convert=('\/cdb1\/pdb01\/','\/cdb2\/pdb01\/');\r\n\r\nPluggable database created.\r\n\r\nSQL> alter pluggable database PDB01 open;\r\nalter pluggable database PDB01 open\r\n*\r\nERROR at line 1:\r\nORA-60510: encountered error  ORA-65047  during Replay Upgrade\r\nORA-65047: Object SYS.CDB_SYNC_CAPTURE_TABLES is invalid or was compiled with\r\nerrors in the root.\r\nHelp: https:\/\/docs.oracle.com\/error-help\/db\/ora-60510\/<\/pre>\n
In this example, I was upgrading from 19.29.0 to 23.26.0.<\/p>\n
The upgrade to 23ai\/26ai is hitting ORA-65047 with actions on top of %_SYNC_CAPTURE_TABLES views, which is an object that no longer exists because it was dropped by previous 23 RUs.<\/span><\/p>\n
Checking the error:<\/p>\n
SQL> alter session set container=PDB01;\r\n\r\nSession altered.\r\n\r\nSQL> select statement_id, statement from dba_replay_upgrade_errors where errormsg like '%ORA-65047%SYS.CDB_SYNC_CAPTURE_TABLES%';\r\n\r\nSTATEMENT_ID STATEMENT\r\n____________ ______________________________________________________________\r\n       57228 grant select on CDB_SYNC_CAPTURE_TABLES to select_catalog_role<\/pre>\n
The Replay Upgrade process loads the statements from a table called pdb_sync$<\/strong>, in CDB$ROOT. Unfortunately, it is only populated when you first create the database and is not refreshed after you apply an RUs. This is a design problem that is being corrected in the future. In my case, this database was created at 23.5 and later patched to 23.26.0, but the contents of pdb_sync$<\/strong> are not refreshed to reflect objects that were removed.<\/p>\n
To solve this problem, you can either:<\/p>\n
    \n
  1. Use the AutoUpgrade<\/strong> tool to upgrade your PDB instead, which I recommend, or<\/li>\n
  2. Fix the pdb_sync$<\/strong> reloading it with the right data, or<\/li>\n
  3. Create a new empty and dummy CDB using dbca and plug\/upgrade to this CDB instead.<\/li>\n<\/ol>\n
    Please note you will have to start from the beginning. So always keep a backup of your unplugged PDB before trying those methods.<\/p>\n
    1 – Using AutoUpgrade<\/h3>\n
    In this post I show how to run the final upgrade processes using AutoUpgrade: https:\/\/www.dbarj.com.br\/en\/2026\/01\/upgrade-from-oracle-19c-to-26ai-between-two-different<\/a><\/p>\n
    2 – Reloading pdb_sync$<\/h3>\n
    To reload the pdb_sync$<\/strong> table with the new and updated data, you have to call @?\/rdbms\/admin\/catcaptabupg.sql<\/strong> once connected to the CDB$ROOT:<\/p>\n
    $ sqlplus \/ as sysdba\r\n\r\nSQL*Plus: Release 23.26.0.0.0 - for Oracle Cloud and Engineered Systems on Wed Jan 14 19:29:06 2026\r\nVersion 23.26.0.0.0\r\n\r\nCopyright (c) 1982, 2025, Oracle.  All rights reserved.\r\n\r\nConnected to:\r\nOracle AI Database 26ai Enterprise Edition Release 23.26.0.0.0 - for Oracle Cloud and Engineered Systems\r\nVersion 23.26.0.0.0\r\n\r\nSQL> @?\/rdbms\/admin\/catcaptabupg.sql\r\n\r\nSession altered.\r\n\r\nno rows selected\r\n\r\nold   4:   vsns CONSTANT vsns_t := vsns_t &vsns;\r\nnew   4:   vsns CONSTANT vsns_t := vsns_t ('19200');\r\n\r\nPL\/SQL procedure successfully completed.\r\n\r\nSession altered.\r\n\r\nTable created.\r\n\r\n3 rows deleted.\r\n\r\n0 rows deleted.\r\n\r\n504 rows deleted.\r\n\r\n0 rows deleted.\r\n\r\n85192 rows deleted.\r\n\r\n0 rows deleted.\r\n\r\n0 rows deleted.\r\n\r\n0 rows deleted.\r\n\r\n1 row deleted.\r\n\r\nCommit complete.\r\n\r\nTable dropped.\r\n\r\nSystem altered.\r\n\r\nSystem altered.\r\n\r\nProcedure created.\r\n\r\nold   3:   vsns CONSTANT vsns_t := vsns_t &1;\r\nnew   3:   vsns CONSTANT vsns_t := vsns_t ('19200');\r\n19200: COMPLETED\r\n\r\nPL\/SQL procedure successfully completed.\r\n\r\nProcedure dropped.\r\n\r\n    APPID# APP_NAME\r\n---------- --------------------------------\r\n4294967291 APP$CDB$CATALOG\r\n\r\nno rows selected\r\n\r\nSystem altered.\r\n\r\nSystem altered.\r\n\r\nSession altered.\r\n\r\nold   3:   vsns CONSTANT vsns_t := vsns_t &vsns;\r\nnew   3:   vsns CONSTANT vsns_t := vsns_t ('19200');\r\n\r\nPL\/SQL procedure successfully completed.\r\n\r\nPL\/SQL procedure successfully completed.\r\n\r\nSession altered.\r\n\r\nSQL><\/pre>\n
    After the table is reloaded, try again to plug\/upgrade the PDB:<\/p>\n
    SQL> create pluggable database PDB01 using '\/u01\/app\/oradata\/PDB01.xml' file_name_convert=('\/cdb1\/pdb01\/','\/cdb2\/pdb01\/');\r\n\r\nPluggable database created.\r\n\r\nSQL> alter pluggable database PDB01 open;\r\n\r\nWarning: PDB altered with errors.\r\n\r\n    CON_ID CON_NAME                       OPEN MODE  RESTRICTED\r\n---------- ------------------------------ ---------- ----------\r\n         2 PDB$SEED                       READ ONLY  NO\r\n         4 PDB01                          READ WRITE YES<\/pre>\n
    Notice that PDB is open but in restricted mode.<\/p>\n
    We need to finish the process by calling datapatch:<\/p>\n
    $ $ORACLE_HOME\/OPatch\/datapatch\r\nSQL Patching tool version 23.26.0.0.0 Lim on Wed Jan 14 14:46:51 2026\r\nCopyright (c) 2012, 2025, Oracle.  All rights reserved.\r\n\r\nLog file for this invocation: \/u01\/app\/oracle\/product\/database\/dbhome_1\/cfgtoollogs\/sqlpatch\/sqlpatch_sid_orcl_ts_2026_01_14_14_46_51_pid_959636\/sqlpatch_invocation.log\r\n\r\nConnecting to database...OK\r\nGathering database info...done\r\n\r\nNote:  Datapatch will only apply or rollback SQL fixes for PDBs\r\n       that are in an open state, no patches will be applied to closed PDBs.\r\n       Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation\r\n       (Doc ID 1585822.1)\r\n\r\nBootstrapping registry and package to current versions...done\r\nDetermining current state...done\r\n\r\nCurrent state of interim SQL patches:\r\n  No interim patches found\r\n\r\nCurrent state of release update SQL patches:\r\n  Binary registry:\r\n    23.26.0.0.0 Release_Update 250927052030: Installed\r\n  PDB CDB$ROOT:\r\n    Applied 23.26.0.0.0 Release_Update 250927052030 successfully on 14-JAN-26 02.13.41.925667 PM\r\n  PDB PDB$SEED:\r\n    Applied 23.26.0.0.0 Release_Update 250927052030 successfully on 14-JAN-26 02.13.42.033770 PM\r\n  PDB PDB01:\r\n    Applied 23.26.0.0.0 Release_Update 250927052030 successfully\r\n\r\nAdding patches to installation queue and performing prereq checks...done\r\nInstallation queue:\r\n  For the following PDBs: CDB$ROOT PDB$SEED\r\n    No interim patches need to be rolled back\r\n    No release update patches need to be installed\r\n    No interim patches need to be applied\r\n  For the following PDBs: PDB01\r\n    No interim patches need to be rolled back\r\n    No release update patches need to be installed\r\n    No interim patches need to be applied\r\n\r\nBypass install queue:\r\n  For the following PDBs: PDB01\r\n    No interim rollbacks will bypass install\r\n    Patch 38404116 (Database Release Update : 23.26.0.0.0 (38404116) Gold Image): will bypass install\r\n      Apply from 23.26.0.0.0 Release_Update 250927052030 to 23.26.0.0.0 Release_Update 250927052030\r\n    No interim applys will bypass install\r\n\r\n\r\nInstallation queue after removing bypass entries...\r\nInstallation queue:\r\n  For the following PDBs: CDB$ROOT PDB$SEED\r\n    No interim patches need to be rolled back\r\n    No release update patches need to be installed\r\n    No interim patches need to be applied\r\n  For the following PDBs: PDB01\r\n    No interim patches need to be rolled back\r\n    No release update patches need to be installed\r\n    No interim patches need to be applied\r\n\r\n\r\nProcessing bypass install queue:\r\n  Patch 38404116 apply (pdb PDB01): SUCCESS (bypass_install)\r\n\r\nSQL Patching tool complete on Wed Jan 14 14:47:01 2026<\/pre>\n
    Finally, let’s reopen the PDB:<\/p>\n
    SQL> alter pluggable database PDB01 close;\r\n\r\nPluggable database altered.\r\n\r\nSQL> alter pluggable database PDB01 open;\r\n\r\nPluggable database altered.\r\n\r\nSQL> show pdbs\r\n\r\n    CON_ID CON_NAME                       OPEN MODE  RESTRICTED\r\n---------- ------------------------------ ---------- ----------\r\n         2 PDB$SEED                       READ ONLY  NO\r\n         4 PDB01                          READ WRITE NO<\/pre>\n
    The last step would be to:<\/p>\n
    3 – Using the dummy CDB<\/h3>\n
    First, I will create a new dummy CDB in 23.26.0 with dbca:<\/p>\n
    $ dbca -silent -createDatabase \\\r\n-gdbName orcl \\\r\n-templateName General_Purpose.dbc \\\r\n-characterSet AL32UTF8 \\\r\n-createAsContainerDatabase true \\\r\n-numberOfPDBs 1 \\\r\n-pdbAdminPassword \"Rodrigo.123\" \\\r\n-pdbName PDB01 \\\r\n-useLocalUndoForPDBs true \\\r\n-databaseConfigType SINGLE \\\r\n-databaseType MULTIPURPOSE \\\r\n-datafileDestination \/u01\/app\/oradata \\\r\n-dvConfiguration false \\\r\n-emConfiguration NONE \\\r\n-enableArchive false \\\r\n-memoryMgmtType AUTO_SGA \\\r\n-totalMemory 4000 \\\r\n-nationalCharacterSet AL16UTF16 \\\r\n-olsConfiguration false \\\r\n-recoveryAreaDestination \/u01\/app\/fra \\\r\n-sampleSchema false \\\r\n-sid orcl \\\r\n-storageType FS \\\r\n-useOMF false \\\r\n-sysPassword \"Rodrigo.123\" \\\r\n-systemPassword \"Rodrigo.123\"<\/pre>\n
    After the CDB is created, connect to it and just try the same steps from the previous method:<\/p>\n