Support Article
Update.sh is failing during Rule Update with Split Schema
SA-24083
Summary
User performed Out of place Update from Pega 7.1.8 to 7.2 using the documentation provided in PDN.
Current Rules schema: RULES
Current Data Schema : DATA
New Rules schema on same DB: RULESNEW
Executed update.sh after running the migrate.sh script but the build failed with below error.
Error Messages
Warn - NonVersionedJdbcJarReader - unable to load classes from the database: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=RULESNEW.PR_ASSEMBLEDC
LASSES, DRIVER=3.62.56
[java] May 27, 2016 5:23:45 AM com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl
[java] 19830421: PegaRULES classes will be loaded from jar files (and NOT the database)
[java] May 27, 2016 5:23:45 AM com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl
[java] SEVERE: Error initializing PRAppLoader
[java] java.lang.ClassNotFoundException: com.pega.pegarules.bootstrap.loader.PRAppLoader
Steps to Reproduce
1. Perform migrate.sh with source rules and data schema pointed to currrent schmeas. Target rules schema pointed to new schema. Migrate.sh executed successfully.
2. Update setupdatabase.prop file with both rule and data schema as new schema and then execute update.sh.
Root Cause
A defect or configuration issue in the operating environment. setupdatabase.prop is having following parameters which is stopping to create tables.
bypass.pega.schema=true
bypass.udf.generation=true
Resolution
Perform the following local-change:
Update following properties:
bypass.pega.schema=false
bypass.udf.generation=false
Published June 9, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.