My Oracle Support Banner

Document Signature History Is Failed To Get Update In Table with Error "string literal too long" (Doc ID 2520016.1)

Last updated on JANUARY 24, 2020

Applies to:

PeopleSoft Enterprise SCM Supplier Contract Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.


Document Signature History is failed to get Update in Table

History is not getting updated and status of the document is still pending, although the Signature process is completed in DocuSign System.

Receiving SQL Fatal error on page when clicked on 'Get e-Signature status'.This happens if signature history is more than 4000 characters.


A fatal peopleCode SQL error occurred .
SQL error in Exec(2,280)
Return: 1704 - ORA-01704: string literal too long

The following error in app server log
PSAPPSRV.25358 (4313) [2018-08-17T11:03:06.318 COREBri@10.***.250.** (IE 11.0; WIN7) ICPanel](0) SQL error. Function: SQLExec
  Error Position: 46
  Return: 1704 - ORA-01704: string literal too long
  Statement: update ps_cs_doc_hdr set cs_collab_comments = '  ********************************************'

The issue can be reproduced at will with the following steps:
1. Import any pdf file in Document Management (Supplier Contracts--> Create Contracts and Documents--> Document Management)
2. Click on "Prepare and Route for e-Signature"
3. Enter e-mail id and send document for signing
4. From email review document for more than 20 times
5. re-open document and click on "get e-Signature Status"
6. Error message

The issue has the following business impact:
Due to this issue, users cannot use DocuSign e-signature process for signing the contract documents.




To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.