IBM Support

IT25377: GRANT STATEMENT IS MISSING FROM DB2LOOK OUTPUT.

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

  • The problem is following grant statement is missing from db2look
    -x  output/
    db2 grant read,write on variable sysibm.client_ipaddr to user
    db2admin
    
    Here's the simplified repro :
    
    db2 "CREATE DB SAMPLE USING CODESET UTF-8 TERRITORY US
    RESTRICTIVE"
    db2 connect to SAMPLE
    db2 grant read,write on variable sysibm.client_ipaddr to user
    db2admin
    
    $ db2look -d SAMPLE -x
    -- No userid was specified, db2look tries to use Environment
    variable USER
    -- USER is: DB2INST1
    -- This CLP file was created using DB2LOOK Version "10.5"
    -- Timestamp: Wed 13 Jun 2018 03:47:00 AM EDT
    -- Database Name: SAMPLE
    -- Database Manager Version: DB2/LINUXX8664 Version 10.5.9
    -- Database Codepage: 1208
    -- Database Collating Sequence is: IDENTITY
    -- Alternate collating sequence(alt_collate): null
    -- varchar2 compatibility(varchar2_compat): OFF
    
    CONNECT TO SAMPLE;
    COMMIT WORK;
    CONNECT RESET;
    TERMINATE;
    
    This happens because we exclude SYSIBM schema when selecting
    from SYSCAT.VARIABLEAUTH.
    We don't include SYSIBM schema because many implicit grants
    under schema SYSIBM would have been printed out.
    With this fix we will print grant command with schema SYSIBM if
    it is explicitly specified i.e if the command is db2look -d
    SAMPLE -x -z SYSIBM, it will print the grant message.
    

Local fix

  • N/A
    

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

    IT25377

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A50

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-06-14

  • 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

    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":"10.5","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 January 2020