IBM Support

JR45770: FEDERATED FMP TRAPPED WHEN QUERY JDBC NICKNAME WITH CLOB DATA LONGER THAN 32K

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Federated FMP process trapped when selecting a JDBC nickname
    with LOB column data greater than 32k:
    
    SELECT * FROM TESTLOB
    
    --------------------------------
    SQL1476N  The current transaction was rolled back because of
    error "-1476".
    SQLSTATE=40506
    
    <StackTrace>
    -------Frame------ ------Function + Offset------
    0x000000000000F4E8 ?unknown + 0x0
    0x09000000073C6518 fetch_lob__14Jdbc_StatementFPiUiPUiT3PUc +
    0x1298
    0x09000000073BD33C fetch_lob__10Jdbc_QueryFPiUiPUiT3PUc + 0x5C
    0x09000000233BC4A8 sqlqg_FMP_Fetch__FP12sqlri_rquery + 0x108
    0x0900000023372DA0
    sqlqgRouter__FP17sqlqg_FMP_RequestPP15sqlqg_FMP_ReplyP10sqlri_uf
    ob + 0x1FA0
    0x0900000023376884 sqlqg_fedstp_hook + 0x1A4
    0x09000000332A103C sqlqgDyload__FP10sqlri_ufob + 0x334
    0x09000000333026E0 sqlerFedFmpListener + 0x790
    0x0900000033B030B4 sqlerWorkerThreadEntry__FPv + 0x4E8
    0x09000000006314F4 _pthread_body + 0xDC
    </StackTrace>
    
    This issue can be reproduce with a Postgre SQL case:
    1. On Postgre SQL side, create a table:
    CREATE TABLE public.testlob("C1" text)
    
    2. Insert data equals or greater than 32k into above table.
    
    3. On Federation Server side, create a nickname pointing to
    above table
    
    4. Select the nickname.
    
    The issue may also happen to other JDBC data srouces.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * The user is running JDBC wrapper.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Federation Server v10.1 FP3.                      *
    ****************************************************************
    

Problem conclusion

  • The problem was firstly fix on Federation Server V10.1 FP3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR45770

  • Reported component name

    FEDSRVR JDBC WR

  • Reported component ID

    5724N9714

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-16

  • Closed date

    2013-10-03

  • Last modified date

    2013-10-03

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

    JR45769

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

Fix information

  • Fixed component name

    FEDSRVR JDBC WR

  • Fixed component ID

    5724N9714

Applicable component levels

  • RA10 PSY

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS2K5T","label":"InfoSphere Federation Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A10"}]

Document Information

Modified date:
07 October 2021