IBM Support

IT28021: DB2 BACKUP OPERATIONS USING THE NETBACKUP (NBDB2.S064) LIBRARY WILL FAIL WITH AN SQL2079N ERROR, IN VERSION 11.1.4.4.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Starting in Db2 v11.1.4.4, Db2 BACKUP operations using the
    NetBackup (nbdb2.s064) library will fail with an SQL2079N,
    return code "30" error.
    
    For example:
      db2 => BACKUP DATABASE mydbname LOAD
    /usr/openv/netbackup/bin/nbdb2.so64 OPEN 4 SESSIONS BUFFER 1024
      SQL2079N An error was reported by the shared library
      "/usr/openv/netbackup/bin/nbdb2.so64". Return code: "30".
    
    The /var/log/messages file may show additional core dump
    information related to segfault within the db2vend fenced vendor
    process, with tokens that include "json_object_iter_next":
    
      Core was generated by `db2vend (db2med - 258 (APPADMIN)) 0 '.
      Program terminated with signal 11, Segmentation fault.
      #0 0x00007f52d5192053 in json_object_iter_next ()
          from /home/db2inst1/sqllib/lib64/libdb2e.so.1
      ...
      (gdb) bt
      #0 0x00007f52d5192053 in json_object_iter_next ()
         from /home/db2inst1/sqllib/lib64/libdb2e.so.1
      (gdb)
    
    
    The db2 diagnostic log (db2diag.log) will show the following
    error messages:
      2019-01-11-19.26.04.264980-300 I535923E1391   LEVEL:Error
      PID     : 5090         TID : 140364509865728 PROC :  db2sysc 0
      INSTANCE: db2bktst      NODE : 000      DB : SAMPLE
      APPHDL  : 0-22             APPID:*LOCAL.db2bktst.190112002602
      AUTHID  : DB2BKTST     HOSTNAME:
    bbldb2test.bblab.us.equifax.com
      EDUID   : 82               EDUNAME: db2med.22.0 (SAMPLE) 0
      FUNCTION: DB2 UDB, database utilities, sqluVendorCallWrapper,
    probe:337
      MESSAGE : ZRC=0x800F00AF=-2146500433=SQLO_PROG_ERR "Unknown"
      DATA #1 : String, 19 bytes
      Signal encountered.
      DATA #2 : Vendor RC, PD_DB2_TYPE_VENDOR_RC, 4 bytes
      Vendor RC=0x0000001E=30 -- see DB2 API Guide for meaning.
      CALLSTCK: (Static functions may not be resolved correctly, as
    they are resolved to the nearest symbol)
      [0] 0x00007FA942A3DF0E
    
    _Z21sqluVendorCallWrapperP18SQLO_VENDOR_HANDLEP23sqluFencedVendo
    rCommBufjP28sqluFencedVendorProcessStateiP12SQLU_BAGT_CB
      + 0x37E
      [1] 0x00007FA9429BC599
    _Z20sqluInitVendorDeviceP13SQLUMC_IBLK_T + 0x79
      [2] 0x00007FA9429B07AF _Z18sqluMCInitBackupMCP13SQLUMC_IBLK_T
    + 0x13F
      [3] 0x00007FA9429ADA97
    _Z25sqluMCProcessBackupStatesP13SQLUMC_IBLK_T + 0x137
      [4] 0x00007FA9429AD873 _Z32sqluMCStartBackupMediaControllerPcj
    + 0x443
      [5] 0x00007FA9440846BA sqloEDUEntry + 0x57A
      [6] 0x00007FA94BC14AA1 /lib64/libpthread.so.0 + 0x7AA1
      [7] 0x00007FA93B762BDD clone + 0x6D
    
      2019-01-11-19.26.04.272601-300 I537315E917           LEVEL:
    Error
      PID     : 5090                 TID : 140364509865728 PROC :
    db2sysc 0
      INSTANCE: db2bktst             NODE : 000            DB   :
    SAMPLE
      APPHDL  : 0-22                 APPID:
    *LOCAL.db2bktst.190112002602
      AUTHID  : DB2BKTST             HOSTNAME:
    bbldb2test.bblab.us.equifax.com
      EDUID   : 82                   EDUNAME: db2med.22.0 (SAMPLE) 0
      FUNCTION: DB2 UDB, database utilities,
    sqluMapVend2MediaRCWithLog, probe:664
      DATA #1 : String, 135 bytes
      Vendor error: rc = 30 returned from function sqluvint.
      Return_code structure from vendor library
    /usr/openv/netbackup/bin/nbdb2.so64:
    
    
    A trap file may also be seen within the Db2 diagnostic path,
    showing function json_deep_copy() from library
    (/usr/openv/lib/libjanssonST.so) invoking function
    json_object_iter_next() in library
    (/db2/sbe3/sqllib/lib64/libdb2e.so.1):
    
      Process name: db2vend (db2med - 52 (SBE3)) 0
      Signal #11 (SIGSEGV): si_addr is 0x0000003400000010, si_code
    is 0x00000001 (SEGV_MAPERR:Address not mapped to object.)
      0x0000000000405CD5 db2vendCodeTrapHandler + 0x02e5
                    (db2vend (db2med - 52 (SBE3)) 0)
      0x000000349FA32510 address: 0x000000349FA32510 ; dladdress:
    0x000000349FA00000 ; offset in lib: 0x0000000000032510 ;
                    (/lib64/libc.so.6)
      0x00007F98AEA1C053 json_object_iter_next + 0x0003
                    (/db2/sbe3/sqllib/lib64/libdb2e.so.1)
      0x00007F989AC75377 json_deep_copy + 0x0098
                    (/usr/openv/lib/libjanssonST.so)
      0x00007F989AF02E32 address: 0x00007F989AF02E32 ; dladdress:
    0x00007F989AE78000 ; offset in lib: 0x000000000008AE32 ;
                    (/usr/openv/lib/libnbbasecST.so)
      0x00007F989AF050A6 vnet_connect_to_service + 0x019d
                    (/usr/openv/lib/libnbbasecST.so)
      0x00007F989B26C3CA bprd_connect_before_vxss + 0x009d
                    (/usr/openv/lib/libnbclientcST.so)
      0x00007F989B26C55D bprd_connect_need_auth + 0x0117
                    (/usr/openv/lib/libnbclientcST.so)
      0x00007F989B26C644 bprd_connect + 0x000f
                    (/usr/openv/lib/libnbclientcST.so)
      0x00007F989B2723EE bprd_get_features + 0x0087
                    (/usr/openv/lib/libnbclientcST.so)
      0x00007F989B4D4582 bsa_checkFeatureId + 0x01ce
                    (/usr/openv/lib/libxbsa64.so)
    
    
    The problem is caused by function name collision between newly
    introduced DB2 JSON related function in Version 11.1.4.4
    

Local fix

  • Upgrade to the fixpack inclusive of this APAR 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

    IT28021

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-07

  • 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:

    IT36464 IT37301

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU029","label":"Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
17 June 2021