Discussion
Cognizant
IN
Last activity: 6 Apr 2018 19:26 EDT
Generating Rules Schema Objects Stalled (migrate.sh)
We have upgraded our application in development environment from 6.2.1 to 7.1.9 after this; we cloned the rules schema from development and created a copy in QA environment (ORACLE + TOMCAT + UNIX setup) to peform a data only upgrade. Before we could perform the dataonly upgrade we ran the migrate.sh to "Generate rules schema objects" however this script stalled with the following error...
bash-4.1$ ./migrate.sh
Buildfile: .../migrateSystem.xml
Setup:
[pega:propertyparser] Reading Properties from : .../migrateSystem.properties
[mkdir] Created dir: .../MigrateTemp-25-October-YYYY-HH.MM.SS
[echo] Using temporary directory .../MigrateTemp-25-October-YYYY-HH.MM.SS
[unzip] Expanding: .../pega7/archives/pegadbinstall-classes.zip into .../pega7/migratesystem/MigrateTemp-25-October-YYYY-HH.MM.SS/load
[echo] Using logging configuration from: ./config/deploylogging.properties
[propertyfile] Creating new property file: .../pega7/migratesystem/MigrateTemp-25-October-YYYY-HH.MM.SS/prbootstrap.properties
[pega:checkforuncommittedhotfixes] Found Uncommitted hotfixes, please commit the following hotfixes before migrating:
[pega:checkforuncommittedhotfixes] HFIX-29421
BUILD FAILED
.../pega7/scripts/migrateSystem.xml:501: Migration cannot proceed due to uncommitted hotfixes.
Before cloning the rules schema from development we ensured that all hotfixes were commited including HFIX-29421 however this still occured.
Kindly help with your suggestions.
**Moderation Team has archived 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.
AIG
US
Please check below table in lifted Rule schema -
select * from pega.pr_data_products
where pystatus <> 'Committed'
If you have added HF to PRPC 6.2 which support to uncommited mode installer then execute same to old 6.2 schema as well and find HF number.
Search for " HFIX-29421" in table and remove entry; However prior this, plan to commit HF if there any with uncomitted in lifted Pega 7 instead of deletion option.
You may need to reimport HF post upgrade.
Cognizant
IN
We ran the following SQL to update the rows that were showing up as uncommitted.
update PegaRULES.pr_data_products set pystatus = 'Committed'
where pystatus = 'Uncommitted'
We re-ran the migrate.sh to "Generate rules schema objects" and it ran successfully.