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

General
, , , ,
1

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

2

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,

3

@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,

4

Hi @HariR246,

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

Thanks,

5

@GOWRISHANKAR is there a solution for this error ? We are facing same error when upgrading our app from 8.3.1 to 8.6.1

6

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.

7

@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