Nikhil Garge (Nikhil_Garge)
Virtusa Corporation
Associate Architect Technology
Virtusa Corporation
Nikhil_Garge Member since 2015 5 posts
Virtusa Corporation
Posted: August 1, 2017
Last activity: January 25, 2018
Posted: 1 Aug 2017 13:13 EDT
Last activity: 25 Jan 2018 14:28 EST

ORA-12899: value too large for column for pyMEMO (actual: 256, maximum: 255)

Hello All ,

We are using PEGA 7.1.7 and the above mentioned exception is logged in AES alert-

The pyMemo is present in the custom work history table A_B_Work_Hist with the column data type as VARCHAR(255 Bytes).Also at run time the Audit has below entry

"Added History ~~~~~ ABC updated successfully "

the data type of the database column in the table A_B_Work_Hist is VARCHAR2 (255 BYTES) due to which Pega consider it as a foreign character.

There are 2 solution I can think of

  1. 1. 1. change the datatype of the pyMemo column in the table to VARCHAR2 (255 CHAR) which we are not sure what would be the impact on existing audit.
  1. 1. 2. remove the '~' from the field value referred in the custom Add history activity from "Added {1}~~~{2} " to "Added {1} {2} " which removes this special character and the audit looks like as below

"Added History ABC updated successfully "

Please suggest if i implement Approach 2 then will the AES exception related to above will be fixed?



***Edited by Moderator: Marissa to update categories***

Data Integration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.