Jaspersoft unable to get to next record


Article ID: 39004


Updated On:


Clarity PPM On Premise



When trying to run a report in Development environment, get an error: 

Error Details: 
Unable to get next record. 
com.jaspersoft.jasperserver.api.JSExceptionWrapper: net.sf.jasperreports.engine.JRException: unable to get next record 
Alternatively, we might also see the following symptom:
We got this error while trying to run the Load Data Warehouse Access Rights job.  
We are able to run the 'Load Data Warehouse' job successfully.  
Please look at it and see what may be the issue. Following code is taken from bg-dwh.log. 
DBA says there is nothing wrong with the TEMP tablespace. 
It seems the underlying view, DWH_INV_SECURITY_V has a troublesome NOT IN clause. But this view is built-in and we have no desire to modify. 
2015/10/05 08:23:45 - IS ORCL? - [CA Clarity][Oracle JDBC Driver][Oracle]ORA-01652: unable to extend temp segment by 128 in tablespace TEMP 
2015/10/05 08:23:45 - IS ORCL? - ORA-02063: preceding line from PPMDBLINK_2 
2015/10/05 08:23:45 - IS ORCL? - ORA-06512: at "PPM_DWH_2.DWH_INV_SECURITY_PRC", line 39 


Caused by CLRT-79077

This is caused when there is a very large dataset with many Security Groups and OBS Access Rights configured.  


Resolved in CA PPM 14.3 Generic Patch #5   

Additional Information: 

Reference TEC1696455 : PPM 14.3 Generic Patch available to resolve reported issues  



Release: ESPCLA99000-14.2-Clarity-Extended Support Plus