05-30-2025 03:33 AM
When trying to upgrade Cisco ISE, I must first complete the checks beforehand to do so.
The only error I get in this regard is with one specific node:
Running the command mentioned on the CLI of this node to see further details just gives me the below (these are the last entries, nothing exists after it):
Thu May 29 13:30:36 UTC 2025 : Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT Thu May 29 13:30:50 UTC 2025 : Job "CEPM"."SYS_IMPORT_SCHEMA_01" successfully completed at Thu May 29 13:30:48 2025 elapsed 0 00:03:24 Thu May 29 13:30:50 UTC 2025 : Thu May 29 13:30:50 UTC 2025 : Changing host config entry to standalone... Thu May 29 13:30:50 UTC 2025 : ORACLE_SID : cpm11 Thu May 29 13:30:50 UTC 2025 : NODECNT : Thu May 29 13:30:50 UTC 2025 : - Successful Thu May 29 13:30:50 UTC 2025 : - Successful Thu May 29 13:30:50 UTC 2025 : Thu May 29 13:30:50 UTC 2025 : runDBClone method finished executing Thu May 29 13:30:50 UTC 2025 : triggerUpgradeOnClonedInstance method started executing Thu May 29 13:30:52 UTC 2025 : Modifying upgrade scripts to run on cloned database Thu May 29 13:30:52 UTC 2025 : - Successful Thu May 29 13:31:30 UTC 2025 : Thu May 29 13:31:30 UTC 2025 : Running schema upgrade on cloned database Thu May 29 13:37:08 UTC 2025 : - Successful Thu May 29 13:37:08 UTC 2025 : Thu May 29 13:37:08 UTC 2025 : Running data upgrade on cloned database Thu May 29 13:37:48 UTC 2025 : - Failed Thu May 29 13:37:48 UTC 2025 : ConfigDBUpgrade : Performing Clean-up Thu May 29 13:38:10 UTC 2025 : copying back the scripts Thu May 29 13:38:10 UTC 2025 : removing the directory Thu May 29 13:38:10 UTC 2025 : ConfigDBUpgrade : Clean-up Completed
It seems like its the action of running the data on the cloned database that is failing, but I cant seem to find any information on this or how to fix it.
Anyone seen this before?
06-01-2025 10:08 AM
I would highly recommend working with TAC on this.
06-01-2025 10:42 PM
Hi @TariqMK ,
are you upgrading ISE from/to which version ?
Note 1: if you are upgrading from 3.1 to 3.4 (for example) try using URT in CLI to verify this issue:
ise-urtbundle-3.4.0.608-1.0.0.SPA.x86_64.tar.gz
Note 2: please take a look at: Mastering ISE Upgrades - Best Practices, Tips and Tricks., pay special attention to Run the URT.
Hope this helps !!!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide