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

THE RESOURCE LIMIT VALUE IN DB2DIAG.LOG AT THE DB2START MAY BE INCORRECT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The db2diag.log entry logged at db2start time may report 
incorrect resource limit. 
Here is an example on AIX, which reports "Cur core size (bytes)" 
as 0xFFFFFFFF even though the actual core limit is larger than 
4GB: 
 
2010-03-16-14.07.28.539323+540 E635748821A1311    LEVEL: Event 
PID     : 213484               TID  : 258         PROC : db2sysc 
INSTANCE: db2inst1             NODE : 000 
EDUID   : 258 
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:1 
START   : DB2 DBM 
  ...(snip)... 
Cur cpu time limit (seconds)  = 0x7FFFFFFFFFFFFFFF 
Cur file size limit (bytes) = 0x7FFFFFFFFFFFFFFF 
Cur data size (bytes)  = 0x7FFFFFFFFFFFFFFF 
Cur stack size (bytes)  = 0x7FFFFFFFFFFFFFFF 
Cur core size (bytes)  = 0x00000000FFFFFFFF 
Cur memory size (bytes) = 0x7FFFFFFFFFFFFFFF 
nofiles (descriptors)  = 0x7FFFFFFFFFFFFFFF 
 
 
Here is another example on Linux, which reports the limit value 
with 8-byte width: 
$ ulimit -d 4194305    # 4GB + 1KB 
$ ulimit -a | grep data 
data seg size         (kbytes, -d) 4194305 
 
2010-12-15-18.36.38.364001+540 E69107E1400         LEVEL: Event 
PID     : 19055                TID  : 183106529632 PROC : 
db2syscr 
INSTANCE: v95fp5               NODE : 000 
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:1 
START   : DB2 DBM 
DATA #1 : Build Level, 152 bytes 
Instance "v95fp5" uses "64" bits and DB2 code release "SQL09055" 
with level identifier "06060107". 
Informational tokens are "DB2 v9.5.0.5", "s091123", "MI00316", 
Fix Pack "5". 
 ...(snip)... 
Cur cpu time limit (seconds)  = 0xFFFFFFFF 
Cur file size limit (bytes) = 0xFFFFFFFF 
Cur data size (bytes)  = 0x00000400 
Cur stack size (bytes)  = 0xFFFFFFFF 
Cur core size (bytes)  = 0xFFFFFFFF 
Cur memory size (bytes) = 0xFFFFFFFF 
nofiles (descriptors)  = 0x00000800 
 
On Solaris platform, the resource limits may not be written out. 
 
These are just display problem and do not affect the actual 
resource limit.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error description field for more information.            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 5.                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
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
Problem was first fixed in DB2 UDB Version 9.7 FixPack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.01.2011
09.12.2011
09.12.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP5
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.5 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.