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

DB2 PURESCALE ON AIX - CHANGE LOGGING LEVEL IN MOUNTV10_*.KSH SCRIPTS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
This is a serviceability enhancement. 
 
The Purescale TSA scripts - mountV10_monitor.ksh, 
mountV10_start.ksh, mountV10_stop.ksh may use debug priority 
level for some status messages, e.g. "logger -i -p debug ...". 
On AIX such "debug" messages are not logged per default in the 
system logs. So for post mortem analysis we may be missing 
important information. We should change the logging level to 
"info".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 pureScale users                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 FP3                              * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Fixed in DB2 version 10.1 FP3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
05.02.2013
01.10.2013
01.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList