JR43168: SQL901N ERROR OR TRAP WHEN USING DRDA NICKNAME WITH VARCHAR COLUMN AND REMOTE DATABASE CODEPAGE IS DIFFERENT THAN LOCAL

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • When using DRDA nickname with VARCHAR column while codepage are
    different between remote and local database, you may encounter
    following error:
    
    SQL0901N The SQL statement failed because of a non-severe system
    error.Subsequent SQL statements can be processed. (Reason "real
    column
    length exceeds max length".) SQLSTATE=58004
    
    or trap due to memory corruption:
    
    2012-06-15-10.38.54.768679+480 I1026157A1893      LEVEL: Severe
    PID     : 332222               TID  : 45437       PROC : db2sysc
    0
    INSTANCE: db2inst1             NODE : 000         DB   :
    <dbname>
    APPHDL  : 0-36486              APPID:
    *LOCAL.db2inst2.120615010430
    AUTHID  : PROC
    EDUID   : 45437                EDUNAME: db2agent (<dbname>) 0
    FUNCTION: DB2 UDB, SQO Memory Management,
    sqloDiagnoseFreeBlockFailure, probe:10
    MESSAGE : Possible memory corruption detected.
    DATA #1 : ZRC, PD_TYPE_ZRC, 4 bytes
    0x820F0002
    DATA #2 : Corrupt block address, PD_TYPE_CORRUPT_BLK_PTR, 8
    bytes
    0x0780000320562780
    DATA #3 : Block header, PD_TYPE_BLK_HEADER, 24 bytes
    0x0780000320562768 : 2020 2020 2020 2020 2020 2020 2020 2020
    
    0x0780000320562778 : 2020 2020 2020 0560
    .`
    DATA #4 : Data header, PD_TYPE_BLK_DATA_HEAD, 48 bytes
    0x0780000320562780 : 7331 3230 3232 3800 0000 0000 0000 0000
    s120228.........
    0x0780000320562790 : 0000 0000 0000 0000 7543 BB1E 008A 1B14
    ........uC......
    0x07800003205627A0 : 0133 02A3 6079 5298 0700 0006 30A5 D120
    .3..`yR.....0..
    CALLSTCK:
      [0] 0x0900000003B12E90 pdLog + 0x88
      [1] 0x0900000003EF5BA4
    @78@sqloDiagnoseFreeBlockFailure__FP8SMemFBlkCb + 0xF4
      [2] 0x0900000003EF59E0
    sqloDiagnoseFreeBlockFailure__FP8SMemFBlkCb@glue6D5 + 0x78
      [3] 0x0900000003BA47C4 sqlofmblkEx + 0x80
      [4] 0x090000000525A758
    sqlra_sqlW_mem_free_sibling_list__FP8sqlrr_cbP23sqlra_workspace_
    siblingPUl + 0x87C
      [5] 0x09000000052617C4
    sqlra_sqlW_mem_freespace__FP8sqlrr_cbUlPUli + 0x430
      [6] 0x09000000052612C8
    sqlra_sqlW_mem_freespace__FP8sqlrr_cbUlPUli@glue103E + 0x74
      [7] 0x0900000005DBCE3C
    sqlra_sqlW_check_for_cleanup__FP8sqlrr_cbUlP7OSSTick + 0x60
      [8] 0x090000000525FC04
    sqlra_sqlW_get_dynamic_section__FP8sqlrr_cbP16sqlra_cached_var +
    0x11A8
      [9] 0x090000000420F440
    sqlra_load_var__FP8sqlrr_cbP16sqlra_cached_var + 0x468
    
    After db2set DB2MEMDBG=PROTECT, you can see the following call
    stack:
    
    0x000000000000F414 ?unknown + 0x0
    0x0900000018A658C0
    process_output_value__14DRDA_StatementFP10sqlri_rcolP18drda_colu
    mn_bufferiT3PUib + 0x3A0
    0x0900000018A65318
    process_output_data__14DRDA_StatementFP17Runtime_Data_List +
    0x278
    0x0900000018A784F4 fetch__10DRDA_QueryFv + 0x194
    0x090000000CC5FF60 sqlqg_FMP_Fetch__FP12sqlri_rquery + 0x1A0
    0x090000000CC1CE14
    sqlqgRouter__FP17sqlqg_FMP_RequestPP15sqlqg_FMP_ReplyP10sqlri_uf
    ob + 0x22D4
    0x090000000CC200F0 sqlqg_fedstp_hook + 0x1B0
    0x090000004E7EA0C8 sqlqgDyload__FP10sqlri_ufob + 0x258
    0x090000004E7D4EB0
    sqlriFedInvokerTrusted__FP10sqlri_ufobP21sqlriRoutineErrorIntf +
    0x1F0
    0x090000004E7D42C0
    sqlriFedInvokeInvoker__FP10sqlri_ufobP14sqlqg_Fmp_Info + 0xF0
    0x090000004E6D2A14
    sqlqg_Call_FMP_Thread__FP17sqlqg_FMP_RequestPP15sqlqg_FMP_Reply
    + 0x46C
    0x090000004EFAB8B8 sqlqgFetch__FP12sqlri_rquery + 0xDC0
    0x090000004EFE4FCC sqlri_djx_rta__FP8sqlrr_cb + 0xA10
    

Local fix

  • Enlarge the VARCHAR column length to enough value for the
    nickname by ALTER NICKNAME
    

Problem summary

  • User affected:
      Users of InfoSphere Federation Server
    Problem description and summay:
      See error description
    

Problem conclusion

  • Problem was fistly fixed in Version 9.5, FixPak 10. This
    fix should be applied on the federation Server.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR43168

  • Reported component name

    ODBC WRAPPER

  • Reported component ID

    5724N9707

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-06-20

  • Closed date

    2012-11-01

  • Last modified date

    2012-11-01

  • 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

    ODBC WRAPPER

  • Fixed component ID

    5724N9707

Applicable component levels

  • R950 PSY

       UP



Rate this page:

(0 users)Average rating

Document information


More support for:

InfoSphere Federation Server
Data Sources and Wrappers - ODBC

Software version:

950

Reference #:

JR43168

Modified date:

2012-11-01

Translate my page

Machine Translation

Content navigation