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 IC71038 Status: Closed

nodelock.db2 has world-write permission

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
During license addition and removal, nodelock.db2 is created by 
the license subsystem.   It is not accessed by DB2 after those 
operations have completed.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 Users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During license addition and removal, nodelock.db2 is created * 
* by the license subsystem.  It is not accessed by DB2 after   * 
* those operations have completed.                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* The customer needs to upgrade to db2_v91fp10 or higher       * 
* versions to include this Fix.                                * 
****************************************************************
Local Fix:
Remove the file.
available fix packs:
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
This issue is fixed in db2_v91fp10. The file  'nodelock.db2' 
will be deleted automatically after db2licm is finished with 
it.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC71271 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.09.2010
17.06.2011
17.06.2011
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.10 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.