home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC91217 Status: Closed

CALLS TO SQLF_FIX_DBM_CFG BY DOWNLEVEL CLIENT CAN RESULT IN EACCESS IF USER
DOESN'T HAVE WRITE PERMISSION TO DB2SYSTM

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Downlevel clients will make a call to sqlf_fix_dbm_cfg since the 
client level and database server level are not the same.  This 
increases the probability of an EACCESS error caused by the user 
not having write access to db2systm.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users with clients and servers at different levels           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 9.                       * 
****************************************************************
Local Fix:
Open up the permissions on the db2systm file
available fix packs:
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.7 Fix Pack 9.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC91808 IC95239 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.04.2013
17.12.2013
17.12.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList