IBM Support

IT07693: FTE JEE DB-LOGGER GENERATES WARNING MESSAGES IN WAS CE 2.1 WHEN USED WITH ORACLE DB

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, generates warnings when used with an
    Oracle database. An example of such a warning message is as
    follows:
    
    
    11:11:39,505 WARN  [Schema] Existing column "EXECUTED_COMMAND"
    on table "FTELOG.CALL" is incompatible with the same column in
    the given schema definition. Existing column:
    Full Name: CALL.EXECUTED_COMMAND
    Type: clob
    Size: 4000
    Default: null
    Not Null: false
    Given column:
    Full Name: Call.EXECUTED_COMMAND
    Type: varchar
    Size: 255
    Default: null
    Not Null: false
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects all users of the WebSphere MQ File Transfer
    Edition JEE Database Logger to persist, to an Oracle database,
    information published as XML log messages to the SYSTEM.FTE
    topic on the coordination queue manager.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    If any of the columns defined for a table created in Oracle
    database are of type CLOB (e.g., NCLOB),  the Java class defined
    using Java Persistence Architecture to represent that particular
    table should annotate the class member-variables representing
    the column of type CLOB with  "@Lob".  If not, the column type
    is assumed to be of type "VARCHAR" by  Java Persistence
    Architecture implementation.
    
    This annotation was not included in the WebSphere MQ File
    Transfer Edition Java classes where appropriate. Therefore, when
    the Java Persistence Architecture implementation tried to match
    the member field representing a column in a database table with
    the actual column in the database table, the difference was
    detected and reported as a warning by Java Persistence
    Architecture implementation.
    

Problem conclusion

  • The WebSphere MQ File Transfer Edition JEE Database Logger
    classes representing the database tables have been updated with
    the required annotations.
    
    
    Note :
    
    Columns with the names  "SOURCE_BRIDGE_URL"  and
    "DESTINATION_BRIDGE_URL" in the table
    "FTELOG"."TRANSFER_EVENT" should be defined with the column
    length 2083.
    
    Users of WebSphere MQ File Transfer Edition  using DB2 database
    may have to update these columns' lengths manually after
    applying this APAR,  if the length of these columns has been
    defined as 1024. Otherwise if data longer than 1024 bytes is
    written then the data will be truncated and no warning may be
    given by DB2.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.0       7.0.4.6
    v7.5       7.5.0.7
    v8.0       8.0.0.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

    IT07693

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-17

  • Closed date

    2016-02-08

  • Last modified date

    2016-02-08

  • 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

  • R704 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.4","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
08 February 2016