Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Smriti Parmar (SmritiP9)
Larsen & Toubro Infotech

Larsen & Toubro Infotech
IN
SmritiP9 Member since 2016 3 posts
Larsen & Toubro Infotech
Posted: Sep 2, 2016
Last activity: Apr 6, 2018
Posted: 2 Sep 2016 5:05 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed
Solved

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://community.pega.com/support/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

Show More

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://community.pega.com/support/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.


Show Less
To see attachments, please log in.
Updates

Posted: 8 years ago
Posted: 2 Sep 2016 6:26 EDT
Sandeep Ghosh (Sandeep_Ghosh)
Scotiabank
Lead System Architect
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

 

To see attachments, please log in.
Posted: 8 years ago
Posted: 2 Sep 2016 6:56 EDT
Smriti Parmar (SmritiP9)
Larsen & Toubro Infotech

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.

To see attachments, please log in.
Posted: 8 years ago
Posted: 2 Sep 2016 11:01 EDT
Smriti Parmar (SmritiP9)
Larsen & Toubro Infotech

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?

To see attachments, please log in.
Posted: 8 years ago
Posted: 2 Sep 2016 12:03 EDT
Sandeep Ghosh (Sandeep_Ghosh)
Scotiabank
Lead System Architect
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

To see attachments, please log in.
Posted: 7 years ago
Posted: 27 Jan 2017 3:29 EST
Abhishek Pattnaik (AbhishekP7879)
Cognizant

Cognizant
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

 

 

 

 

To see attachments, please log in.
Posted: 8 years ago
Posted: 5 Sep 2016 3:07 EDT
Smriti Parmar (SmritiP9)
Larsen & Toubro Infotech

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

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice