Generating Rule schema objects migrate.sh failing from 5.5 to 7.1.9
HI,
We are upgrading from pega5.5 to pega 7.1.9 , our migration and rule upgrade got completed successfully. Now when we are running migrate scripts to generate rule schema objects we are getting below error. We have given target schema as new pega7 rules schema in migratesystem.property file (as per Pega Upgrade guide). But one of the pdn link suugests to give target as old schema and source schema name as your new rule schema. Please advise.
https://pdn.pega.com/support-articles/error-while-generating-rules-schema-objects
BUILD FAILED
/opt/wassource/WAS_DUMP/PEGA-EAR/scripts/migrateSystem.xml:501: java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name
HI,
We are upgrading from pega5.5 to pega 7.1.9 , our migration and rule upgrade got completed successfully. Now when we are running migrate scripts to generate rule schema objects we are getting below error. We have given target schema as new pega7 rules schema in migratesystem.property file (as per Pega Upgrade guide). But one of the pdn link suugests to give target as old schema and source schema name as your new rule schema. Please advise.
https://pdn.pega.com/support-articles/error-while-generating-rules-schema-objects
BUILD FAILED
/opt/wassource/WAS_DUMP/PEGA-EAR/scripts/migrateSystem.xml:501: java.sql.SQLSyntaxErrorException: ORA-00903: invalid table name
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)
at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:873)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1167)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1289)
at oracle.jdbc.driver.OracleStatement.executeQuery(OracleStatement.java:1491)
at oracle.jdbc.driver.OracleStatementWrapper.executeQuery(OracleStatementWrapper.java:406)
at com.pega.pegarules.util.anttasks.CheckForUncommittedHotfixes.execute(CheckForUncommittedHotfixes.java:43)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.taskdefs.Sequential.execute(Sequential.java:68)
at net.sf.antcontrib.logic.IfTask.execute(IfTask.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:154)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:292)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:435)
at org.apache.tools.ant.Target.performTasks(Target.java:456)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
at org.apache.tools.ant.Main.runBuild(Main.java:851)
at org.apache.tools.ant.Main.startAnt(Main.java:235)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
**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.
Scotiabank
CA
For your 2nd migrate (3rd script during upgrade)
Source rule schema = upgraded rule schema
target rule schema = upgraded rule schema
source data schema = <blank>
target data schema = Old pega 5.x schema
I hope it clarifies, Please re-run and let us know the result.
Regards,
Sandeep
Larsen & Toubro Infotech
IN
HI , thanks that means running with target rule schema as old pega5 schema and source rule schema as pega 7 schema is not correct approach.
Accepted Solution
Scotiabank
CA
yes, you are right. Please re-run it with the configuration I have said and let us know the result.
Regards,
Sandeep
Larsen & Toubro Infotech
IN
thanks it worked. So now post that we are doing Data only upgrade. As per upgrade guide 'When upgrading from any release prior to PRPC 6.2, you must run additional scripts to update the ruleset columns.1. Navigate to ResourceKit\AdditionalUpgradeScripts and locate the scripts for your database:
l <database>_rulesetversion_columns_data.sql
l <database>_rulesetversion_columns_rule.sql scripts'.
Do we need to run those scripts too after data upgrade from PEGA 5.5 to PEGA 7.1.9?
Scotiabank
CA
You should run the scripts as you are upgrading from Pega 5.5.
If you closely inspect the SQLs you find that it only adds a column for ruleset version (as far as I remmember), so there is no harm in running those scripts.
Regards,
Sandeep
JP Morgan & Chase Co.
IN
Hi Sandeep,
Pega 7.2 user guide says other way round for the 3rd script :
pega.target.data.schema=original data schema
pega.target.rules.schema=new rules schema
pega.source.rules.schema=original rules schema
And if I understand correctly original rules schema should be the old schema. Could you please share your thoughts because we facing the same issue with upgrade from 6.2 sp2 to 7.2.
Regards
Larsen & Toubro Infotech
IN
HI After generating schema objects.. we run upgrade .sh script with data only parameter in my old 5.5 schema for Data upgrade. But it stopped updating logs after 6 min and the scripts were still ruinning build didnt failed nethier success. no updation in logs but sscripts were running till 2 hours with out any changes. Pls advise