Posted: 4 Jun 2015 9:03 EDT Last activity: 6 Apr 2018 19:26 EDT
Rule Migration failed with parsing error during Pega7 upgrade
We are performing an upgrade to Pega7, but it failed during the Rule Migration.
The error thrown by the script is pasted here below, do we have a workaround to proceed further.
[java] The generated sql is incomplete
[java] java.lang.Exception: Generated DDL cannot be applied automatically due to parsing errors.
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.generateCloneDDL(SchemaGenerator.java:652)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.main(SchemaGenerator.java:1292)
[java] ERROR: The table pr_index_circumstance_def was ignored because the following column(s) were not recognized: FromKPI: bit, CATabbedNavigation: bit, CreatedInSendMailer: bit, IsPostACA: bit
[java] Error generating ddl for mssql, dbo
[java] Generated DDL cannot be applied automatically due to parsing errors.
F:\114716_Pega717\scripts\migrateSystem.xml:478: The following error occurred while executing this line:
F:\114716_Pega717\scripts\setupDDL.xml:272: Java returned: 1
**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.
In this case, Bit is sql ever specific data type. Prddl does not support it. But in general all the data types are supported by Pega except the db specific native data types. In such case the migration will fail and we need to analyze on the equivalent data type which is available as there should not be any data loss.