DB2 - Problembeschreibung
Problem IC99737 | Status: Geschlossen |
DATABASE MIGRATION TO V10 CAN TAKE A LONG TIME TO COMPLETE, WHILE V10 LOGFILES ARE ALLOCATED IN BACKGROUND | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
Database migration to V10 can take a long time, while V10 logfiles are allocated in background. Most of the time is spent in db2spcat during internal savepoint rollbacks, waiting on db2loggr. Start and stop time of db2spcat utility are reported in db2diag.log file: 2014-02-14-16.50.06.010613+060 I2698103A350 LEVEL: Warning PID : 57802888 TID : 1 PROC : db2bp INSTANCE: xxxxx NODE : 000 DB : yyyyy APPID : *LOCAL.xxxxx.140214154911 HOSTNAME: zzzzz EDUID : 1 FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:556 MESSAGE : Begin db2spcat ... 2014-02-14-16.57.23.893435+060 I25190485A374 LEVEL: Warning PID : 57802888 TID : 1 PROC : db2bp INSTANCE: xxxxx NODE : 000 DB : yyyyy APPID : *LOCAL.xxxxx.140214154911 HOSTNAME: zzzzz EDUID : 1 FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:563 MESSAGE : End db2spcat: with rc = 0, sqlcode = 0 | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 4. * **************************************************************** | |
Local-Fix: | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 10.1 Fix Pack 4. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC99738 Nachfolger : | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 28.02.2014 23.06.2014 23.06.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 |