Support Article
Issue restarting tomcat instance post upgrade to split-schema
SA-9813
Summary
With the out-of-the-box (OOTB) upgrade (using setupDatabase.properties) of Pega 7.1.7, the DBA user does not have access to specific RULES tables.
This results in error in log files while logging in using any operator.
The upgrade is from a single to a split-schema configuration.
All migration scripts executes correctly without any errors. The error occurs after the migration and restarting the Tomcat instance.
Error Messages
2015-04-02 07:35:14,164 [http-bio-8080-exec-9] [TABTHREAD0] [ ] [ PlosFW:01.01.01] ( internal.access.DatabaseImpl) ERROR |[email protected] - Encountered problem when performing a Commit
com.pega.pegarules.pub.database.DatabaseException: ORA-01031: insufficient privileges
From: (HA1D0D0D8C52485AAD4D26C217E68526F:xxx.xxx.xx.x)
SQL: MERGE INTO PEGA717MIGRATIONRULES.pr_sys_rule_impl t USING (SELECT ? "pzInsKey" , sysdate"pxCommitDateTime" , ? "pxInsName" , ? "pxObjClass" , ? "pxUpdateDateTime" , ? "pzAspect" , ? "pzclass" , ? "pzpackage" , ? "pzpreload" , ? "pzRuleInsKey" , ? "pzChecksum" FROM dual) inputs ON (t.pzInsKey = inputs."pzInsKey") WHEN MATCHED THEN UPDATE SET PXINSNAME = inputs."pxInsName" , PXOBJCLASS = inputs."pxObjClass" , PXUPDATEDATETIME = inputs."pxUpdateDateTime" , PZASPECT = inputs."pzAspect" , PZCLASS = inputs."pzclass" , PZPACKAGE = inputs."pzpackage" , PZPRELOAD = inputs."pzpreload" , PZRULEINSKEY = inputs."pzRuleInsKey" , pxCommitDateTime = sysdate , pzChecksum = inputs."pzChecksum" WHEN NOT MATCHED THEN INSERT (pzInsKey , pxCommitDateTime , PXINSNAME , PXOBJCLASS , PXUPDATEDATETIME , PZASPECT , PZCLASS , PZPACKAGE , PZPRELOAD , PZRULEINSKEY , pzChecksum) VALUES (inputs."pzInsKey" , sysdate , inputs."pxInsName" , inputs."pxObjClass" , inputs."pxUpdateDateTime" , inputs."pzAspect" , inputs."pzclass" , inputs."pzpackage" , inputs."pzpreload" , inputs."pzRuleInsKey" , inputs."pzChecksum")
Caused by SQL Problems.
Problem #1, SQLState 42000, Error code 1031: java.sql.BatchUpdateException: ORA-01031: insufficient privileges
Steps to Reproduce
Install PRPC 6.2 SP1 and use upgrade scripts to migrate to Pega 7.1.7 to have split schema for database.
Root Cause
The root cause of this problem is an error/omission in product documentation.
In the UpgradeGuide, Upgrading from a Single to Split Schema>Upgrading with one database>Generate rules schema objects section it explains to keep the same values for the source and target destinations.
Instead it must advice to set the target data schema, while upgrading with two databases.
Configure the target data schema.
pega.target.data.schema=Data Schema
Make sure the target data schema is set, otherwise the Rules schema is used by default.
Resolution
This issue is scheduled to be resolved in update release Pega 7.1.8
Addtional Note: To resolved the problem on existing migrated system run the migrate script again after setting both the target rules and data schemas and then just the rules.objects properties to true.
pega.target.rules.schema= %your_rule_schemas%
pega.target.data.schema= %your_data_schemas%
pega.move.admin.table=false
pega.clone.generate.xml=false
pega.clone.create.ddl=false
pega.clone.apply.ddl=false
pega.bulkmover.unload.db=false
pega.bulkmover.load.db=false
pega.rules.objects.generate=true
pega.rules.objects.apply=true
A doc bug has been raised with number BUG-175254 and documentation issue is resolved for Pega 7.1.8 release.
Published August 7, 2015 - 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.