|
Problem IC76633
|
Status: Closed |
DURING DB2 INSTANCE STARTUP THE DIAGPATH SETTING FOR DB2DIAG.LO G LOCATION IS NOT HONORED FOR a FIRST INFO MESSAGE from DB2SYSC |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Unixes *
****************************************************************
* PROBLEM DESCRIPTION: *
* 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. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.8 Fixpack 4 *
**************************************************************** |
| Local Fix: |
n/a |
| available fix packs: |
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
First fixed in DB2 v9.8 Fixpack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.05.2011
01.08.2011
01.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.4
|
 |
