PegaRULES initialization failed after restart
SummaryPegaRULES initialization failed after restart of the application on the weblogic server and shows errors in log files.
Error Messages2016-07-19 10:15:57,226 [abc.xyz.net] [ STANDARD] [ ] [ ] (ternal.vtable.VirtualTableImpl) INFO - ...Finished. Preloaded 21.2MB for 89318 rules in 12101 ms
2016-07-19 10:15:57,255 [abc.xyz.net] [ STANDARD] [ ] [ ] (artup.SearchInitializationTask) INFO - Starting configuration of node for full-text search.
2016-07-19 10:15:58,686 [abc.xyz.net] [ STANDARD] [ ] [ ] ( internal.mgmt.PREnvironment) ERROR - com.pega.pegarules.pub.PRRuntimeException: Method Invocation exception
2016-07-19 10:15:58,716 [abc.xyz.net] [ STANDARD] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: eqds3abc.xyz.net
com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed
Steps to ReproduceStart the application after upgrade.
Root CauseUser has pzTenantID in pr_data_admin_product table. This column is there despite it is non-Multi Tenant system. But as this should be there only for Multi Tenant system. This is breaking the flow and engine is not starting.
Actually additional scripts from pega 7.2 onwards Multi Tenant related sql scripts is included... previous version of pega dont have that script. post upgrade as we have to run the additional scripts , even Multi Tenant related script was executed. Hence those column were created.
ResolutionRan below scripts on pr_data_admin_product table.
ALTER TABLE PR_DATA_ADMIN_PRODUCT DROP CONSTRAINT PR_DATA_ADMIN_PRODUCT_PK CASCADE;
ALTER TABLE PR_DATA_ADMIN_PRODUCT DROP COLUMN pzTenantId;
ALTER TABLE PR_DATA_ADMIN_PRODUCT ADD CONSTRAINT PR_DATA_ADMIN_PRODUCT_PK PRIMARY KEY (pzInsKey);This made the system to be up again.
Published August 31, 2016 - Updated September 9, 2016