DB2 - Problem description
Problem IC84269 | Status: Closed |
ADD LOGFILE EXTENT NUMBER TO SQLPSUSPENDLOG MESSAGE | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
When doing flash copy backups, customers need to know, which is the last logfile they need to copy. Currently the following message is written to db2diag.log: 2011-11-09-17.54.47.336913+060 I34322068A467 LEVEL: Warning PID : 1475 TID : 968 PROC : db2sysc 0 INSTANCE: db2isp NODE : 000 DB : ISP APPHDL : 0-25753 APPID: *LOCAL.db2isp.111109165607 AUTHID : DB2ISP EDUID : 968 EDUNAME: db2agent (ISP) 0 FUNCTION: DB2 UDB, data protection services, sqlpSuspendLog, probe:205 DATA #1 : <preformatted> LSO at suspend time is 8578776072529 As LSOs are not transparent to customers, the log number should be added too for serviceability reasons. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 1. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 10.1 Fix Pack 1. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.06.2012 07.11.2012 07.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |