Support Article
Data-Admin-Requestor "MY_SYSTEM!BATCH" not found after upgrade
SA-9896
Summary
System start fails after upgrade from single schema to split schema environment.
Error Messages
Error on startup:
( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server:
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
…
Caused by:
com.pega.pegarules.pub.context.PRSecurityException: Unable to construct authorization core due to authorization failure
at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(SessionAuthorization.java:245)
at com.pega.pegarules.session.internal.mgmt.PRRequestorBase.allocateSessionAuthorization(PRRequestorBase.java:537)
at com.pega.pegarules.session.internal.mgmt.PRRequestorImpl.allocateSessionAuthorization(PRRequestorImpl.java:2009)
…
Caused by:
com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "MY_SYSTEM!BATCH" not found
From: (B8729CA8C208C9E5E4D6907C38B22AF79)
Steps to Reproduce
1. Upgrade to split schema by creating two new empty schemas.
2. Use the migrate script to migrate rules to new rules schema and data to new data schema and than upgrade each of them respectively.
3. Start the system to observe the error.
Root Cause
The root cause of this problem is software use/operation error. The migrate script does not migrate data tables to a new schema. The existing combined data/rules schema that you are upgrading from will become the new data schema in the upgraded environment.
Resolution
This issue is resolved by making the following change to the operating environment:
If a new rel_71 data schema is required, then use database tools to copy the original schema to this new schema before the upgrade.
Published June 12, 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.