Posted: 3 Jun 2015 16:16 EDT Last activity: 17 Jul 2017 16:38 EDT
issue in Upgrade 7.1.8
I'm upgrading from 6.3 to 7.1.8. I ran first 2 steps migrate and upgrade script. Now when I run the migrate script for the second time to generate the rules schema object , I'm getting the below error.
[pegaropertyparser] Reading Properties from : /DBA01/RSM_WORKERDONOTDELETE/scripts/migrateSystem.properties
[mkdir] Created dir: /DBA01/RSM_WORKERDONOTDELETE/Temp/MigrateTemp-03-June-2015-14.50.07
[echo] Using temporary directory /DBA01/RSM_WORKERDONOTDELETE/Temp/MigrateTemp-03-June-2015-14.50.07
[unzip] Expanding: /DBA01/RSM_WORKERDONOTDELETE/archives/pegadbinstall-classes.zip into /DBA01/RSM_WORKERDONOTDELETE/Temp/MigrateTemp-03-June-2015-14.50.07/load
[echo] Using logging configuration from: ./config/deploylogging.properties [propertyfile] Creating new property file: /DBA01/RSM_WORKERDONOTDELETE/Temp/MigrateTemp-03-June-2015-14.50.07/prbootstrap.properties [pega:checkforuncommittedhotfixes] Found Uncommitted hotfixes, please commit the following hotfixes before migrating: [pega:checkforuncommittedhotfixes] HFIX-8246 [pega:checkforuncommittedhotfixes] HFIX-7535 [pega:checkforuncommittedhotfixes] HFIX-9161
/DBA01/RSM_WORKERDONOTDELETE/scripts/migrateSystem.xml:501: Migration cannot proceed due to uncommitted hotfixes.
It says we have uncommited hotfix , is there a way that i can force the script to run ?
***Updated by moderator: Marissa to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
I have already upgraded the rule base schema , now I cannot login and commit it. is there a way to force run the script ? while we upgraded to 7.1.7 we faced a similar issue while running the upgrade script. then we ran ./update.sh --force and the script ran fine. so i tried running ./migrate.sh --force but it did not work.
What happens when you try to log in now ? Just wondering whether that's the aspect of the issue we should be focusing on first ? (That is: if we can get the login to work [if that is the right course of action], then we can commit the HFIXes ?)
I'm trying to determine if a bug should be raised for the upgrade scripts to stop you from proceeding with the upgrade sooner in the process if hotfixes are installed but not committed. Did you need to restore your database, or were you able to recycle the servers and log in after the first run of the migrate and upgrade script? (I would think at this point you'd have had to restore the database, but I'd just like to verify before entering the bug)
No, After recycle I was able to login to 6.3 and commit the hot fix. We completed migrating the rules to new schema and upgraded it at this point the old schema which had 6.3 rules and hotfix was not touched. So I was able to login and commit the hotfix and proceed with the migration.