E-IH: Interaction Hub Content Management's Maintain Content Component Error During Checkout

(Doc ID 2280618.1)

Last updated on JUNE 27, 2017

Applies to:

PeopleSoft Enterprise PRTL Interaction Hub - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

Environment:
---------------
Interaction Hub 9.1 ,Portal Bundle # 5 Multi language enabled
Production Instance.
ISSUE:
----------
When using a CFR language browser or any non-English, when user tries to check out a content that has large content they get the SQL error.



ERROR
-----------------------
A fatal PeopleCode SQL error occurred. Please consult your system log for details.

Erreur SQL dans Exec. (2,280) EPPCM_CM.CategoryTypeHandler.Workgroups.OnExecute Name:processHTMLLang PCPC:261079 Statement:3817
Called from:EPPCM_CM.CategoryTypeHandler.Workgroups.OnExecute Name:saveContent Statement:1371
Called from:EPPCM_CNT_WRK.FUNCLIB_01.FieldFormula Name:SaveContAPI Statement:212
Called from:EPPCM_DEFN_CONT.GBL.SavePostChange Statement:1

Au cours de l'exécution d'instructions SQL, une erreur s'est produite dans le sous-programme Exec. Le message précédent devrait avoir présenté les instructions SQL exécutées.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Login with a CFR browser and navigate to Interaction Hub Content Management> Maintain Content
2 Checout any content with more than 7190 characters
3. See the following error
A fatal PeopleCode SQL error occurred. Please consult your system log for details.

Erreur SQL dans Exec. (2,280) EPPCM_CM.CategoryTypeHandler.Workgroups.OnExecute Name:processHTMLLang PCPC:261079 Statement:3817
Called from:EPPCM_CM.CategoryTypeHandler.Workgroups.OnExecute Name:saveContent Statement:1371
Called from:EPPCM_CNT_WRK.FUNCLIB_01.FieldFormula Name:SaveContAPI Statement:212
Called from:EPPCM_DEFN_CONT.GBL.SavePostChange Statement:1

Au cours de l'exécution d'instructions SQL, une erreur s'est produite dans le sous-programme Exec. Le message précédent devrait avoir présenté les instructions SQL exécutées.


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms