home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC67526 Status: Geschlossen

ERROR "SQLUXCOMMITROLLBACKREQUEST" OCCURRED BEFORE ONLINE BACKUP
IS DONE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When running a backup on a heavily-loaded system, the backup's 
application state will change from "Performing a backup" to "UOW 
Executing" shortly after the backup starts.  This problem 
manifests itself in two ways. 
 
1. Querying the backup's application state by using LIST 
APPLICATIONS or a similar tool will show the backup's state as 
"UOW Executing" rather than the correct "Performing a backup". 
 
2. Near the end of the backup operation, a message similar to 
the following will be generated in the db2diag.log file: 
 
2010-01-13-11.24.16.724000-300 E40413F501        LEVEL: Error 
PID    : 3248                TID  : 3496        PROC : 
db2syscs.exe 
INSTANCE: DB2LR1              NODE : 000        DB  : LR1 
APPHDL  : 0-822                APPID: *LOCAL.DB2LR1.100113152600 
 
AUTHID  : SAPLR1 
EDUID  : 3496                EDUNAME: db2agent (LR1) 0 
FUNCTION: DB2 UDB, database utilities, 
sqluxCommitRollbackRequest, probe:1969 
MESSAGE : Unexpected application status 
DATA #1 : unsigned integer, 4 bytes 
3 
 
The error will typically occur when there is a lot of lock 
contention on the database.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All platforms.  Problem occurs when system is heavily        * 
* loaded.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When running a backup on a heavily-loaded system, the        * 
* backup's application state will change from "Performing a    * 
* backup" to "UOW Executing" shortly after the backup starts.  * 
* This problem manifests itself in two ways.                   * 
*                                                              * 
* 1. Querying the backup's application state by using LIST     * 
* APPLICATIONS or a similar tool will show the backup's state  * 
* as "UOW Executing" rather than the correct "Performing a     * 
* backup".                                                     * 
*                                                              * 
* 2. Near the end of the backup operation, a message similar   * 
* to the following will be generated in the db2diag.log file:  * 
*                                                              * 
* 2010-01-13-11.24.16.724000-300 E40413F501         LEVEL:     * 
* Error                                                        * 
* PID     : 3248                 TID  : 3496        PROC :     * 
* db2syscs.exe                                                 * 
* INSTANCE: DB2LR1               NODE : 000         DB   : LR1 * 
* APPHDL  : 0-822                APPID:                        * 
* *LOCAL.DB2LR1.100113152600                                   * 
* AUTHID  : SAPLR1                                             * 
* EDUID   : 3496                 EDUNAME: db2agent (LR1) 0     * 
* FUNCTION: DB2 UDB, database utilities,                       * 
* sqluxCommitRollbackRequest, probe:1969                       * 
* MESSAGE : Unexpected application status                      * 
* DATA #1 : unsigned integer, 4 bytes                          * 
* 3                                                            * 
*                                                              * 
* The problem will typically occur when there is a lot of lock * 
* contention on the database.                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* The problem does not lead to data loss or corruption of any  * 
* kind so it can be safely ignored.  Customers wishing to get  * 
* correct results from the monitor can upgrade to v9.7 fp2.    * 
****************************************************************
Local-Fix:
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
Fix is targeted for v9.7 fp2.  Backup will detect that the 
application state has changed to the wrong value and will set it 
back to the correct value.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC67549 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.03.2010
13.05.2010
13.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList