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

Report Definition code: 29532 SQLState: 99999 Message: ORA-29532



A Report Definition with properties.not optimized that worked previously now throws an error message. 
However, the Report Definition works as expected when two of the referenced properties are removed. 

Error Messages

** An error occurred on executing the query for the report definition - There was a problem getting a list: code: 29532 SQLState: 99999 Message: ORA-29532: Java call terminated by uncaught Java exception: java.lang.ArrayIndexOutOfBoundsException" 

Steps to Reproduce

Execute any Report Definition with  properties not optimized.

Root Cause

An issue in the custom application code or rules 
A corrupt user-defined function (UDF) affected UDF installation.

The Pega Platform uses UDFs for its reporting capabilities.

Use the following query to test whether the UDFs are correctly installed : 

select pr_read_from_stream('pzInsKey', 'pzInsKey',pzPVStream) as "StringValue",
pr_read_int_from_stream('pzRuleSetVersionMajor', 'pzInsKey',pzPVStream) as "IntegerValue",
pr_read_decimal_from_stream('pzRuleSetVersionMinor', 'pzInsKey', pzPVStream) as "DecimalValue" 
from pr4_rule where rownum<5;

In this case, pr_read_from_stream has a problem because the following query, when run, shows the ArrayIndexOutOfBounds exception coming from pr_read_from_stream. This is the same error that was thrown in PRPC.

select pr_read_from_stream('pzInsKey', 'pzInsKey',pzPVStream) as StringValue from rules.pr4_rule where pxinsname='@BASECLASS!ALLFLOWS';

There is another condition that causes the same issue to occur: An attempt is made to execute a method in a Java class that has not been previously compiled or resolved.

Use the following query to check for this second condition:

select * from user_objects where object_type='JAVA CLASS'; 

(Some of the classes might show as invalid according to the database; ignore these items.)

However, this second conditions did not exist for the case reported for this article: All the classes were valid, and the issue was only with the pr_read_from_stream.


Perform the following local-change when either of the root cause conditions exist:
Reinstall the UDF.

Published January 31, 2016 - 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