Report failure referencing "Did not find report result for {paginated: false, maxPageHeight: null, maxPageWidth: null}"

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

One report is failing in Clarity PPM Advanced Reporting and Reports and Jobs. When running in Advanced Reporting with no parameters selected, an error referencing: 

Did not find report result for {paginated: false, maxPageHeight: null, maxPageWidth: null}

When running from Reports and Jobs, an error in the app-ca.logs references: 

Caused by: java.sql.SQLException: ORA-01489: result of string concatenation is too long 

Caused by: Error : 1489, Position : 9851, Sql = SELECT TO_CHAR(SYSDATE,'YY-MM-DD HH:mi:ss') RUN_DATE

Excerpt of error from logs when reproduced in Advanced Reporting: 

com.jaspersoft.jasperserver.api.JSException: Error filling report

Arguments:  at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.EngineServiceImpl$FillResultListener.reportFillError(EngineServiceImpl.java:1336)

Caused by: net.sf.jasperreports.engine.JRException: Unable to get next record.

Caused by: net.sf.jasperreports.engine.JRException: Unable to get next record from result set.

 at net.sf.jasperreports.engine.JRResultSetDataSource.next(JRResultSetDataSource.java:170)

Caused by: java.sql.SQLRecoverableException: Closed Connection: next

org.quartz.JobExecutionException: Did not find report result for {paginated: false, maxPageHeight: null, maxPageWidth: null}

Environment

Release : 15.6.1

Component : CA PPM SAAS JASPERSOFT

Resolution

If this is a custom report, check to see if this related to an issue with the design of the report. Listagg is one function that can cause issues, so if this is in the report query, one test would be to replace this function and see if the report then runs. (see external article:  http://www.dba-oracle.com/t_ora_01489_listagg.htm)