Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Error when migrating from Pega 7.3.1 to Pega 7.4

SA-68830

Summary



Error occurs when migrating Pega 7.3.1 to Pega 7.4.


Error Messages



     [java] (INFO): Table PR_DATA_ADMIN entered to process - not found on database.      [java] (INFO): Encountered exception during processing!
     [java] Invalid Tables entered for include Processing
     [java]     at com.pega.pegarules.util.deploy.PegaBulkMover.process(PegaBulkMover.java:599)
     [java]     at com.pega.pegarules.util.deploy.PegaBulkMover.main(PegaBulkMover.java:343)
     [java]
     [java] PegaBulkMover:: Exception SQL error trying to obtain Tables from Database Schema name.
     [java]     at com.pega.pegarules.util.deploy.PegaBulkMover.process(PegaBulkMover.java:647)
     [java]     at com.pega.pegarules.util.deploy.PegaBulkMover.main(PegaBulkMover.java:343)
     [java]
     [java] 
     [java] Ending Time: 
     [java] 
     [java] Elapsed Time: 0 minute(s), 0 second(s).
     [java] Exception in thread "main" java.lang.RuntimeException: PegaBulkMover:: Exception SQL error trying to obtain Tables from Database Schema name.
     [java]     at com.pega.pegarules.util.deploy.PegaBulkMover.process(PegaBulkMover.java:647)
     [java]     at com.pega.pegarules.util.deploy.PegaBulkMover.main(PegaBulkMover.java:343)
     [java] Caused by: java.lang.Exception: Invalid Tables entered for include Processing
     [java]     at com.pega.pegarules.util.deploy.PegaBulkMover.process(PegaBulkMover.java:599)
     [java]     ... 1 more

BUILD FAILED
/opt/tomcat/pega_7.4_update/scripts/migrateSystem.xml:644: The following error occurred while executing this line:
/opt/tomcat/pega_7.4_update/scripts/migrateSystem.xml:39: Java returned: 1



Steps to Reproduce



Run migrate.sh.


Root Cause



A software use or operation error.
In the migrateSystem.properties file, the source data schema name was not specified. Hence, the script assumed that this was a single schema and searched for the pr_data_admin table in the pega_rules schema and could not find it there.



Resolution



Perform the following local-change:

Modify the below,

pega.source.data.schema=

to 

pega.source.data.schema=yourSourceDataSchemaName

 
Suggest Edit

Published January 4, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us