IBM Support

IT06125: FTE DB-Logger receives PersistenceException: ORA-01400 : when inserting null value into ("FTELOG"."CALL_ARGUMENT"."VALUE")

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The WebSphere MQ File Transfer Edition Database Logger 7.0.4.4
    running in WAS CE 2.1 is sending some messages to the reject
    queue without the property usr.WMQFTE_ReasonForRejection.
    
    An Exception appears in the WAS CE error log related to an
    insert of a null value in table FTELOG"."CALL_ARGUMENT"."VALUE
    The error is similar to this:
    
    Caused by:
     org.apache.openjpa.persistence.PersistenceException: ORA-01400:
    "not possible to insert a null value into
    ("FTELOG"."CALL_ARGUMENT"."VALUE")"
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of the WebSphere MQ File Transfer
    Edition Database Logger to persist, to a database, information
    published as XML log messages to a topic concerning either:
    
      - A Managed Call operation
    
    or
    
      - A Managed Transfer operation that specifies a program to run
    either before a transfer starts, or after it finishes.
    
    
    Platforms affected:
    MultiPlatform, z/OS, Windows, Solaris x86-64, Solaris SPARC,
    Linux on zSeries, Linux on x86-64, Linux on x86, Linux on S390,
    Linux on Power, IBM iSeries, HP-UX OpenVMS, HP-UX PA-RISC, HP-UX
    Itanium, AIX
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When a managed file transfer is started, a message is logged
    into the database to indicate it. This information is present as
    XML message in the subscription queue. The database logger
    parsers the XML message and updates the information in the
    message to the database. As part of this logging
    "FTELOG.CALL_ARGUMENT" table is updated with the information
    about the call arguments used in the transfer.The "VALUE" column
    in this table is defined not to accept null values(i.e. defined
    with NOT NULL).
    
    One of the call arguments was present in the different form in
    the XML message than the database logger was expecting. Due to
    this difference database logger could not extract the data from
    XML message and tried insert 'null' value in the "VALUE" column.
    This resulted in Oracle database throwing the error ORA-01400
    and Database Logger received PersistenceException.
    
    ------------
    
    
    When a managed file transfer is started, the WebSphere MQ File
    Transfer Edition (FTE) source agent for the transfer will
    publish an XML message to a topic on the coordination queue
    manager. A copy of this message is received by the WebSphere MQ
    FTE Database Logger application in order to persist the
    information it contains to a database.
    
    The WebSphere MQ FTE Database Logger incorrectly parsed
    correctly formed (as per the schema definition) XML messages
    that contained, one or more of, the XML elements:
    
      - property
      - argument
      - target
    
    that related to commands or programs to execute as part of the
    managed transfer. These XML elements are child elements of the
    parent  element in the XML message.
    
    Because the XML message was not parsed correctly, the WebSphere
    MQ Database Logger attempted to create a new entry in the
    database table FTELOG.CALL_ARGUMENT that contained a NULL entry
    for the column "VALUE". The "VALUE" column is defined as one
    that does not accept a NULL value. As a result, the underlying
    database throw an exception when the attempt was made to persist
    this new entry.
    

Problem conclusion

  • The WebSphere MQ File Transfer Edition Database Logger code has
    been updated such that, for XML messages published when a
    managed transfer is started, the XML elements:
    
      - property
      - argument
      - target
    
    relating to commands or programs to execute as part of the
    managed transfer are parsed correctly, so that the data
    contained within these elements are extracted correctly to
    persist to the database.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.5
    
    The latest available FTE maintenance can be obtained from
    'Fix List for WebSphere MQ File Transfer Edition 7.0'
    http://www-01.ibm.com/support/docview.wss?uid=swg27015313
    
    The latest available MQ maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT06125

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    702

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-12-18

  • Closed date

    2015-02-22

  • Last modified date

    2015-04-21

  • 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

    WMQ FILE TRANSF

  • Fixed component ID

    5724R1000

Applicable component levels

  • R702 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.2","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
21 April 2015