Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Database-BadClassDef exception in SystemOut.log file



"Database-BadClassDef" errors when starting Pega Marketing Server.

Error Messages

[10/14/16 22:30:12:471 EET] 0000009a SystemOut O 2016-10-14 22:30:12,471 [ x] [ STANDARD] [ ] (res.CacheDataToCandidateMapper) WARN - Unable to load RULE-OBJ-MODEL XXXX-DECISIONRESULT PYDEFAULT #20160628T142559.479 GMT due to Database-BadClassDef XXX-DecisionResult; This may cause the wrong rule to run during rule execution.

Steps to Reproduce

Not applicable

Root Cause

The rule RULE-OBJ-MODEL.pydefault was found to have been defined against a non-existent Class.
(The 'applies to' property was set to " XXXX-DECISIONRESULT" – this class had previously been deleted).


Perform the following local-change:
  1. Recreate the "XXXX-DECISIONRESULT" Class.
  2. Delete the 'pyDefault' rule.
  3. Delete the "XXXX-DECISIONRESULT" Class.
Suggest Edit

Published August 23, 2017 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us