I recently had to move a database from a 19.23 to a 19.26 dbhome on an ExaCC. This will include the database to be patched. The command dbaascli database move failed during the datapatch steps with following error:<\/p>\n\n\n\n
DBD::Oracle::st execute failed: ORA-01691: unable to extend lob segment SYS.SYS_LOB0000023009C00008$$ by 1024 in tablespace SYSTEM<\/code><\/pre>\n\n\n\nWith this blog I would like to share my troubleshooting with you and how I resolved the problem.<\/p>\n\n\n\n\n\n\n\n
Moving database to new dbhome<\/h3>\n\n\n\n
In order to move\/patch the database I used dbaascli database move command.<\/p>\n\n\n\n
\n[root@exacc-cl01n1 ~]# dbaascli database move --oracleHome \/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3 --dbname CDBTEST\nDBAAS CLI version 25.1.1.0.0\nExecuting command database move --oracleHome \/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3 --dbname CDBTEST\nJob id: 17f6fef5-2143-4bb7-8007-a27cf5232099\nSession log: \/var\/opt\/oracle\/log\/CDBTEST\/database\/move\/dbaastools_2025-05-05_02-47-51-PM_237874.log\nLoading PILOT...\nSession ID of the current execution is: 15920\nLog file location: \/var\/opt\/oracle\/log\/CDBTEST\/database\/move\/pilot_2025-05-05_02-47-55-PM_238225\n-----------------\nRunning initialization job\nCompleted initialization job\n-----------------\nRunning validate_user_input job\nCompleted validate_user_input job\n-----------------\nRunning validate_database job\n[WARNING] [DBAAS-70643] Following pluggable databases '{CDBTEST=[PDB_001T]}' do not have services configured.\n ACTION: Make sure to configure the services of pluggable databases so that pluggable databases are started after the database bounce.\nCompleted validate_database job\n-----------------\nRunning validate_creg_file_existence job\nCompleted validate_creg_file_existence job\n-----------------\nRunning validate_source_home job\nCompleted validate_source_home job\n-----------------\nRunning validate_major_version job\nCompleted validate_major_version job\n-----------------\nRunning validate_oracle_home_type job\nCompleted validate_oracle_home_type job\n-----------------\nRunning check_target_source_home_not_same job\nCompleted check_target_source_home_not_same job\n-----------------\nRunning validate_home_existence job\nCompleted validate_home_existence job\n-----------------\nRunning validate_home_consistency job\nCompleted validate_home_consistency job\n-----------------\nRunning validate_home_options job\nCompleted validate_home_options job\n-----------------\nRunning validate_disk_space job\nCompleted validate_disk_space job\n-----------------\nAcquiring write lock: cdbtest\nAcquiring read lock: _u02_app_oracle_product_19.0.0.0_dbhome_1\nAcquiring read lock: _u02_app_oracle_product_19.0.0.0_dbhome_3\nRunning pre_patch_lock_manager job\nCompleted pre_patch_lock_manager job\n-----------------\nRunning enable_wallet_root job\nCompleted enable_wallet_root job\n-----------------\nRunning copy_config_files job\nCompleted copy_config_files job\n-----------------\nRunning stop_database_instance-exacc-cl01n1 job\nCompleted stop_database_instance-exacc-cl01n1 job\n-----------------\nRunning update_database_resource-exacc-cl01n1 job\nCompleted update_database_resource-exacc-cl01n1 job\n-----------------\nRunning start_database_instance-exacc-cl01n1 job\nCompleted start_database_instance-exacc-cl01n1 job\n-----------------\nRunning exacs_post_patch_node_updation job\nCompleted exacs_post_patch_node_updation job\n-----------------\nRunning update_dba_directories job\nCompleted update_dba_directories job\n-----------------\nRunning datapatch_and_recompile_invalid_objects job\nDatapatch execution on database 'CDBTEST' is in progress\nExecution of datapatch_and_recompile_invalid_objects failed\n[FATAL] [DBAAS-60022] Command '\/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3\/OPatch\/datapatch -verbose' has failed on nodes [exacc-cl01n1].\n*MORE DETAILS*\nResult of node:exacc-cl01n1\n[Interim patch 28318139 (ORA-31003 ERROR WHEN IMPORTING FULL DATABASE IN PARALLEL):, Binary registry: Not installed, PDB PDB_001T: Rolled back successfully on 06-MAR-22 10.57.36.095921 AM, PDB CDB$ROOT: Not installed, PDB PDB$SEED: Not installed, Interim patch 28555193 (DBMS_METADATA.GET_DDL CAPTURE INCORRECT STORAGE OPTIONS OF THE XML COLUMN ON GTT):, Binary registry: Not installed, PDB PDB_001T: Rolled back successfully on 06-MAR-22 10.57.37.111786 AM, PDB CDB$ROOT: Not installed, PDB PDB$SEED: Not installed, Interim patch 30944402 (SELECT FROM MASTER TABLE RUNS SLOW DURING TABLE_DATA EXPORT WHEN THERE ARE MANY SUBPARTITIONS):, Binary registry: Not installed, PDB PDB_001T: Rolled back successfully on 19-AUG-23 09.58.11.269998 AM, PDB CDB$ROOT: Not installed, PDB PDB$SEED: Not installed, Interim patch 32067171 (OJVM RELEASE UPDATE: 19.10.0.0.210119 (32067171)):, Binary registry: Not installed, PDB PDB_001T: Rolled back successfully on 06-MAR-22 10.57.35.074017 AM, PDB CDB$ROOT: Not installed, PDB PDB$SEED: Not installed, Interim patch 33192694 (OJVM RELEASE UPDATE: 19.13.0.0.211019 (33192694)):, Binary registry: Not installed, PDB PDB_001T: Rolled back successfully on 19-AUG-23 09.58.11.262033 AM, PDB CDB$ROOT: Not installed, PDB PDB$SEED: Not installed, Interim patch 33522539 (MERGE ON DATABASE RU 19.13.0.0.0 OF 33280027):, Binary registry: Not installed, PDB PDB_001T: Rolled back successfully on 19-AUG-23 09.58.11.271219 AM, PDB CDB$ROOT: Not installed, PDB PDB$SEED: Not installed, Interim patch 34786990 (OJVM RELEASE UPDATE: 19.18.0.0.230117 (34786990)):, Binary registry: Not installed, PDB PDB_001T: Rolled back successfully on 17-AUG-24 08.59.17.242116 AM, PDB CDB$ROOT: Not installed, PDB PDB$SEED: Not installed, Interim patch 34972375 (DATAPUMP BUNDLE PATCH 19.18.0.0.0):, Binary registry: Not installed, PDB PDB_001T: Rolled back successfully on 17-AUG-24 08.59.19.038902 AM, PDB CDB$ROOT: Not installed, PDB PDB$SEED: Not installed, Interim patch 36199232 (OJVM RELEASE UPDATE: 19.23.0.0.240416 (36199232)):, Binary registry: Not installed, PDB PDB_001T: Applied successfully on 17-AUG-24 08.59.17.362926 AM, PDB CDB$ROOT: Applied successfully on 18-APR-24 10.08.56.234640 AM, PDB PDB$SEED: Applied successfully on 18-APR-24 10.19.33.039940 AM, Interim patch 36420641 (DATAPUMP BUNDLE PATCH 19.23.0.0.0):, Binary registry: Not installed, PDB PDB_001T: Applied successfully on 17-AUG-24 09.00.21.159959 AM, PDB CDB$ROOT: Applied successfully on 02-OCT-24 11.47.34.300679 AM, PDB PDB$SEED: Applied successfully on 02-OCT-24 11.50.34.101031 AM, Interim patch 37102264 (OJVM RELEASE UPDATE: 19.26.0.0.250121 (37102264)):, Binary registry: Installed, PDB PDB_001T: Not installed, PDB CDB$ROOT: Not installed, PDB PDB$SEED: Not installed, Interim patch 37470729 (DATAPUMP BUNDLE PATCH 19.26.0.0.0):, Binary registry: Installed, PDB PDB_001T: Not installed, PDB CDB$ROOT: Not installed, PDB PDB$SEED: Not installed, Current state of release update SQL patches:, Binary registry:, 19.26.0.0.0 Release_Update 250118124854: Installed, PDB PDB_001T:, Applied 19.23.0.0.0 Release_Update 240406004238 successfully on 17-AUG-24 08.59.50.930598 AM, PDB CDB$ROOT:, Applied 19.23.0.0.0 Release_Update 240406004238 successfully on 18-APR-24 10.19.15.621942 AM, PDB PDB$SEED:, Applied 19.23.0.0.0 Release_Update 240406004238 successfully on 18-APR-24 10.28.06.019862 AM, Adding patches to installation queue and performing prereq checks...done, Installation queue:, For the following PDBs: CDB$ROOT PDB$SEED PDB_001T, The following interim patches will be rolled back:, 36199232 (OJVM RELEASE UPDATE: 19.23.0.0.240416 (36199232)), 26749785 (PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK), 27605010 (DST UPGRADE SLOW (BEGIN_UPGRADE AND UPGRADE_DATABASE) EVEN WITH PATCH 19704999), 36420641 (DATAPUMP BUNDLE PATCH 19.23.0.0.0), Patch 37260974 (Database Release Update : 19.26.0.0.250121 (37260974)):, Apply from 19.23.0.0.0 Release_Update 240406004238 to 19.26.0.0.0 Release_Update 250118124854, The following interim patches will be applied:, 37102264 (OJVM RELEASE UPDATE: 19.26.0.0.250121 (37102264)), 26749785 (PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK), 27605010 (DST UPGRADE SLOW (BEGIN_UPGRADE AND UPGRADE_DATABASE) EVEN WITH PATCH 19704999), 37470729 (DATAPUMP BUNDLE PATCH 19.26.0.0.0), DBD::Oracle::st execute failed: ORA-01691: unable to extend lob segment SYS.SYS_LOB0000023009C00008$$ by 1024 in tablespace SYSTEM, ORA-06512: at line 2 (DBD ERROR: OCIStmtExecute) [for Statement \"BEGIN, INSERT INTO sys.dba_registry_sqlpatch_ru_info, (patch_id,, patch_uid,, patch_descriptor,, ru_version,, ru_build_description,, ru_build_timestamp,, patch_directory), VALUES, (:patch_id,, :patch_uid,, :patch_descriptor,, :ru_version,, :ru_build_description,, TO_TIMESTAMP(:ru_build_timestamp, 'YYMMDDHH24MISS'),, :patch_directory);, COMMIT;, END;\" with ParamValues: :patch_descriptor=OCIXMLTypePtr=SCALAR(0x4b4dcb0), :patch_directory='PK.........y4Z\ufffd&(.\ufffd...........37260974_rollback.sql\ufffd.]s.\u05ba.\ufffd\ufffd+t\ufffd\ufffdng\ufffd.o\ufffd\ufffd\ufffd\ufffdv.\ufffd?2\ufffd\ufffd\ufffd\ufffd\ufffdF..\ufffd$ . [\ufffd\ufffd\ufffd.@.q\ufffd\ufffd\ufffddQ.\ufffdTqc\ufffd\ufffd\u00fb\ufffd\ufffdz\ufffd\ufffd\ufffdrv\ufffd8.\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd.\ufffd\ufffd\ufffd..\ufffd\ufffd\ufffd\ufffd(M\ufffd\u03f3\ufffd\ufffd\u00b4.]%\ufffd,u\n \ufffdz\ufffd\ufffd.\ufffd8\ufffd\ufffd\ufffd.\ufffd\ufffd.s\ufffdf\ufffd\ufffd\ufffd\ufffd\ufffd,J\ufffdWa.\ufffda6\ufffdy\ufffd.zp\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd,..\ufffd?\ufffdl\ufffd\ufffd\ufffdt\ufffd\ufffd\ufffd..\ufffd\/fW\ufffd(j\ufffd}pp\ufffd8^\ufffd\ufffd..~w\ufffdN.\ufffd?\ufffd..\ufffd.\ufffd\ufffd.(Z\ufffd\ufffd\ufffde\ufffd\ufffd.\ufffd\ufffd\ufffd\ufffd\ufffd\ufffdb\ufffd\ufffd\ufffd.\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffdK6E\ufffd+\ufffd?\ufffd\ufffdA.ln._\ufffd.=.\ufffdqp\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd.\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\u01eb.q\ufecb\ufffd\ufffd.\ufffd\ufffd\ufffd.\ufffd.\u03b2 \ufffd\\\/x\ufffd\ufffd.M\ufffdQ\ufffd_\ufffdq\ufffd\u00fd7.-N\ufffdTory\ufffd|\ufffd\ufffd\ufffdy\ufffd&E..y\ufffd\ufffdi\ufffd\ufffd..)\ufffdN.\ufffd.7\ufffd\ufffd.\u05cc\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffdoqxz|\ufffd|st\ufffdX...\ufffd\ufffd\ufffd\ufffd\ufffd\ufffdG'\ufffd\ufffd.N\ufffd_\ufffd.?..*\ufffd.\ufffd....\/\ufffd\ufffd\ufffd\ufffd.\ufffd\ufffd?|\ufffdpWn.\ufffd*\ufffd\ufffd;;;.}\ufffd\ufffd.\ufffd.\ufffd+\ufffd\ufffd\ufffd\ufffd..fJ\ufffd`., 7+\ufffd\ufffdz\ufffd>.?\n \ufffdY\ufffd.\ufffd.\ufffd\ufffd...\ufffd.,...N\ufffd\ufffd9\ufffd\ufffd.\ufffd\ufffd.Y\ufffdrp\ufffd\ufffd\ufffd\ufffdO\ufffd\ufffd8_\ufffd\ufffd\ufffdO\ufffd\ufffd%\ufffd.E\ufffdF\ufffd.\ufffd\ufffdt\ufffd|\ufffd\ufffd.\ufffd\ufffd.\ufffdQ|\ufffdL\ufffd\ufffd\ufffd\ufffd\ufffdy.\ufffd\ufffd[\ufffd'\ufffd|.\ufffd\ufffd\ufffd.\ufffd.y\ufffd\u00eb.\ufffd:xy\ufffd..pS>\ufffd\ufffd.|U.\ufffd\ufffdr\ufffd\/j\ufffd?=:\ufffd\\...\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd.\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffdry\ufffd\ufffd\ufffd\ufffd\ufffdQY\ufffdJ.\ufffd.}N\ufffd\ufffd.\ufffd.S%\ufffd\ufffd\ufffd\ufffd\ufffd\ufffdj\ufffd^j.=7T\ufffdZ\ufffde.W\ufffdz.\ufffd?..\ufffd>\ufffd\ufffd?\ufffdw\ufffd.{w9{\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\/\u01cb\ufffd\ufffd\ufffd\ufffd\ufffd\ufffd\ufffdf])\ufffd.\ufffd\ufffd\ufffd\ufffd\ufffd.O\ufffd*\ufffd\n\ufffd\ufffd\u03f6!\ufffd\ufffd\ufffd\ufffd?\ufffd.\ufffd\ufffd&)\ufffd\ufffd\ufffdI\ufffdtzv\ufffdx\ufffd\ufffd., \ufffdLU.\ufffdIV\ufffd..7.R7.y\ufffd\ufffd&h{*\ufffd3.\ufffdmJm}n(, _\ufffd...\ufffd\ufffd2\ufffdL\u0770\ufffdr*\u00e7..\ufffdS7\u0572@\ufffdV\ufffd\ufffd.1>\ufffd\ufffd\ufffd'\ufffd2\ufffd.\ufffd\ufffd., ...\ufffd9.m)s.\ufffdS.\u0234\ufffdT\ufffd\ufffdK.\ufffd.$!'\ufffd..;\ufffdZ\ufffd.#T\ufffd.\ufffd\ufffd(\ufffdf.\ufffd\ufffd.\ufffdi.pBK\ufffd\ufffdh\ufffdfX*\u07e9...\ufffd\ufffdi\ufffd, \ufffd.*d\ufffd.\ufffde..6.Oy!*\ufffd.:\ufffd.MQ4s\ufffd\ufffd\ufffd.\ufffd...\ufffdSW\ufffd\ufffd|\ufffd\ufffd...F\ufffdOC\ufffd,e\ufffd..\ufffd\"\/\ufffd\ufffd:5\ufffd...', :patch_id='37260974', :patch_uid='26040769', :ru_build_description=\"Release_Update\", :ru_build_timestamp=\"250118124854\", :ru_version=\"19.26.0.0.0\"] at \/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3\/sqlpatch\/sqlpatch.pm line 5337., Please refer to MOS Note 1609718.1 and\/or the invocation log, \/u02\/app\/oracle\/cfgtoollogs\/sqlpatch\/sqlpatch_258023_2025_05_05_14_50_06\/sqlpatch_invocation.log, for information on how to resolve the above errors., SQL Patching tool complete on Mon May 5 14:50:40 2025]\nExit code of the operation:1\nReleasing lock: cdbtest\nReleasing lock: _u02_app_oracle_product_19.0.0.0_dbhome_1\nReleasing lock: _u02_app_oracle_product_19.0.0.0_dbhome_3\n*** Executing jobs which need to be run always... ***\n-----------------\nRunning post_patch_lock_manager job\nCompleted post_patch_lock_manager job\n******** PLUGIN EXECUTION FAILED ********\nTo resume this failed session, run the following command:\ndbaascli database move --oracleHome \/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3 --dbname CDBTEST --sessionID 15920 --resume\n<\/pre>\n<\/br>\n\n\n\nAs we can see the command failed with following error:<\/p>\n\n\n\n
[FATAL] [DBAAS-60022] Command '\/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3\/OPatch\/datapatch -verbose' has failed on nodes [exacc-cl01n1].\n7470729 (DATAPUMP BUNDLE PATCH 19.26.0.0.0), DBD::Oracle::st execute failed: ORA-01691: unable to extend lob segment SYS.SYS_LOB0000023009C00008$$ by 1024 in tablespace SYSTEM<\/code><\/pre>\n\n\n\nTroubleshooting<\/h3>\n\n\n\n
So let’s troubleshoot!<\/p>\n\n\n\n
The database has been moved to the new dbhome, and the dbaascli command failed on datapatch level.<\/p>\n\n\n\n
\noracle@exacc-cl01n1:\/u02\/app\/oracle\/local\/dmk\/etc\/ [rdbms1900] CDBTEST1\n2025-05-05_14-56-12::DMK_ENV.pm::read_oratab ::INFO ==> changed ORACLE_HOME found in oratab: +ASM1 - old=\/u01\/app\/19.0.0.0\/grid, new=\/u02\/app\/23.0.0.0\/gridhome_1\n\n **********************************\n INSTANCE_NAME : CDBTEST1\n DB_NAME : CDBTEST\n DB_UNIQUE_NAME : CDBTEST_CHZ2\n STATUS : OPEN READ WRITE\n LOG_MODE : ARCHIVELOG\n USERS\/SESSIONS : 2\/7\n DATABASE_ROLE : PRIMARY\n FLASHBACK_ON : YES\n FORCE_LOGGING : YES\n VERSION : 19.26.0.0.0\n CDB_ENABLED : YES\n PDBs : PDB_001T PDB$SEED\n **********************************\n\n PDB color: pdbname=mount, pdbname=open read-write, pdbname=open read-only\n Statustime: 2025-05-05 14:56:12\n\noracle@exacc-cl01n1:\/u02\/app\/oracle\/local\/dmk\/etc\/ [CDBTEST1 (CDB$ROOT)] echo $ORACLE_HOME\n\/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3\n<\/pre>\n<\/br>\n\n\n\nAnd the PDB is opened read write.<\/p>\n\n\n\n
\noracle@exacc-cl01n1:\/u02\/app\/oracle\/local\/dmk\/etc\/ [CDBTEST1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Mon May 5 14:56:31 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 4 PDB_001T READ WRITE NO\nSQL>\n<\/pre>\n<\/br>\n\n\n\nLet’s try to run datapatch manually, expecting it will fail with same errors. But it might help me to extract more easily datapatch result.<\/p>\n\n\n\n
\noracle@exacc-cl01n1:\/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3\/ [CDBTEST1 (CDB$ROOT)] cd OPatch\/\n\noracle@exacc-cl01n1:\/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3\/OPatch\/ [CDBTEST1 (CDB$ROOT)] .\/datapatch -verbose\nSQL Patching tool version 19.26.0.0.0 Production on Mon May 5 14:57:00 2025\nCopyright (c) 2012, 2025, Oracle. All rights reserved.\n\nLog file for this invocation: \/u02\/app\/oracle\/cfgtoollogs\/sqlpatch\/sqlpatch_309940_2025_05_05_14_57_00\/sqlpatch_invocation.log\n\nConnecting to database...OK\nGathering database info...done\n\nNote: Datapatch will only apply or rollback SQL fixes for PDBs\n that are in an open state, no patches will be applied to closed PDBs.\n Please refer to Note: Datapatch: Database 12c Post Patch SQL Automation\n (Doc ID 1585822.1)\n\nBootstrapping registry and package to current versions...done\nDetermining current state...done\n\nCurrent state of interim SQL patches:\nInterim patch 26749785 (PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK):\n Binary registry: Not installed\n PDB PDB_001T: Rolled back successfully on 17-AUG-24 08.59.18.040319 AM\n PDB CDB$ROOT: Not installed\n PDB PDB$SEED: Not installed\nInterim patch 26749785 (PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK):\n Binary registry: Not installed\n PDB PDB_001T: Applied successfully on 17-AUG-24 08.59.56.646477 AM\n PDB CDB$ROOT: Applied successfully on 02-OCT-24 11.46.11.005940 AM\n PDB PDB$SEED: Applied successfully on 02-OCT-24 11.47.47.794119 AM\n...\n...\n...\nDBD::Oracle::st execute failed: ORA-01691: unable to extend lob segment SYS.SYS_LOB0000023009C00008$$ by 1024 in tablespace SYSTEM\nORA-06512: at line 2 (DBD ERROR: OCIStmtExecute) [for Statement \"BEGIN\n INSERT INTO sys.dba_registry_sqlpatch_ru_info\n (patch_id,\n patch_uid,\n patch_descriptor,\n ru_version,\n ru_build_description,\n ru_build_timestamp,\n patch_directory)\n VALUES\n (:patch_id,\n :patch_uid,\n :patch_descriptor,\n :ru_version,\n :ru_build_description,\n TO_TIMESTAMP(:ru_build_timestamp, 'YYMMDDHH24MISS'),\n :patch_directory);\n COMMIT;\n END;\" with ParamValues: :patch_descriptor=OCIXMLTypePtr=SCALAR(0x4611c98), :patch_directory='PK.........y4Z\u2592&(.\u2592...........37260974_rollback.sql\u2592.]s.\u05ba.\u2592\u2592+t\u2592\u2592ng\u2592.o\u2592\u2592\u2592\u2592v.\u2592\u034c?2\u2592\u2592\u2592\u2592\u2592F..\u2592$ . [\u2592\u2592\u2592.@.q\u2592\u2592\u2592dQ.\u2592Tqc\u2592\u2592\u00fb\u2592\u2592z\u2592\u2592\u2592rv\u25928.\u2592\u2592\u2592\u2592\u2592\u2592\u2592.\u2592\u2592\u2592..\u2592\u2592\u2592\u2592(M\u2592\u03f3\u2592\u2592\u00b4.]%\u2592,u\n \u2592z\u2592\u2592.\u25928\u2592\u2592\u2592.\u2592\u2592.s\u2592f\u2592\u2592\u2592\u2592\u2592,J\u2592Wa.\u2592a6\u2592y\u2592.zp\u2592\u2592\u2592\u2592\u2592\u2592\u2592,..\u2592?\u2592l\u2592\u2592\u2592t\u2592\u2592\u2592..\u2592\/fW\u2592(j\u2592}pp\u25928^\u2592\u2592..~w\u2592N.\u2592?\u2592..\u2592.\u2592\u2592.(Z\u2592\u2592\u2592e\u2592\u2592.\u2592\u2592\u2592\u2592\u2592\u2592b\u2592\u2592\u2592.\u2592\u2592\u2592\u2592\u2592\u2592\u2592K6E\u2592+\u2592?\u2592\u2592A.ln._\u2592.=.\u2592\u0738qp\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592.\u2592\u2592\u2592\u2592\u2592\u2592\u01eb.q\ufecb\u2592\u2592.\u2592\u2592\u2592.\u2592.\u03b2 \u2592\\\/x\u2592.M\u2592Q\u2592_\u2592q\u2592\u00fd7.-N\u2592Tory\u2592|\u2592\u2592\u2592y\u2592&E..y\u2592\u2592i\u2592\u2592..)\u2592N.\u2592.7\u2592\u2592.\u05cc\u2592\u2592\u2592\u2592\u2592\u2592\u2592\u2592oqxz|\u2592|st\u2592X...\u2592\u2592\u2592\u2592\u2592\u2592G'\u2592\u2592.N\u2592_\u2592.?..*\u2592.\u2592....\/\u2592\u2592\u2592\u2592.\u2592\u2592?|\u2592pWn.\u2592*\u2592\u2592;;;.}\u2592\u2592.\u2592.\u2592+\u2592\u2592\u2592\u2592..fJ\u2592`.\n7+\u2592\u2592z\u2592>.?\n \u2592Y\u2592.\u2592.\u2592\u2592...\u2592.,...N\u2592\u25929\u2592.\u2592\u2592.Y\u2592rp\u2592\u2592\u2df7\u2592\u2592O\u25928_\u2592\u2592\u2592O\u2592\u2592%\u2592.E\u2592F\u2592.\u2592\u2592t\u2592|\u2592\u2592.\u2592\u2592.\u2592Q|\u2592L\u2592\u2592\u2592\u2592y.\u2592\u2592[\u2592'\u2592|.\u2592\u2592\u2592.\u2592.y\u2592\u00eb.\u2592:xy\u2592..pS>\u2592\u2592.|U.\u2592\u2592r\u2592\/j\u2592?=:\u2592\\...\u2592\u2592\u2592\u2592\u2592\u2592.\u2592\u2592\u2592\u2592\u2592\u2592\u2592ry\u2592\u2592\u2592\u2592\u2592QY\u2592J.\u2592.}N\u2592\u2592.\u2592.S%\u2592\u2592\u2592\u2592\u2592\u2592j\u2592^j.=7T\u2592Z\u2592e.W\u2592z.\u2592?..\u2592>\u2592\u2592?\u2592w\u2592.{w9{\u2592\u2592\u2592\u2592\u2592\u2592\/\u01cb\u2592\u2592\u2592\u2592\u2592\u2592\u2592f])\u2592.\u2592\u2592\u2592\u2592.O\u2592*\u2592\n\u2592\u2592\u03f6!\u2592\u2592\u2592\u2592?\u2592.\u2592\u2592&)\u2592\u2592\u2592I\u2592tzv\u2592x\u2592\u2592.\n\u2592LU.\u2592IV\u2592..7.R7.y\u2592\u2592&h{*\u25923.\u2592mJm}n(\n_\u2592...\u2592\u25922\u2592L\u0770\u2592r*\u00e7..\u2592S7\u0572@\u2592V\u2592\u2592.1>\u2592\u2592\u2592'\u25922\u2592.\u2592\u2592.\n...\u25929.m)s.\u2592S.\u0234\u2592T\u2592\u2592K.\u2592.$!'\u2592..;\u2592Z\u2592.#T\u2592.\u2592\u2592(\u2592f.\u2592\u2592.\u2592i.pBK\u2592\u2592h\u2592fX*\u07e9...\u2592\u2592i\u2592\n\u2592.*d\u2592.\u2592e..6.Oy!*\u2592.:\u2592.MQ4s\u2592\u2592\u2592.\u2592...\u2592SW\u2592\u2592|\u2592\u2592...F\u2592OC\u2592,e\u2592..\u2592\"\/\u2592\u2592:5\u2592...', :patch_id=\"37260974\", :patch_uid=\"26040769\", :ru_build_description=\"Release_Update\", :ru_build_timestamp=\"250118124854\", :ru_version=\"19.26.0.0.0\"] at \/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3\/sqlpatch\/sqlpatch.pm line 5337.\n\n\nPlease refer to MOS Note 1609718.1 and\/or the invocation log\n\/u02\/app\/oracle\/cfgtoollogs\/sqlpatch\/sqlpatch_309940_2025_05_05_14_57_00\/sqlpatch_invocation.log\nfor information on how to resolve the above errors.\n\nSQL Patching tool complete on Mon May 5 14:57:34 2025\n<\/pre>\n<\/br>\n\n\n\nLet’s check SYSTEM tablespace usage in the CDB$ROOT.<\/p>\n\n\n\n
\noracle@exacc-cl01n1:~\/ [CDBTEST1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Mon May 5 15:02:00 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> @qdbstbssize.sql\n\nPL\/SQL procedure successfully completed.\n\n\n Nb Extent Segment Alloc. Space Max. Percent Block\nName files Type Mgmnt Mgmnt Size (GB) Free (GB) Size (GB) used % size Log Encrypt Compress\n------------------------- ----- ---- ------ ------- ---------- ---------- ---------- ------- ----- --- ------- --------\nSYSAUX 1 DATA LM-SYS AUTO 5.95 4.47 32768.00 .00 8 KB YES YES NO\nSYSTEM 1 DATA LM-SYS MANUAL 1.95 .62 32768.00 .00 8 KB YES YES NO\nTEMP 1 TEMP LM-UNI MANUAL 1.00 2.31 512.00 -.26 8 KB NO YES NO\nUNDOTBS1 1 UNDO LM-SYS MANUAL 1.95 1.89 512.00 .01 8 KB YES YES NO\nUSERS 1 DATA LM-SYS AUTO 1.00 .93 32768.00 .00 8 KB YES YES NO\n ----- ---------- ---------- ----------\nTOTAL 5 11.85 10.22 99328.00\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nWe can see all is ok. Let’s check the same in the PDB.<\/p>\n\n\n\n
\nSQL> alter session set container=PDB_001T;\n\nSession altered.\n\nSQL> @qdbstbssize.sql\n...\n...\n...\nSYSAUX 1 DATA LM-SYS AUTO 82.62 74.52 32768.00 .02 8 KB YES YES NO\nSYSTEM 1 DATA LM-SYS MANUAL 24.71 .10 32768.00 .08 8 KB YES YES NO\nTEMP 1 TEMP LM-UNI MANUAL 114.26 342.75 32768.00 -.70 8 KB NO YES NO\nUNDO 1 UNDO LM-SYS MANUAL 684.57 673.58 32768.00 .03 8 KB YES YES NO\nUSERS 1 DATA LM-SYS AUTO 20.00 19.93 20.00 .33 8 KB YES YES NO\n ----- ---------- ---------- ----------\nTOTAL 2732 7101.04 1385.79 ##########\n\n2732 rows selected.\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nIt’s all good as well. And the pdb$seed?<\/p>\n\n\n\n
\nSQL> alter session set container=PDB$SEED;\n\nSession altered.\n\nSQL> @qdbstbssize.sql\n\nPL\/SQL procedure successfully completed.\n\n\n Nb Extent Segment Alloc. Space Max. Percent Block\nName files Type Mgmnt Mgmnt Size (GB) Free (GB) Size (GB) used % size Log Encrypt Compress\n------------------------- ----- ---- ------ ------- ---------- ---------- ---------- ------- ----- --- ------- --------\nSYSAUX 1 DATA LM-SYS AUTO .59 .08 32768.00 .00 8 KB YES NO NO\nSYSTEM 1 DATA LM-SYS MANUAL .59 .00 32768.00 .00 8 KB YES NO NO\nTEMP 1 TEMP LM-UNI MANUAL .18 .00 32768.00 .00 8 KB NO NO NO\nUNDOTBS1 1 UNDO LM-SYS MANUAL .59 .33 512.00 .05 8 KB YES NO NO\n ----- ---------- ---------- ----------\nTOTAL 4 1.95 .41 98816.00\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nAll is ok as well.<\/p>\n\n\n\n
Let’s check where this SYS_LOB belongs to. cdb$root? PDB? pdb$seed?<\/p>\n\n\n\n
\nSQL> alter session set container=PDB$SEED;\n\nSession altered.\n\nSQL> select tablespace_name, table_name from dba_lobs where segment_name='SYS_LOB0000023009C00008$$' and owner='SYS';\n\nTABLESPACE_NAME TABLE_NAME\n------------------------------ --------------------------------------------------------------------------------------------------------------------------------\nSYSTEM REGISTRY$SQLPATCH_RU_INFO\n\nSQL> alter session set container=cdb$root;\n\nSession altered.\n\nSQL> select tablespace_name, table_name from dba_lobs where segment_name='SYS_LOB0000023009C00008$$' and owner='SYS';\n\nno rows selected\n\nSQL> alter session set container=PDB_001T;\n\nSession altered.\n\nSQL> select tablespace_name, table_name from dba_lobs where segment_name='SYS_LOB0000023009C00008$$' and owner='SYS';\n\nno rows selected\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nSo the LOB belongs to the pdb$seed.<\/p>\n\n\n\n
From the alert log I can see:<\/p>\n\n\n\n
PDB$SEED(2):Pluggable database PDB$SEED opening in read write\nPDB$SEED(2):Autotune of undo retention is turned on.\nPDB$SEED(2):This instance was first to open pluggable database PDB$SEED (container=2)\nPDB$SEED(2):queued attach DA request 0xb2325ed8 for pdb 2, ospid 3457\n2025-05-05T15:11:01.061406+02:00\nDomain Action Reconfiguration started (domid 2, new da inc 19, cluster inc 2)\nInstance 1 is attaching to domain 2\n Global Resource Directory partially frozen for domain action\nDomain Action Reconfiguration complete (total time 0.0 secs)\n2025-05-05T15:11:01.067485+02:00\nPDB$SEED(2):Endian type of dictionary set to little\nPDB$SEED(2):Undo initialization recovery: Parallel FPTR failed: start:1139322373 end:1139322379 diff:6 ms (0.0 seconds)\nPDB$SEED(2):Undo initialization recovery: err:0 start: 1139322373 end: 1139322392 diff: 19 ms (0.0 seconds)\nPDB$SEED(2):[3457] Successfully onlined Undo Tablespace 2.\nPDB$SEED(2):Undo initialization online undo segments: err:0 start: 1139322392 end: 1139322638 diff: 246 ms (0.2 seconds)\nPDB$SEED(2):Undo initialization finished serial:0 start:1139322373 end:1139322643 diff:270 ms (0.3 seconds)\nPDB$SEED(2):Database Characterset for PDB$SEED is AL32UTF8\nPDB$SEED(2):SUPLOG: Set PDB SUPLOG SGA at PDB OPEN, old 0x0, new 0x0 (no suplog)\nPDB$SEED(2):Opening pdb with no Resource Manager plan active\n2025-05-05T15:11:01.806446+02:00\nPDB$SEED(2):joxcsys_required_dirobj_exists: directory object exists with required path \/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3\/javavm\/admin\/, pid 3457 cid 2\nPluggable database PDB$SEED opened read write\n2025-05-05T15:11:03.081311+02:00\nQPI: opatch file present, opatch\nQPI: qopiprep.bat file present\nQPI: Cleaning and refreshing metadata..\n2025-05-05T15:11:09.187099+02:00\nQPI: Cleaning and refreshing metadata..\n2025-05-05T15:11:23.765174+02:00\nPDB$SEED(2):ORA-1691: unable to extend lobsegment SYS.SYS_LOB0000023009C00008$$ by 1024 in tablespace SYSTEM [PDB$SEED] (ospid 3221)\n2025-05-05T15:11:24.482146+02:00\nPDB$SEED(2):Pluggable database PDB$SEED closing<\/code><\/pre>\n\n\n\nSo we can see that once the pdb$seed is opened in read write mode, datapatch is failing due to the fact it is not possible to extend the SYS.SYS_LOB0000023009C00008$$ lob segment.<\/p>\n\n\n\n
Let’s look into the ASM to see if there is enough disk space.<\/p>\n\n\n\n
\nASMCMD> lsdg\nState Type Rebal Sector Logical_Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name\nMOUNTED HIGH N 512 512 4096 4194304 49072128 56708 0 18902 0 Y DATAC4\/\nMOUNTED HIGH N 512 512 4096 4194304 16356864 13063776 0 4354592 0 N RECOC4\/\nMOUNTED HIGH N 512 512 4096 4194304 163568640 163563936 0 54521312 0 N SPRC4\/\nASMCMD>\n<\/pre>\n<\/br>\n\n\n\nThere is not a lot of usable space for the DATA Disk Group, certainly not enough, but still some space. Let’s try to open the pdb$seed in read write and to create a table.<\/p>\n\n\n\n
\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n\nSQL> shutdown immediate\nPluggable Database closed.\n\nSQL> alter pluggable database open read write;\n\nPluggable database altered.\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ WRITE NO\n\nSQL> create table xxx (n number) tablespace system;\n\nTable created.\n\nSQL> insert into xxx values (10);\n\n1 row created.\n\nSQL> commit;\n\nCommit complete.\n\nSQL> drop table xxx purge;\n\nTable dropped.\n<\/pre>\n<\/br>\n\n\n\nThis is possible. Let’s try to resize system data file.<\/p>\n\n\n\n
\nSQL> alter database datafile 2 resize 2048M;\nalter database datafile 2 resize 2048M\n*\nERROR at line 1:\nORA-01237: cannot extend datafile 2\nORA-01110: data file 2: '+DATAC4\/CDBTEST_CHZ2\/165C22D4CFFCA759E0638A534664B46C\/DATAFILE\/system.615.1181302705'\nORA-17505: ksfdrsz:1 Failed to resize file to size 262144 blocks\nORA-15041: diskgroup \"DATAC4\" space exhausted\n<\/pre>\n<\/br>\n\n\n\nThis is not possible and it is confirmed DATA Disk Group does not have enough available space.<\/p>\n\n\n\n
I first will reopen the pdb$seed in read only.<\/p>\n\n\n\n
\nSQL> shutdown immediate\nPluggable Database closed.\n\nSQL> alter pluggable database open read only;\n\nPluggable database altered.\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\nSQL>\n<\/pre>\n<\/br>\n\n\n\nFollowing DocId would explain the problem. One or more disk having 0 free MB:<\/p>\n\n\n\n
Datapatch failed with ORA-01691: unable to extend lob segment on MGMTDB (Doc ID 2352895.1)<\/p>\n\n\n\n
Let’s check, connecting to the +ASM instance.<\/p>\n\n\n\n
\nSQL> select instance_name from v$instance;\n\nINSTANCE_NAME\n----------------\n+ASM1\n\nSQL> select group_number, name from v$asm_diskgroup;\n\nGROUP_NUMBER NAME\n------------ ------------------------------\n 1 DATAC4\n 2 RECOC4\n 3 SPRC4\n\nSQL> select DISK_NUMBER, FREE_MB from v$asm_disk where group_number=1 and FREE_MB=0;\n\nDISK_NUMBER FREE_MB\n----------- ----------\n 48 0\n\nSQL> select count(*) from v$asm_disk where group_number=1 and FREE_MB 0;\n\n COUNT(*)\n----------\n 95\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nYes, this is exactly the problem! Disk Number 48 has got 0 free MB.<\/p>\n\n\n\n
Resolution<\/h3>\n\n\n\n
Let’s resolve the problem.<\/p>\n\n\n\n
Through the OCI console, I added 1 TB to the ASM. The usable space of the disk groups then became as following:<\/p>\n\n\n\n
\nASMCMD> lsdg\nState Type Rebal Sector Logical_Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files Name\nMOUNTED HIGH Y 512 512 4096 4194304 50959872 1932164 0 644054 0 Y DATAC4\/\nMOUNTED HIGH N 512 512 4096 4194304 16356864 13058556 0 4352852 0 N RECOC4\/\nMOUNTED HIGH N 512 512 4096 4194304 163568640 163563936 0 54521312 0 N SPRC4\/\nASMCMD>\n<\/pre>\n<\/br>\n\n\n\nI checked to ensure there is no more disks with 0 free MB.<\/p>\n\n\n\n
\n[grid@exacc-cl01n1 ~]$ sqlplus \/ as sysdba\n\nSQL*Plus: Release 23.0.0.0.0 - for Oracle Cloud and Engineered Systems on Mon May 5 16:28:11 2025\nVersion 23.7.0.25.01\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 23ai Enterprise Edition Release 23.0.0.0.0 - for Oracle Cloud and Engineered Systems\nVersion 23.7.0.25.01\n\nSQL> select instance_name from v$instance;\n\nINSTANCE_NAME\n----------------\n+ASM1\n\nSQL> select DISK_NUMBER, FREE_MB from v$asm_disk where group_number=1 and FREE_MB=0;\n\nno rows selected\n\nSQL> select count(*) from v$asm_disk where group_number=1 and FREE_MB 0;\n\n COUNT(*)\n----------\n 96\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nI resume the dbaascli move operation, which became successful.<\/p>\n\n\n\n
\n[root@exacc-cl01n1 ~]# dbaascli database move --oracleHome \/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3 --dbname CDBTEST --sessionID 15920 --resume\nDBAAS CLI version 25.1.1.0.0\nExecuting command database move --oracleHome \/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3 --dbname CDBTEST --sessionID 15920 --resume\nJob id: 7e59d18a-ca1b-4808-a927-c3ce9131b968\nSession log: \/var\/opt\/oracle\/log\/CDBTEST\/database\/move\/dbaastools_2025-05-05_05-52-50-PM_350983.log\nLoading PILOT...\nSession ID of the current execution is: 15932\nLog file location: \/var\/opt\/oracle\/log\/CDBTEST\/database\/move\/pilot_2025-05-05_05-52-54-PM_351354\n-----------------\nRunning initialization job\nCompleted initialization job\n-----------------\nAcquiring write lock: cdbtest\nAcquiring read lock: _u02_app_oracle_product_19.0.0.0_dbhome_1\nAcquiring read lock: _u02_app_oracle_product_19.0.0.0_dbhome_3\nRunning datapatch_and_recompile_invalid_objects job\nDatapatch execution on database 'CDBTEST' is in progress\nDatapatch execution on database 'CDBTEST' is complete\nRecompilation of invalid objects on database 'CDBTEST' is in progress\nRecompilation of invalid objects on database 'CDBTEST' is complete\nCompleted datapatch_and_recompile_invalid_objects job\n-----------------\nRunning update_pdb_status job\nCompleted update_pdb_status job\n-----------------\nRunning post_patch_lock_manager job\nCompleted post_patch_lock_manager job\nReleasing lock: cdbtest\nReleasing lock: _u02_app_oracle_product_19.0.0.0_dbhome_1\nReleasing lock: _u02_app_oracle_product_19.0.0.0_dbhome_3\n-----------------\nRunning invoke_backup_asst job\nCompleted invoke_backup_asst job\n-----------------\nRunning post_move_validation job\nCompleted post_move_validation job\n-----------------\nRunning generate_dbsystem_details job\nAcquiring native write lock: global_dbsystem_details_generation\nReleasing native lock: global_dbsystem_details_generation\nCompleted generate_dbsystem_details job\n\ndbaascli execution completed\nYou have new mail in \/var\/spool\/mail\/root\n<\/pre>\n<\/br>\n\n\n\nAnd I checked database patch version for the cdb$root and the pdb.<\/p>\n\n\n\n
\noracle@exacc-cl01n1:~\/ [rdbms1900] CDBTEST1\n2025-05-05_18-01-21::DMK_ENV.pm::read_oratab ::INFO ==> changed ORACLE_HOME found in oratab: +ASM1 - old=\/u01\/app\/19.0.0.0\/grid, new=\/u02\/app\/23.0.0.0\/gridhome_1\n\n **********************************\n INSTANCE_NAME : CDBTEST1\n DB_NAME : CDBTEST\n DB_UNIQUE_NAME : CDBTEST_CHZ2\n STATUS : OPEN READ WRITE\n LOG_MODE : ARCHIVELOG\n USERS\/SESSIONS : 2\/7\n DATABASE_ROLE : PRIMARY\n FLASHBACK_ON : YES\n FORCE_LOGGING : YES\n VERSION : 19.26.0.0.0\n CDB_ENABLED : YES\n PDBs : PDB_001T PDB$SEED\n **********************************\n\n PDB color: pdbname=mount, pdbname=open read-write, pdbname=open read-only\n Statustime: 2025-05-05 18:01:22\n\noracle@exacc-cl01n1:~\/ [CDBTEST1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Mon May 5 18:01:25 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> set lines 300\nSQL> set tab off\nSQL> set pages 500\n\nSQL> alter session set nls_date_format='DD\/MM\/YYYY HH24:MI:SS';\n\nSession altered.\n\nSQL> col action_time for a30\nSQL> select action_time, patch_id, source_version, target_version, status, description from dba_registry_sqlpatch;\n\nACTION_TIME PATCH_ID SOURCE_VERSION TARGET_VERSION STATUS DESCRIPTION\n------------------------------ ---------- --------------- --------------- ------------------------- ----------------------------------------------------------------------------------------------------\n18-APR-24 10.08.56.234640 AM 36199232 19.1.0.0.0 19.23.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.23.0.0.240416 (36199232)\n18-APR-24 10.19.15.621942 AM 36233263 19.1.0.0.0 19.23.0.0.0 SUCCESS Database Release Update : 19.23.0.0.240416 (36233263)\n02-OCT-24 11.46.11.005940 AM 26749785 19.23.0.0.0 19.23.0.0.0 SUCCESS PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK\n02-OCT-24 11.46.13.343508 AM 27605010 19.23.0.0.0 19.23.0.0.0 SUCCESS DST UPGRADE SLOW (BEGIN_UPGRADE AND UPGRADE_DATABASE) EVEN WITH PATCH 19704999\n02-OCT-24 11.47.34.300679 AM 36420641 19.23.0.0.0 19.23.0.0.0 SUCCESS DATAPUMP BUNDLE PATCH 19.23.0.0.0\n05-MAY-25 05.27.25.226657 PM 36199232 19.23.0.0.0 19.26.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.23.0.0.240416 (36199232)\n05-MAY-25 05.27.26.115643 PM 37102264 19.23.0.0.0 19.26.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.26.0.0.250121 (37102264)\n05-MAY-25 05.27.26.697687 PM 26749785 19.23.0.0.0 19.26.0.0.0 SUCCESS PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK\n05-MAY-25 05.27.28.734483 PM 27605010 19.23.0.0.0 19.26.0.0.0 SUCCESS DST UPGRADE SLOW (BEGIN_UPGRADE AND UPGRADE_DATABASE) EVEN WITH PATCH 19704999\n05-MAY-25 05.27.28.839820 PM 36420641 19.23.0.0.0 19.26.0.0.0 SUCCESS DATAPUMP BUNDLE PATCH 19.23.0.0.0\n05-MAY-25 05.28.35.890001 PM 37260974 19.23.0.0.0 19.26.0.0.0 SUCCESS Database Release Update : 19.26.0.0.250121 (37260974)\n05-MAY-25 05.28.44.283893 PM 26749785 19.23.0.0.0 19.26.0.0.0 SUCCESS PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK\n05-MAY-25 05.28.46.272241 PM 27605010 19.23.0.0.0 19.26.0.0.0 SUCCESS DST UPGRADE SLOW (BEGIN_UPGRADE AND UPGRADE_DATABASE) EVEN WITH PATCH 19704999\n05-MAY-25 05.29.22.101438 PM 37470729 19.23.0.0.0 19.26.0.0.0 SUCCESS DATAPUMP BUNDLE PATCH 19.26.0.0.0\n\n14 rows selected.\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 4 PDB_001T READ WRITE NO\n\nSQL> alter session set container=PDB_001T;\n\nSession altered.\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 4 PDB_001T READ WRITE NO\n\nSQL> select action_time, patch_id, source_version, target_version, status, description from dba_registry_sqlpatch;\n\nACTION_TIME PATCH_ID SOURCE_VERSI TARGET_VERSI STATUS DESCRIPTION\n------------------------------ ---------- ------------ ------------ -------------------- ----------------------------------------------------------------------------------------------------\n19-JUN-21 09.56.16.648813 AM 32067171 19.1.0.0.0 19.1.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.10.0.0.210119 (32067171)\n19-JUN-21 09.56.16.641919 AM 32218454 19.1.0.0.0 19.10.0.0.0 SUCCESS Database Release Update : 19.10.0.0.210119 (32218454)\n19-JUN-21 09.56.17.529234 AM 28318139 19.1.0.0.0 19.1.0.0.0 SUCCESS ORA-31003 ERROR WHEN IMPORTING FULL DATABASE IN PARALLEL\n19-JUN-21 09.56.18.407598 AM 28555193 19.1.0.0.0 19.1.0.0.0 WITH ERRORS DBMS_METADATA.GET_DDL CAPTURE INCORRECT STORAGE OPTIONS OF THE XML COLUMN ON GTT\n19-JUN-21 10.13.13.165620 AM 28555193 19.10.0.0.0 19.10.0.0.0 SUCCESS DBMS_METADATA.GET_DDL CAPTURE INCORRECT STORAGE OPTIONS OF THE XML COLUMN ON GTT\n06-MAR-22 10.57.35.074017 AM 32067171 19.13.0.0.0 19.13.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.10.0.0.210119 (32067171)\n06-MAR-22 10.57.39.351946 AM 33192694 19.10.0.0.0 19.10.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.13.0.0.211019 (33192694)\n06-MAR-22 10.57.36.095921 AM 28318139 19.13.0.0.0 19.13.0.0.0 SUCCESS ORA-31003 ERROR WHEN IMPORTING FULL DATABASE IN PARALLEL\n06-MAR-22 10.57.37.111786 AM 28555193 19.13.0.0.0 19.13.0.0.0 SUCCESS DBMS_METADATA.GET_DDL CAPTURE INCORRECT STORAGE OPTIONS OF THE XML COLUMN ON GTT\n06-MAR-22 10.57.39.348199 AM 33192793 19.10.0.0.0 19.13.0.0.0 SUCCESS Database Release Update : 19.13.0.0.211019 (33192793)\n06-MAR-22 10.57.40.368792 AM 30944402 19.10.0.0.0 19.10.0.0.0 SUCCESS SELECT FROM MASTER TABLE RUNS SLOW DURING TABLE_DATA EXPORT WHEN THERE ARE MANY SUBPARTITIONS\n06-MAR-22 10.57.41.384551 AM 33522539 19.10.0.0.0 19.10.0.0.0 SUCCESS MERGE ON DATABASE RU 19.13.0.0.0 OF 33280027\n19-AUG-23 09.58.11.262033 AM 33192694 19.18.0.0.0 19.18.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.13.0.0.211019 (33192694)\n19-AUG-23 09.58.13.172768 AM 34786990 19.13.0.0.0 19.13.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.18.0.0.230117 (34786990)\n19-AUG-23 09.58.11.269998 AM 30944402 19.18.0.0.0 19.18.0.0.0 SUCCESS SELECT FROM MASTER TABLE RUNS SLOW DURING TABLE_DATA EXPORT WHEN THERE ARE MANY SUBPARTITIONS\n19-AUG-23 09.58.11.271219 AM 33522539 19.18.0.0.0 19.18.0.0.0 SUCCESS MERGE ON DATABASE RU 19.13.0.0.0 OF 33280027\n19-AUG-23 09.58.13.169832 AM 34765931 19.13.0.0.0 19.18.0.0.0 SUCCESS DATABASE RELEASE UPDATE : 19.18.0.0.230117 (REL-JAN230131) (34765931)\n19-AUG-23 09.58.13.340768 AM 26749785 19.13.0.0.0 19.13.0.0.0 SUCCESS PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK\n19-AUG-23 09.58.13.346063 AM 27605010 19.13.0.0.0 19.13.0.0.0 SUCCESS DST UPGRADE SLOW (BEGIN_UPGRADE AND UPGRADE_DATABASE) EVEN WITH PATCH 19704999\n19-AUG-23 09.58.14.253669 AM 34972375 19.13.0.0.0 19.13.0.0.0 SUCCESS DATAPUMP BUNDLE PATCH 19.18.0.0.0\n17-AUG-24 08.59.17.242116 AM 34786990 19.18.0.0.0 19.23.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.18.0.0.230117 (34786990)\n17-AUG-24 08.59.17.362926 AM 36199232 19.18.0.0.0 19.23.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.23.0.0.240416 (36199232)\n17-AUG-24 08.59.18.040319 AM 26749785 19.18.0.0.0 19.23.0.0.0 SUCCESS PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK\n17-AUG-24 08.59.18.971587 AM 27605010 19.18.0.0.0 19.23.0.0.0 SUCCESS DST UPGRADE SLOW (BEGIN_UPGRADE AND UPGRADE_DATABASE) EVEN WITH PATCH 19704999\n17-AUG-24 08.59.19.038902 AM 34972375 19.18.0.0.0 19.23.0.0.0 SUCCESS DATAPUMP BUNDLE PATCH 19.18.0.0.0\n17-AUG-24 08.59.50.930598 AM 36233263 19.18.0.0.0 19.23.0.0.0 SUCCESS Database Release Update : 19.23.0.0.240416 (36233263)\n17-AUG-24 08.59.56.646477 AM 26749785 19.18.0.0.0 19.23.0.0.0 SUCCESS PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK\n17-AUG-24 08.59.57.504574 AM 27605010 19.18.0.0.0 19.23.0.0.0 SUCCESS DST UPGRADE SLOW (BEGIN_UPGRADE AND UPGRADE_DATABASE) EVEN WITH PATCH 19704999\n17-AUG-24 09.00.21.159959 AM 36420641 19.18.0.0.0 19.23.0.0.0 SUCCESS DATAPUMP BUNDLE PATCH 19.23.0.0.0\n05-MAY-25 05.31.01.733241 PM 36199232 19.23.0.0.0 19.26.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.23.0.0.240416 (36199232)\n05-MAY-25 05.31.03.413696 PM 37102264 19.23.0.0.0 19.26.0.0.0 SUCCESS OJVM RELEASE UPDATE: 19.26.0.0.250121 (37102264)\n05-MAY-25 05.31.04.821299 PM 26749785 19.23.0.0.0 19.26.0.0.0 SUCCESS PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK\n05-MAY-25 05.31.06.205197 PM 27605010 19.23.0.0.0 19.26.0.0.0 SUCCESS DST UPGRADE SLOW (BEGIN_UPGRADE AND UPGRADE_DATABASE) EVEN WITH PATCH 19704999\n05-MAY-25 05.31.06.379357 PM 36420641 19.23.0.0.0 19.26.0.0.0 SUCCESS DATAPUMP BUNDLE PATCH 19.23.0.0.0\n05-MAY-25 05.32.25.947558 PM 37260974 19.23.0.0.0 19.26.0.0.0 SUCCESS Database Release Update : 19.26.0.0.250121 (37260974)\n05-MAY-25 05.32.32.616612 PM 26749785 19.23.0.0.0 19.26.0.0.0 SUCCESS PERF_DIAG NEED TO HAVE MORE CONTROL IN DICTIONARY FOR AUTO_STATS_ADVISOR_TASK\n05-MAY-25 05.32.33.746247 PM 27605010 19.23.0.0.0 19.26.0.0.0 SUCCESS DST UPGRADE SLOW (BEGIN_UPGRADE AND UPGRADE_DATABASE) EVEN WITH PATCH 19704999\n05-MAY-25 05.35.48.324333 PM 37470729 19.23.0.0.0 19.26.0.0.0 SUCCESS DATAPUMP BUNDLE PATCH 19.26.0.0.0\n\n38 rows selected.\n<\/pre>\n<\/br>\n\n\n\nAnd finally I checked PDB violations.<\/p>\n\n\n\n
\noracle@exacc-cl01n1:\/u02\/app\/oracle\/product\/19.0.0.0\/dbhome_3\/OPatch\/ [CDBTEST1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Mon May 5 18:10:56 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 4 PDB_001T READ WRITE NO\n\nSQL> alter session set container=PDB_001T;\n\nSession altered.\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 4 PDB_001T READ WRITE NO\n\nSQL> col name for a15\nSQL> col message for a120\nSQL> col cause for a50\nSQL> set lines 300\nSQL> col cause for a20\nSQL> col type for a10\n\nSQL> select name,cause,type,message,status from PDB_PLUG_IN_VIOLATIONS where status 'RESOLVED';\n\nNAME CAUSE TYPE MESSAGE STATUS\n--------------- -------------------- ---------- ------------------------------------------------------------------------------------------------------------------------ ---------------------------\nPDB_001T OPTION WARNING Database option APS mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0. PENDING\nPDB_001T OPTION WARNING Database option CONTEXT mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0. PENDING\nPDB_001T OPTION WARNING Database option DV mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0. PENDING\nPDB_001T OPTION WARNING Database option OLS mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0. PENDING\nPDB_001T OPTION WARNING Database option ORDIM mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0. PENDING\nPDB_001T OPTION WARNING Database option OWM mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0. PENDING\nPDB_001T OPTION WARNING Database option SDO mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0. PENDING\nPDB_001T OPTION WARNING Database option XOQ mismatch: PDB installed version NULL. CDB installed version 19.0.0.0.0. PENDING\n\n8 rows selected.\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nYes, that’s it, all is ok now.<\/p>\n\n\n\n
To wrap up…<\/h3>\n\n\n\n
The database move on another higher version dbhome on the ExaCC failed on the datapatch step, due to the fact one of the Disk had 0 free MB. Adding space to the ASM resolved the issue.<\/p>\n","protected":false},"excerpt":{"rendered":"
I recently had to move a database from a 19.23 to a 19.26 dbhome on an ExaCC. This will include the database to be patched. The command dbaascli database move failed during the datapatch steps with following error: With this blog I would like to share my troubleshooting with you and how I resolved the […]<\/p>\n","protected":false},"author":48,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3624,59],"tags":[3413,2598,2576],"type_dbi":[],"class_list":["post-39701","post","type-post","status-publish","format-standard","hentry","category-exacc-oracle","category-oracle","tag-dbaascli","tag-exacc-3","tag-patching-2"],"acf":[],"yoast_head":"\n
dbaascli database move failing with ORA-01691 on ExaCC - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"dbaascli database move failing with ORA-01691 on ExaCC\" \/>\n<meta property=\"og:description\" content=\"I recently had to move a database from a 19.23 to a 19.26 dbhome on an ExaCC. This will include the database to be patched. The command dbaascli database move failed during the datapatch steps with following error: With this blog I would like to share my troubleshooting with you and how I resolved the […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-07-28T15:59:16+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-07-28T15:59:19+00:00\" \/>\n<meta name=\"author\" content=\"Marc Wagner\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Marc Wagner\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/\"},\"author\":{\"name\":\"Marc Wagner\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"headline\":\"dbaascli database move failing with ORA-01691 on ExaCC\",\"datePublished\":\"2025-07-28T15:59:16+00:00\",\"dateModified\":\"2025-07-28T15:59:19+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/\"},\"wordCount\":494,\"commentCount\":0,\"keywords\":[\"dbaascli\",\"exacc\",\"patching\"],\"articleSection\":[\"ExaCC\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/\",\"name\":\"dbaascli database move failing with ORA-01691 on ExaCC - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2025-07-28T15:59:16+00:00\",\"dateModified\":\"2025-07-28T15:59:19+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"dbaascli database move failing with ORA-01691 on ExaCC\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\",\"name\":\"Marc Wagner\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"caption\":\"Marc Wagner\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"dbaascli database move failing with ORA-01691 on ExaCC - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/","og_locale":"en_US","og_type":"article","og_title":"dbaascli database move failing with ORA-01691 on ExaCC","og_description":"I recently had to move a database from a 19.23 to a 19.26 dbhome on an ExaCC. This will include the database to be patched. The command dbaascli database move failed during the datapatch steps with following error: With this blog I would like to share my troubleshooting with you and how I resolved the […]","og_url":"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/","og_site_name":"dbi Blog","article_published_time":"2025-07-28T15:59:16+00:00","article_modified_time":"2025-07-28T15:59:19+00:00","author":"Marc Wagner","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Marc Wagner","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/"},"author":{"name":"Marc Wagner","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"headline":"dbaascli database move failing with ORA-01691 on ExaCC","datePublished":"2025-07-28T15:59:16+00:00","dateModified":"2025-07-28T15:59:19+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/"},"wordCount":494,"commentCount":0,"keywords":["dbaascli","exacc","patching"],"articleSection":["ExaCC","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/","url":"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/","name":"dbaascli database move failing with ORA-01691 on ExaCC - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2025-07-28T15:59:16+00:00","dateModified":"2025-07-28T15:59:19+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/dbaascli-database-move-failing-with-ora-01691-on-exacc\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"dbaascli database move failing with ORA-01691 on ExaCC"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628","name":"Marc Wagner","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","caption":"Marc Wagner"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/39701","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/48"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=39701"}],"version-history":[{"count":18,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/39701\/revisions"}],"predecessor-version":[{"id":39720,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/39701\/revisions\/39720"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=39701"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=39701"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=39701"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=39701"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}