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

SET WRITE SUSPEND CAN TAKE SOME AMOUNT OF TIME EXTENDING/RENAMING LOG FILES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The DB2 "set write suspend" operation can take some amount of 
time extending/renaming log files. If you are performing "backup 
db <dbname> use snapshot ", you may notice some delay between 
"sqlpSuspendLog, probe:205" and "sqlubSuspendDatabase, 
probe:115" in db2diag.log. 
 
In the following sample db2diag.log, there is a delay about 30 
seconds: 
 
2012-04-12-13.30.43.198025+000 I86410A465         LEVEL: Warning 
PID     : 4457250              TID  : 144850      PROC : db2sysc 
1 
INSTANCE: db2inst              NODE : 001         DB   : SAMPLE 
APPHDL  : 0-64612              APPID: *N0.db2crt.120412132710 
AUTHID  : DB2SAM 
EDUID   : 144850               EDUNAME: db2agntp (SAMPLE) 1 
FUNCTION: DB2 UDB, data protection services, sqlpSuspendLog, 
probe:205 
DATA #1 : <preformatted> 
LSO at suspend time is 42664800656865 
 
........... 
 
2012-04-12-13.31.13.574383+000 E87679A448         LEVEL: Info 
PID     : 4457250              TID  : 144850      PROC : db2sysc 
1 
INSTANCE: db2inst             NODE : 001         DB   : SAMPLE 
APPHDL  : 0-64612              APPID: *N0.db2crt.120412132710 
AUTHID  : DB2SAM 
EDUID   : 144850               EDUNAME: db2agntp (SAMPLE) 1 
FUNCTION: DB2 UDB, database utilities, sqlubSuspendDatabase, 
probe:115 
MESSAGE : Backup has now suspended the database. 
 
If you perform "backup db <dbname> on all dbpartitionnums use 
snapshot " against an instance with large number of 
dbpartitions, it could lead to a long delay before database is 
suspended on all individual partitions.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in Version 10.1 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
17.11.2012
31.12.2012
31.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList