IBM Support

IT31891: WITH ROOT_SQUASH ENABLED THE ADD DBPARTITIONNUM COMMAND CAN FAILWITH SQL6073N

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When a partition is being added to a db2 instance that is stored
    on NFS storage, and root_squash is enabled (which is the
    default), the ADD DBPARTITIONNUM command can fail with: SQL6073N
    An add or drop operation of a database partition or DB2 member
    failed. SQLCODE = "-1042". Database name = "".
    
    On an NFS mount, when root_squash is enabled (default), remote
    root gets mapped to nsfnobody. db2 fails when trying to get
    SQLDBCONF which is a root command. An OS error EACCES (13) is
    also returned.
    
    On remote node that is being added, the remote node will try to
    get the cfg file from another node, in this case node 1
    
    2020-01-19-19.21.33.827120-300 I71516E625            LEVEL:
    Event
    PID     : 20172                TID : 46913067935488  PROC :
    db2sysc 16
    INSTANCE: xxxxxxxx             NODE : 016            DB   :
    
    APPHDL  : 16-53                APPID: *N16.xxxxxx.200120002129
    AUTHID  : xxxxxxxx             HOSTNAME: usl00001455
    EDUID   : 93                   EDUNAME: db2agent (instance) 16
    FUNCTION: DB2 UDB, base sys utilities, sqleCreateDb, probe:4267
    DATA #1 : <preformatted>
    Adding a node and getting cfg.
        Do we have a node: 1
        We are adding node: 16
        We are getting cfg from node: 1
        We are on node: 16
        Catalog node is: 0
    
    ...
    
    RETCODE : ZRC=0x810F0021=-2129723359=SQLO_RCV_PARTIAL
              "Message was received partially"
    
    2020-01-19-19.21.34.642177-300 I72761E549            LEVEL:
    Error
    PID     : 20172                TID : 46913067935488  PROC :
    db2sysc 16
    INSTANCE: xxxxxxxx             NODE : 016            DB   :
    
    APPHDL  : 16-53                APPID: *N16.xxxxxxxx.200120002129
    AUTHID  : xxxxxxxx             HOSTNAME: xxxxxxxx
    EDUID   : 93                   EDUNAME: db2agent (instance) 16
    FUNCTION: DB2 UDB, base sys utilities, sqleGetDbCfgFileRemotely,
    probe:20
    MESSAGE : ZRC=0xFFFFFBEE=-1042
              SQL1042C  An unexpected system error occurred.
    
    On node 1, we will see
    
    2020-01-19-19.21.34.613378-300 E975875E1019          LEVEL:
    Error (OS)
    PID     : 20140                TID : 46912887545440  PROC :
    db2remot
    INSTANCE: xxxxxxx              NODE : 001
    HOSTNAME: xxxxxxxxx
    FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80
    MESSAGE : ZRC=0x840F0001=-2079391743=SQLO_ACCD "Access Denied"
              DIA8701C Access denied for resource "", operating
    system return code
              was "".
    CALLED  : OS, -, open                             OSERR: EACCES
    (13)
    DATA #1 : Codepath, 8 bytes
    4:9:15:24:40
    DATA #2 : File name, 66 bytes
    /db2/xxxxxx/dbpath/xxxxxx/NODE0001/SQL00001/MEMBER0001/SQLDBCONF
    DATA #3 : SQO Open File Options, PD_TYPE_SQO_FILE_OPEN_OPTIONS,
    4 bytes
    SQLO_REVISE, SQLO_READONLY, SQLO_SHAREREAD, SQLO_WRITETHRU
    DATA #4 : Hex integer, 4 bytes
    0x000001A0
    DATA #5 : signed integer, 4 bytes
    0
    DATA #6 : Hex integer, 4 bytes
    0x00000000
    DATA #7 : String, 105 bytes
    Search for ossError*Analysis probe point after this log entry
    for further
    self-diagnosis of this problem.
    
    2020-01-19-19.21.34.616556-300 I976895E1427          LEVEL:
    Warning
    PID     : 20140                TID : 46912887545440  PROC :
    db2remot
    INSTANCE: xxxxxxx              NODE : 001
    HOSTNAME: xxxxxxx
    FUNCTION: DB2 UDB, config/install, sqlf_read_db_and_verify,
    probe:838
    DATA #1 : <preformatted>
    Error on sqlf_openfile.
    pDbName: <NO DBNAME>
    pCfgFilePath
    /db2/xxxxxxx/dbpath/xxxxxxx/NODE0001/SQL00001/MEMBER0001/SQLDBCO
    NF
    pMemberDbPath
    /db2/xxxxxxx/dbpath/xxxxxxx/NODE0001/SQL00001/MEMBER0001/
    memberCfgFilepath
    /db2/xxxxxxx/dbpath/xxxxxxx/NODE0001/SQL00001/MEMBER0001/SQLDBCO
    NF
    bool bGlobalFile 0
    globalDbPath /db2/xxxxxxx/dbpath/xxxxxxx/NODE0001/SQL00001/
    globalCfgFilepath
    /db2/xxxxxxx/dbpath/xxxxxxx/NODE0001/SQL00001/SQLDBCONF
    userExpectedSize 16384
    pFileOpen 0
    openMode 84
    callerID 405930032
    retry: 0 of num_retries: 0
    rc: -2079391743
    CALLSTCK: (Static functions may not be resolved correctly, as
    they are resolved to the nearest symbol)
      [0] 0x00002AAAACC62EED pdLogPrintf + 0x8D
      [1] 0x00002AAAB0D17119
    _Z23sqlf_read_db_and_verifyPcS_S_bP10sqlf_dbcfdsmP12SQLO_FHANDLE
    Piii + 0x6A9
      [2] 0x00002AAAB0D228C2 _Z8sqlfixdbPKcP10sqlf_dbcfdmmS0_b +
    0x3F2
      [3] 0x0000000000408C20
    _Z27sqleReadStorageInfoFromDiskP9sqlf_kcfdP19sqloRemoteCmdHandle
    PcbP5sqlca + 0x910
      [4] 0x0000000000406239 main + 0x12D9
      [5] 0x0000003818A1ED20 __libc_start_main + 0x100
      [6] 0x0000000000404E99 /db2/xxxxxxx/home/sqllib/adm/db2remot +
    0x4E99
    
    
    To quickly check if this is the problem try using touch as root
    to create a test file on the remote node that is being added.
    For example:
    
    On the remote node
    
    [root@xxxxxxxxxxx xxxx]# touch test.txt
    touch: cannot touch `test.txt': Permission denied
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All Users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 11.1 Fix Pack 6                       *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 Version 11.1 Fix Pack 6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT31891

  • 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

    2020-02-18

  • Closed date

    2020-03-23

  • Last modified date

    2020-03-23

  • 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

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
23 March 2020