• Type: Bug Fix
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Affects Version/s:
    • Fix Version/s: Backlog
    • Component/s: Application Server
    • Security Level: Public (Public: Anyone can view)
    • Labels:
    • Rice Module:
    • Application Requirement:
    • KAI Review Status:
      Not Required
    • KTI Review Status:
      Not Required


      We are seeing a database exception occur in the middle of the routing process for one of our EDocLite forms. Here is an example:

      org.springframework.jdbc.UncategorizedSQLException: OJB operation; uncategorized SQLException for SQL []; SQL state [72000]; error code [12899]; ORA-12899: value too large for column "KREW_EDL_DMP_T"."CRNT_NODE_NM" (actual: 40, maximum: 30) ; nested exception is java.sql.SQLException: ORA-12899: value too large for column "KREW_EDL_DMP_T"."CRNT_NODE_NM" (actual: 40, maximum: 30)

      It appears that when the form data is being dumped to to the KREW_EDL_DMP_T table using the EDLDatabasePostProcessor, the extractEDLData method concatenates (in the case of split/join scenarios) node names together for entry into the database; however, the field that holds those concatenated node names (CRNT_NODE_NM) is only allowed a maximum of 30 characters.

      I'm not quite following why it is concatenating the node names, but if this is necessary, it sure seems like that limit would be reached quite quickly in many workflow scenarios. I was able to work around the issue by bumping the field length up to 255; however, there may be situations where that limit would be reached as well.



          There are no comments yet on this issue.


            • Assignee:
              tim tim carroll (Inactive)
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: