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

NullPointerException on running report from specific category

SA-66946

Summary



NullPointerException occurs when running a report from a specific category.


Error Messages



[ajp-bio-8009-exec-3] [TABTHREAD2] [AP:01.20.01] (rd.resolve.SqlReportResolver) ERROR your_domain_name.com|IP Address  - An error occurred during resolving the report definition - null
java.lang.NullPointerException
at com.pega.pegarules.priv.database.sqlgen.constants.ColumnType.enumOf(ColumnType.java:112)
at com.pega.pegarules.data.internal.rd.reference.GenericPropertyReferenceResolver.resolve(GenericPropertyReferenceResolver.java:186)
at com.pega.pegarules.data.internal.rd.resolve.AbstractFieldResolver.resolveField(AbstractFieldResolver.java:88)
at com.pega.pegarules.data.internal.rd.resolve.AbstractFieldResolver.resolveFields(AbstractFieldResolver.java:62)
at com.pega.pegarules.data.internal.rd.resolve.AbstractFieldResolver.resolveFields(AbstractFieldResolver.java:54)
at com.pega.pegarules.data.internal.rd.resolve.ListResolver.resolve(ListResolver.java:56)
at com.pega.pegarules.data.internal.rd.resolve.SqlReportResolver.resolve(SqlReportResolver.java:62)
at com.pega.pegarules.data.internal.rd.resolve.SqlReportResolver.resolve(SqlReportResolver.java:37)
at com.pega.pegarules.data.internal.rd.SQLExecutorResultsCP.resolve(SQLExecutorResultsCP.java:66)
at com.pega.pegarules.data.internal.rd.SqlReportExecutor.executeSubReport(SqlReportExecutor.java:124)
at com.pega.pegarules.data.internal.rd.SqlReportExecutor.execute(SqlReportExecutor.java:71)
at com.pega.pegarules.data.internal.rd.SqlReportExecutor.execute(SqlReportExecutor.java:46)
at com.pega.pegarules.data.internal.rd.resolve.SubReportResolver.executeSubReport(SubReportResolver.java:220)
at com.pega.pegarules.data.internal.rd.resolve.SubReportResolver.processSubReports(SubReportResolver.java:123)
at com.pega.pegarules.data.internal.rd.resolve.SubReportResolver.resolve(SubReportResolver.java:71)
at com.pega.pegarules.data.internal.rd.resolve.SqlReportResolver.resolve(SqlReportResolver.java:62)
at com.pega.pegarules.data.internal.rd.resolve.SqlReportResolver.resolve(SqlReportResolver.java:37)
at com.pega.pegarules.data.internal.rd.SQLExecutorResultsCP.resolve(SQLExecutorResultsCP.java:66)
at com.pega.pegarules.data.internal.rd.SqlReportExecutor.executeMainReport(SqlReportExecutor.java:94)
at com.pega.pegarules.data.internal.rd.SqlReportExecutor.execute(SqlReportExecutor.java:73)
at com.pega.pegarules.data.internal.rd.SqlReportExecutor.execute(SqlReportExecutor.java:46)
at com.pega.pegarules.data.internal.PRDataProviderImpl.executeReport(PRDataProviderImpl.java:1277)
at com.pega.pegarules.session.internal.mgmt.Executable.executeReport(Executable.java:10977)
at com.pegarules.generated.definition.ra_action_dhhsscpendinginvoicevalidation_a10d1a58ec3f8bd26672e1ef3c2138b5.perform(ra_action_dhhsscpendinginvoicevalidation_a10d1a58ec3f8bd26672e1ef3c2138b5.java:52)



Steps to Reproduce



Open and run any report from a specific category.


Root Cause



The issue occurred for all the reports which used the sub report. The sub report used a declare index (Index-class-Data-classname) which was missing a column in the pr_index table. The property was created as part of a recent deployment and the column was not created.


Resolution



Perform the below local change:
  1. Create the column manually in the pr_index table.
  2. Run the column population job for this column.

Published December 1, 2018 - Updated October 8, 2020

Was this useful?

100% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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