DB2 - Problembeschreibung
Problem IT06297 | Status: Geschlossen |
SLOW PERFORMANCE OF UPDATE AND INSERT LOB TRANSACTIONS AFTER STOPPING ONE OR MORE MEMBERS ON A PURESCALE SYSTEM | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
The update and insert LOB transactions are getting slower while the other transactions are working properly, after the LOB transactions including update or insert transactions run then one or more members stop by "db2stop force xx" or even by "db2stop xx quiesce -1". During this issue, the logical page reads for the LOB transactions are much increased and it will go on until the databases are recovered on the stopped members. The increasing logical page reads can be monitored through mon_get_pkg_cache_stmt metric function, db2pd -bufferpools, or application snapshot outputs. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * pureScale user * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to db2 Version 10.5 FixPack 7 or higher * **************************************************************** | |
Local-Fix: | |
To recover this symptom, the database needs to be restarted on the stopped member. 1. db2start the member again. 2. initiate a connection to the database locally, and reset connection before new transactions run. 3. db2stop the member again. Note: DB2COMM repository variable may need to be cleared on the member to constrain new connections from the remote applications during applying the workaround. | |
Lösung | |
Problem was first fixed in Version 10.5 FixPack 7 | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 04.01.2015 22.01.2016 22.01.2016 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.7 |