DB2 FOR LUW / DB2FORLUW / A10 - DB2

db2pd command may show incorrect NEWLOGPATH, MIRRORLOGPATH, and 
OVERFLOWLOGPATH as follows: 
 
$ db2 connect to sample 
$ db2 update db cfg using newlogpath /actlogs 
$ db2 update db cfg using mirrorlogpath /mirrorlogs 
$ db2 update db cfg using overflowlogpath /overflowlogs 
$ db2 terminate ; db2 connect to sample 
$ db2 get db cfg | grep -i log | grep -i path 
 Changed path to log files          (NEWLOGPATH) = 
 Path to log files                               = 
/actlogs/NODE0000/LOGSTREAM0000/ 
 Overflow log path             (OVERFLOWLOGPATH) = 
/overflowlogs/NODE0000/LOGSTREAM0000/ 
 Mirror log path                 (MIRRORLOGPATH) = 
/mirrorlogs/NODE0000/LOGSTREAM0000/ 
 Failover log archive path        (FAILARCHPATH) = 
 
$ db2pd -db sample -dbcfg | grep -i log | grep -i path 
NEWLOGPATH (memory) 
/mirrorlogs/NODE0000/LOGSTREAM0000/ 
NEWLOGPATH (disk) 
Path to log files (memory)     /actlogs/NODE0000/LOGSTREAM0000/ 
Path to log files (disk) 
OVERFLOWLOGPATH (memory)       /overflowlogs/ 
OVERFLOWLOGPATH (disk)         /overflowlogs/ 
MIRRORLOGPATH (memory)         /mirrorlogs/ 
MIRRORLOGPATH (disk)           /mirrorlogs/ 
 
NEWLOGPATH (memory) shows the mirrorlogpath. OVERFLOWLOGPATH and 
MIRRORLOGPATH don't include NODExxxx/LOGSTREAMxxxx.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using db2pd                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* This problem is not fixed in 10.1 release but will be fixed  * 
* in a future release.                                         * 
****************************************************************

Please refer 'get db cfg' output.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

02.07.2014
09.02.2017
09.02.2017