pzpersistsysteminfo throwing exceptions in upgraded system
After update from Pega 7.1.8 to Pega 7.2, PegaRULES logs show exceptions in the log every night.
In systems upgraded to 7.2 (not seen in new 7.2 installations) there are exceptions being thrown when the agent runs the pzpersistsysteminfo activity each night. There are 47 exceptions like this:
2016-03-30 01:00:50,665 [ PegaRULES-Batch-2] [ STANDARD] [ ] [ PegaRULES:07.10] (nal.state.DatabaseTableHandler) ERROR - Database exception while retrieving the database table information for class History-AgentM-AgentMod-Work
com.pega.pegarules.pub.database.BadClassDefinitionException: Database-BadClassDef History-AgentM-AgentMod-Work
Steps to Reproduce
Run the pzpersistsysteminfo activity. This activity is being run by an agent during night hours.
A defect in Pegasystems’ code or rules. In Pega 7.1.8 some unneeded database table rules which do not map to a class were mistakenly included in the product.
Apply HFix-26964 and then run the PZDELETEJUNKDADTS activity.
The activity has an option(checkbox). If it is cleared then it does not delete but displays the list to the user and also are logged to the PegaRULES log file.
If the option is selected then the un-required rules are deleted from the database, and again are also logged to the PegaRULES log file.
0% found this useful