suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT25377 Status: Closed

GRANT STATEMENT IS MISSING FROM DB2LOOK OUTPUT.

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem 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.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
N/A
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2018
16.01.2020
16.01.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)