DB2 FOR LUW / DB2FORLUW / 970 - DB2

During DB2 instance startup procedure the DIAGPATH setting for 
db2diag.log locations is not honored for the first informational 
message from db2sysc. 
 
By means of APAR IC67948  the new functionality was added to the 
instance controller program to print informational message like: 
2000-00-00-00.00.00.0000000-000 E2988A1291         LEVEL: Event 
 
PID     : xxxxxxxx            TID  : 1           PROC : db2sysc 
 
INSTANCE: db2                NODE : 000 
 
FUNCTION: DB2 UDB, base sys utilities, DB2main, probe:1 
 
START   : DB2 DBM 
 
DATA #1 : Build Level, 152 bytes 
 
Instance "db2" uses "64" bits and DB2 code release "SQL09018" 
 
with level identifier "02090107". 
 
Informational tokens are "DB2 v9.1.0.8", "s090823", "U823514", 
Fix Pack 
"8". 
 
DATA #2 : System Info, 224 bytes 
 
System: AIX test 3 5 00CCCAFC4C00 
 
CPU: total:8 online:8 Threading degree per core:2 
 
Physical Memory(MB): total:8192 free:394 
 
Virtual  Memory(MB): total:22528 free:10099 
 
Swap     Memory(MB): total:14336 free:9705 
 
Kernel   Params: msgMaxMessageSize:4194304 
msgMaxQueueSize:4194304 
                 shmMax:68719476736 shmMin:1 shmIDs:131072 
 
                 shmSegments:68719476736 semIDs:131072 
semNumPerID:65535 
                 semOps:1024 semMaxVal:32767 
semAdjustOnExit:16384 
Cur cpu time limit (seconds)  = 0x7FFFFFFFFFFFFFFF 
 
Cur file size limit (bytes) = 0x7FFFFFFFFFFFFFFF 
 
Cur data size (bytes)  = 0x0000000008000000 
 
Cur stack size (bytes)  = 0x0000000010000000 
Cur core size (bytes)  = 0x000000003FFFFE00 
 
Cur memory size (bytes) = 0x7FFFFFFFFFFFFFFF 
 
nofiles (descriptors)  = 0x7FFFFFFFFFFFFFFF 
 
 
 
 
This APAR is addressing the issue that this informational 
message only goes to the db2diag.log file stored at the default 
location at $<INSTANCE_HOME>/sqllib/db2dump/db2diag.log  even if 
the database manager  DIAGPATH setting  points to another 
location.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During DB2 instance startup procedure the DIAGPATH           * 
* settingfordb2diag.log locations is not honored for the       * 
* firstinformationalmessage from db2sysc.By means of APAR      * 
* IC67948  the new functionality was added totheinstance       * 
* controller program to print informational                    * 
* messagelike:2000-00-00-00.00.00.0000000-000 E2988A1291       * 
*  LEVEL:EventPID    : xxxxxxxx            TID  : 1            * 
* PROC :db2syscINSTANCE: db2                NODE :             * 
* 000FUNCTION: DB2 UDB, base sys utilities, DB2main,           * 
* probe:1START  : DB2 DBMDATA #1 : Build Level, 152            * 
* bytesInstance "db2" uses "64" bits and DB2 code              * 
* release"SQL09018"with level identifier                       * 
* "02090107".Informational tokens are "DB2 v9.1.0.8",          * 
* "s090823","U823514",Fix Pack"8".DATA #2 : System Info, 224   * 
* bytesSystem: AIX test 3 5 00CCCAFC4C00CPU: total:8 online:8  * 
* Threading degree per core:2Physical Memory(MB): total:8192   * 
* free:394Virtual  Memory(MB): total:22528 free:10099Swap      * 
* Memory(MB): total:14336 free:9705Kernel  Params:             * 
* msgMaxMessageSize:4194304msgMaxQueueSize:4194304shmMax:6871947 
* shmMin:1 shmIDs:131072shmSegments:68719476736                * 
* semIDs:131072semNumPerID:65535semOps:1024                    * 
* semMaxVal:32767semAdjustOnExit:16384Cur cpu time limit       * 
* (seconds)  = 0x7FFFFFFFFFFFFFFFCur file size limit (bytes) = * 
* 0x7FFFFFFFFFFFFFFFCur data size (bytes)  =                   * 
* 0x0000000008000000Cur stack size (bytes)  =                  * 
* 0x0000000010000000Cur core size (bytes)  =                   * 
* 0x000000003FFFFE00Cur memory size (bytes) =                  * 
* 0x7FFFFFFFFFFFFFFFnofiles (descriptors)  =                   * 
* 0x7FFFFFFFFFFFFFFFThis APAR is addressing the issue that     * 
* this informationalmessage only goes to the db2diag.log file  * 
* stored at thedefaultlocation at                              * 
* $<INSTANCE_HOME>/sqllib/db2dump/db2diag.logeven ifthe        * 
* database manager  DIAGPATH setting  points to                * 
* anotherlocation.                                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Uograde to DB2 9.7 FP3                                       * 
****************************************************************

n/a

DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 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
 

Problem was first fixed in Version 9.7 Fix Pack 3

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

19.04.2010
19.10.2010
19.10.2010

9.7.FP3