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

About HADR: Copy logs from the old log path to new log path

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The following record in db2diag.log is might be incorrect. 
 
2015-01-08-20.13.23.398486+540 I60707907A733        LEVEL: Info 
PID     : 11207144             TID : 3343           PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
DBNAME 
APPHDL  : 0-7                  APPID: 
*LOCAL.db2inst1.150108111323 
AUTHID  : DB2INST1             HOSTNAME: HOSTNAME 
EDUID   : 3343                 EDUNAME: db2agent (DB2INST1) 0 
FUNCTION: DB2 UDB, data protection services, 
sqlpgSwitchToNewLogPath, probe:4240 
MESSAGE : HADR: Copy logs from the old log path to new log path 
DATA #1 : String, 45 bytes 
/home/db2inst1/db2inst1/LOG1b/NODE0000/LOGSTREAM0000/ 
DATA #2 : String, 53 bytes 
/home/db2inst1/db2inst1/db2inst1/NODE0000/SQL00001/LOGSTREAM0000 
/ 
DATA #3 : SQLPG_EXTENT_NUM, PD_TYPE_SQLPG_EXTENT_NUM, 4 bytes 
4409 
 
 
There are two problems in this record. 
 
1. The string "HADR" is not necessary for this record. 
2. The destination path where the log files are copied is 
incorrectly set to the default to log path.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Server users.                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2  version 10.1.0.5.                            * 
****************************************************************
Local Fix:
Not available.
Solution
The problem is first fixed in DB2 version 10.1.0.5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
21.01.2015
21.07.2015
21.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList