IBM Support

PI66462: Transaction log column is too short and reports a SqlDataException

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After creating transaction log tables as detailed in Knowledge
    Center, the application reported:
    com.ibm.db2.jcc.am.SqlDataException: Error for batch element
    #1: THE VALUE OF INPUT VARIABLE OR PARAMETER NUMBER 6 IS
    INVALID OR TOO LARGE
    FOR THE TARGET COLUMN OR THE TARGET VALUE
    at com.ibm.db2.jcc.am.gd.a(Unknown Source)
    

Local fix

  • dtop and create WAS_TRAN_LOG using:
    CREATE TABLE WAS_TRAN_LOG(
      SERVER_NAME VARCHAR(128),
      SERVICE_ID SMALLINT,
      RU_ID BIGINT,
      RUSECTION_ID BIGINT,
      RUSECTION_DATA_INDEX SMALLINT,
      DATA VARCHAR(32548) FOR BIT DATA)
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server that have configured the transaction *
    *                  service to store logs in a database.        *
    ****************************************************************
    * PROBLEM DESCRIPTION: While creating transaction log tables   *
    *                      in DB2 database as detailed in the      *
    *                      Knowledge Center, the application       *
    *                      reported :                              *
    *                      com.ibm.db2.jcc.am.SqlDataException:    *
    *                      Error for batch element                 *
    *                      #1: THE VALUE OF INPUT VARIABLE OR      *
    *                      PARAMETER NUMBER 6 IS                   *
    *                      INVALID OR TOO LARGE                    *
    *                      FOR THE TARGET COLUMN OR THE TARGET     *
    *                      VALUE                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Deprecated DB2 datatype 'LONG VARCHAR' is silently converted
    to 'VARCHAR', with a smaller maximum byte size. Subsequently
    attempting to insert data into the row that exceeds the
    truncated maximum size causes SqlDataException to be thrown.
    

Problem conclusion

  • The column datatype for DB2 has been changed to 'BLOB'.
    
    The fix for this APAR is currently targeted for inclusion in
    WebSphere Application Server fix pack 8.0.0.14, 8.5.5.12 and
    9.0.0.4 and WebSphere Application Server Liberty fix pack
    17.0.0.2.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI66462

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-07-26

  • Closed date

    2016-12-20

  • Last modified date

    2016-12-20

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R800 PSY

       UP

  • R850 PSY

       UP

  • R900 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
16 October 2021