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 IC76458 Status: Geschlossen

POSSIBLE ONLINE BACKUP IMAGE CORRUPTION FROM PURE SCALE ENVIRONMENT

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
Online backup images from Pure Scale environment could be 
corrupted due to a synchronization issue.  Under heavy 
insert/update backup could read in partial pages due to the 
problem and making the image unusable.  The other symptoms of 
the problem 
is a logical error during online backup, which will cause 
database to crash.  The following db2diag.log messages will 
appear: 
 
2011-05-06-15.20.57.399651-240 E9576235A3102        LEVEL: 
Severe (OS) 
PID     : 20381722             TID  : 43500         KTID : 
32505951 
PROC    : db2sysc 0 
INSTANCE: DB2INST             NODE : 000         DB   : DB2DB 
APPHDL  : 0-1490               APPID: *N0.eunicec4.110506194324 
AUTHID  : DB2AUTH 
EDUID   : 43500                EDUNAME: db2bm.42985.2 (DB2DB) 0 
FUNCTION: DB2 UDB, SQO Latch Tracing, 
SQLO_SLATCH_CAS64::validate, probe:10 
MESSAGE : 
ZRC=0x870F00FB=-2029059845=SQLO_SLATCH_ERROR_HELDX_WITH_SHARED_H 
OLDERS 
          "shared latch found with both exclusive and shared 
holders.  Latch likely corrupt."
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Pure Scale                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Online backup images from Pure Scale environment could be    * 
*                                                              * 
* corrupted due to a synchronization issue.  Under heavy       * 
*                                                              * 
* insert/update backup could read in partial pages due to the  * 
*                                                              * 
* problem and thereby unusable.  The other symptoms of the     * 
* problem                                                      * 
* is a logical error during online backup, which will cause    * 
*                                                              * 
* database to come down.  The following db2diag.log messages   * 
* will                                                         * 
* appear:                                                      * 
*                                                              * 
*                                                              * 
*                                                              * 
* 2011-05-06-15.20.57.399651-240 E9576235A3102        LEVEL:   * 
*                                                              * 
* Severe (OS)                                                  * 
*                                                              * 
* PID    : 20381722            TID  : 43500        KTID :      * 
* 32505951                                                     * 
*                                                              * 
* PROC    : db2sysc 0                                          * 
*                                                              * 
* INSTANCE: DB2INST            NODE : 000        DB  : DB2DB   * 
* APPHDL  : 0-1490              APPID:                         * 
* *N0.eunicec4.110506194324                                    * 
* AUTHID  : DB2AUTH                                            * 
*                                                              * 
* EDUID  : 43500                EDUNAME: db2bm.42985.2 (DB2DB) * 
* 0                                                            * 
* FUNCTION: DB2 UDB, SQO Latch Tracing,                        * 
*                                                              * 
* SQLO_SLATCH_CAS64::validate, probe:10                        * 
*                                                              * 
* MESSAGE :                                                    * 
*                                                              * 
* ZRC=0x870F00FB=-2029059845=SQLO_SLATCH_ERROR_HELDX_WITH_SHARED 
* OLDERS                                                       * 
*                                                              * 
*           "shared latch found with both exclusive and shared * 
*                                                              * 
* holders.  Latch likely corrupt."                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Temporary workaround would be to use offline backup instead  * 
* of online backup.                                            * 
*                                                              * 
* Upgrade to v98 fp4 for the fix of the problem.               * 
****************************************************************
Local-Fix:
1. Use offline backup instead of online backup 
2. upgrade to v98 fp4 
3. contact DB2 service for other possible workaround.
verfügbare FixPacks:
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Lösung
v98 fp4
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.05.2011
29.07.2011
29.07.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.FP4
Problem behoben lt. FixList in der Version
9.8.0.4 FixList