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

SILENT SWITCH TO THE DEFAULT LOGPATH PATH

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
DB2 changes log file location (LOGPATH) to the default path if 
the configured LOGPATH is not accessible or wrong log files are 
found. 
This change is performed without notification to the application 
or user-entered command (database activation or first connet). 
 
The default LOGPATH for a DB2 v10.1 database looks like: 
 /home/dbuser/dbinst/NODE0000/SQL00001/LOGSTREAM0000 
 
This change of the log path potentially causes issues during 
subsequent database operation as the default location will very 
likely lack the amount of disk space to hold all log files.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 FixPack 4                        * 
****************************************************************
Local Fix:
available fix packs:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Solution
First fixed in DB2 version 10.5 FixPack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.02.2014
09.09.2014
09.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList