DB2 FOR LUW / DB2FORLUW / A10 - DB2

When restoring into an existing database, currently only the 
logfiles are deleted, but the TAG file will be left untouched in 
the log path. This can lead to issues during a rollforward of 
the newly rerstored database later on. The following messages 
can be found in the db2diag.log file: 
 
2014-03-15-11.11.07.807357+000 E31795340A519 LEVEL: Error 
PID : 17760344 TID : 4113 PROC : db2sysc 0 
INSTANCE: xxxxxx NODE : 000 DB : yyy 
APPHDL : 0-8 APPID: *LOCAL.xxxxxx.140315111107 
AUTHID : xxxxxx HOSTNAME: zzzzzz 
EDUID : 4113 EDUNAME: db2agent (yyy) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgUseCurrentPath, probe:2660 
MESSAGE : ADM1814E The current log path "/db2/yyy/log_dir/" is 
invalid. 
 
2014-03-15-11.11.07.807967+000 E31795860A573 LEVEL: Error 
PID : 17760344 TID : 4113 PROC : db2sysc 0 
INSTANCE: xxxxxx NODE : 000 DB : yyy 
APPHDL : 0-8 APPID: *LOCAL.xxxxxx.140315111107 
AUTHID : xxxxxx HOSTNAME: zzzzzz 
EDUID : 4113 EDUNAME: db2agent (yyy) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgUseCurrentPath, probe:2960 
MESSAGE : ADM1811E DB2 will now switch to the default log path 
"/db2/yyy/xxxxxx/NODE0000/SQL00001/LOGSTREAM0000/". 
 
This APAR will delete the TAG file in addition to the log files, 
when these files belong to the database being overwritten by 
the restore. If these files do not belong to the overwritten 
database, an error will be returned instead.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 5.                      * 
****************************************************************

Manually remove the TAG file from the log path.

First fixed in DB2 Version 10.1 Fix Pack 5.

not known / see Local fix

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

23.05.2014
17.07.2015
17.07.2015