Question
Matlen Silver
US
Last activity: 1 Sep 2016 10:40 EDT
Report Definition Breakes due to lengh of data of CLOB colum
I have a report definition that breakes with this DB exception: ORA-24345: A Truncation or null fetch error occurred
I have discovered that it is due to one of the records has a large amount of data in one of the fields and cannot fetch this data. Is there a way I can limit the size of data I want to return in colum of a report definition. I have tried already a substring but did not work?
**Updated by Moderator: Vidyaranjan. Removed user added Ask the Expert tag. Apologies for confusion, shouldn't have been an end-user option***
Pegasystems
IN
Are you able to execute the same query directly against the database, outside of the Pega platform?
CLOB column type is not supported in Pega platform. To workaround, can probably write a SQL function which can CAST it to VARCHAR (2000) and see if that mitigates this issue.
PayPal
US
Thanks for replaying.
Query execution directly in the DB also throws the same exception. Issue seems to be with the pr_read_from_stream stored procedure which is the one that returns the pyNote column from the pzPVStream(BLOB) column from the pc_data_workattach table.
Also have found that this is a known issue documented here: https://community.pega.com/support/support-articles/error-while-running-report-definition-post-upgrade
I am not sure about the solution because of the impact to the existing data, it could cause conflicts during column population.
Pegasystems
IN
I am confused now. The header seemed to mention that you were retrieving the data from a CLOB column but this reply seems to mention that the property is unexposed and the stream reader functions (UDFs) are being used to get the data from the BLOB. Is there an issue with the CLOB or BLOB?
Also, the PDN link you have mentioned is correct and the enhancement will be available in a future release. For now, the suggested workaround in the support arcticle referenced by you should be used.