Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Hari Radhakrishnan (HariR246) ANZ
ANZ
AU
HariR246 Member since 2020 6 posts
ANZ
Posted: Sep 6, 2021
Last activity: Aug 7, 2023
Posted: 6 Sep 2021 0:08 EDT
Last activity: 7 Aug 2023 10:33 EDT
Closed
Solved

Platform 8.6.1 upgrade - ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion

Hi All,

After the upgrade of PegaCRM 8.5.1 to Pega Platform 8.6.1, we are seeing these errors in the logs. The PegaCRM framework is not yet upgraded to 8.6.1. We saw that there were hot fixes in PEGA7.x for this error. Is there any change (Hotfix or DSS or otherwise) required for Pega 8.6.1?

 

Caused by: com.pega.pegarules.pub.database.DatabaseException: There was a problem getting a list: code: 22835 SQLState: 99999 Message: ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: 393746, maximum: 4000

Thanks, Hari

***Edited by Moderator: Pooja Gadige to add platform capability tag***
***Edited by Moderator Marissa to update Support Case Details***
To see attachments, please log in.
Pega Platform 8.6.1 Case Management Updates Financial Services System/Cloud Ops Administrator Support Case Created

Accepted Solution

Posted: 3 years ago
Posted: 24 Sep 2021 12:57 EDT
Marissa Rogers (MarissaRogers) MOD Principal Knowledge Management Specialist
Pegasystems Inc.
US

Upon reviewing the associated Support Case, the resolution was discovered as follows: Add below DSS: Pega-RULES. reporting/retrieveFullClobContent , Set the value to true. Review below link for Pega0039 alert. https://community.pega.com/sites/default/files/help_v62/howto/howto2/howtopega0039.htm

To see attachments, please log in.
Posted: 3 years ago
Posted: 9 Sep 2021 3:55 EDT
Gowrishankar Ramasamy (GowrishankarR29) Citicorp Services India Private Limited
Citicorp Services India Private Limited
IN

Hi @HariR246,

            I assume the platform has been upgraded to 8.6.1. I believe the upgrade went successful. Now the stack is with PegaCRM 8.5.1 + Pega Platform 8.6.1. 

           Please confirm whether my assumption is correct. Now the application is running successfully with the exceptions in logs. Could you please provide more details on how often these exceptions are captured in logs? The exceptions occur only when certain actions are performed in application?

           Could you please share log file /  complete stack trace to investigate ?

Thanks,

To see attachments, please log in.
Posted: 3 years ago
Posted: 9 Sep 2021 16:38 EDT
Hari Radhakrishnan (HariR246) ANZ
ANZ
AU

@GOWRISHANKAR Yes, the upgrades were successful. Application is currently on PegaCRM 8.5.1 + Pega Platform 8.6.1, as you rightly surmised. We hit another roadblock with the PegaCRM upgrade, hence we are still on this setup.

I will provide the logs via an Incident; it's probably easier to track that way. I thought it might be a known issue, hence posted here.

Thanks,

To see attachments, please log in.
Posted: 3 years ago
Posted: 14 Sep 2021 6:08 EDT
Gowrishankar Ramasamy (GowrishankarR29) Citicorp Services India Private Limited
Citicorp Services India Private Limited
IN

Hi @HariR246,

           Please update the solution once the incident is resolved. The solution will help others who face similar issue.

Thanks,

To see attachments, please log in.
Posted: 2 years ago
Posted: 2 Dec 2021 13:30 EST
Chandra Sekhar Bhagath Vasireddy (Bhagath_Vasireddy) Cognizant Chandra Sekhar Bhagath Vasireddy
Cognizant
IN

@VINAYVOSURI

this issue is product bug for api class #NativeSQLAPIResolver.class ; Request for back port hot fix #HFIX-81831 of PRPC8.6.2 to resolve this product bug

Regards

Bhagath

Certified J2EE Architect / Pega CLSA

AI/ML expertise @ IIIT-H

To see attachments, please log in.

Accepted Solution

Posted: 3 years ago
Posted: 24 Sep 2021 12:57 EDT
Marissa Rogers (MarissaRogers) MOD Principal Knowledge Management Specialist
Pegasystems Inc.
US

Upon reviewing the associated Support Case, the resolution was discovered as follows: Add below DSS: Pega-RULES. reporting/retrieveFullClobContent , Set the value to true. Review below link for Pega0039 alert. https://community.pega.com/sites/default/files/help_v62/howto/howto2/howtopega0039.htm

To see attachments, please log in.
  • Anderson Medeiros Gomes Adriano Viana Bastos

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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