IBM Support

JR60168: INSERT INTO ZDB2 THROUGH NICKNAME FAILS WITH "COLUMN <COLNAME> HAS A TYPE OF GRAPHIC WHICH IS NOT RECOGNIZED"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When inserting into a Nickname for z/OS DB2 table containing
    GRAPHIC column, which column size is larger than 63 double
    bytes, it fails with the following error in db2diag.log.
    ----------------------------------------------------------------
    2018-09-03-15.04.45.262000+540 I1876709F966 LEVEL: Error
    PID : 2768 TID : 260 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000 DB : DB2K1
    APPHDL : 0-10560 APPID: 10.33.2.3.59800.180903055533
    AUTHID : Q2K1102 HOSTNAME: vnk5384
    EDUID : 260 EDUNAME: db2agent (DB2K1) 0
    FUNCTION: DB2 UDB, SW- query graph,
    sqlnq_fcs::populate_default_local_type, probe:120
    MESSAGE : Search default type mapping for the remote target type
    
    DATA #1 : Hexdump, 71 bytes
    0x0000006ADDFF71F0 : 436F 6C75 6D6E 2052 444B 4732 3454 5F53
    Column XXXXXXXXX
    0x0000006ADDFF7200 : 594B 5F4E 594F 5F54 5820 6861 7320 6120
    XXXXXXXXX has a
    0x0000006ADDFF7210 : 7479 7065 206F 6620 4752 4150 4849 4320
    type of GRAPHIC
    0x0000006ADDFF7220 : 7768 6963 6820 6973 206E 6F74 2072 6563
    which is not rec
    0x0000006ADDFF7230 : 6F67 6E69 7A65 64 ognized
    ----------------------------------------------------------------
    
    There is no problem reading(selecting) from the Nickname.
    
    DB2 trace indicates that Federation could not find a matching
    Revers default data type mapping definition for the remote
    GRAPHIC column.
    
    <Snippet from db2trc.fmt>
    ----------------------------------------------------------------
    49442481 entry DB2 UDB drda wrapper
    UnfencedDRDA_Server::get_my_default_local_type_mapping fnc
    (1.3.44.40.0)
    pid 2768 tid 260 cpid 2480 node 0
    eduid 260 eduname db2agent
    bytes 65
    
    Data1 (PD_TYPE_SINT,2) signed integer:
    512                       <-- type id
    Data2 (PD_TYPE_STRING,0) String:
    Object not dumped: Address: 0x00000239A5BFDBBA Size: 0 Reason:
    Zero-length data    <-- remote schema name
    Data3 (PD_TYPE_STRING,7) String:
    GRAPHIC               <-- remote type name
    Data4 (PD_TYPE_SINT,4) signed integer:
    160                       <-- remote length in bytes.
    Data5 (PD_TYPE_SINT,2) signed integer:
    0                           <-- remote scale
    Data6 (PD_TYPE_SINT,2) signed integer:
    78                          <-- remote for bit? = 'N'
    .....
    49442497       exit DB2 UDB Query Gateway Local_Type::matches
    fnc (2.3.38.578.0)
           pid 2768 tid 260 cpid 2480 node 0
           rc = 0                                           <-- No
    match found.
    ----------------------------------------------------------------
    
    Conclusion:
    For MVS type data source, insert into nickname with a Graphic(n)
    data type when n is larger than 63, it reports error "Column
    <colname> has a type of GRAPHIC which is not recognized". This
    is because when insert into nickname with graphic(n), it will
    check the length of graphic type mapping, for graphic DBCS char
    it will get length value of 2n, before the fix, it will limit
    the length with 127, 63*2, after the fix, it moved the
    limitation.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
    ****************************************************************
    

Problem conclusion

  • First fixed in Db2 11.1 Mod 4 Fixpack 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR60168

  • Reported component name

    FEDERATION SERV

  • Reported component ID

    5724N9700

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-10-18

  • Closed date

    2020-01-16

  • Last modified date

    2020-01-16

  • 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

    FEDERATION SERV

  • Fixed component ID

    5724N9700

Applicable component levels

  • RB10 PSN

       UP

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SS2K5T","label":"InfoSphere Federation Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B10"}]

Document Information

Modified date:
02 September 2021