|
Problem IC65807
|
Status: Geschlossen |
BACKUP MAY HANG DUE TO DB2VEND NOT BEING INITIALIZED |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
A backup process may hang under Solaris operating system because
one of the child db2vend process may be waiting to acquire an
AIO lock. This will only affect the backup processing. You can
identify this issue if the backup seems not to respond and by
running "db2ptree". The db2ptree will show some db2vend
processes started and others being db2sysc at the same tree
level
as highlighted with "<<<<<<<<<<<<<" in the output below:
5844 db2wdog 0
5845 db2sysc 0
5846 db2ckpwd 0
5847 db2ckpwd 0
5848 db2ckpwd 0
26338 db2vend (db2med - 1067 (ECA))
26339 db2vend (db2med - 1069 (ECA))
26340 db2vend (db2med - 1068 (ECA))
26341 db2vend (db2med - 1070 (ECA))
26342 db2vend (db2med - 1072 (ECA))
26343 db2sysc 0 <<<<<<<<<<<<<<<
26344 db2vend (db2med - 1071 (ECA))
26345 db2sysc 0 <<<<<<<<<<<<<<<
5933 db2acd 0
7506 db2fmp (C) 0
7720 db2fmp (idle) 0 |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All under Solaris operating system *
****************************************************************
* PROBLEM DESCRIPTION: *
* A backup process may hang under Solaris operating system *
* because one of the child db2vend process may be waiting to *
* acquire an AIO lock. This will only affect the backup *
* processing. You can identify this issue if the backup seems *
* not to respond and by running "db2ptree". The db2ptree will *
* show some db2vend processes started and others being db2sysc *
* at the same tree level as highlighted with "<<<<<<<<<<<<<" *
* in the output below: *
* *
* 5844 db2wdog *
* 05845 db2sysc *
* 05846 db2ckpwd *
* 05847 db2ckpwd *
* 05848 db2ckpwd *
* 026338 db2vend (db2med - 1067 (ECA)) *
* 26339 db2vend (db2med - 1069 (ECA)) *
* 26340 db2vend (db2med - 1068 (ECA)) *
* 26341 db2vend (db2med - 1070 (ECA)) *
* 26342 db2vend (db2med - 1072 (ECA)) *
* 26343 db2sysc 0 <<<<<<<<<<<<<<< *
* 26344 db2vend (db2med - 1071 (ECA)) *
* 26345 db2sysc 0 <<<<<<<<<<<<<<< *
* 5933 db2acd *
* 07506 db2fmp (C) *
* 07720 db2fmp (idle) 0 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 9.7 FP2 or above *
**************************************************************** |
| Local-Fix: |
Cancel the backup and retry might circumvent the issue. |
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
First fixed in DB2 version 9.7 FP2 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 25.01.2010
17.05.2010
17.05.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP2
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.2
|
 |
