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

DB2 MAY CRASH AFTER A RESTORE DUE TO A TIMING HOLE

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
During a redirect restore, when there are attempts to connect to 
the database being restored, there is a small timing hole where 
stale data may be referenced internally by DB2 resulting in 
a crash. 
 
The problem is similar to APAR IC68207. 
 
The  crash usually shows db2diag.log messages similar to 
following : 
 
2012-06-07-09.56.21.319200-240 E3308486E427        LEVEL: Info 
PID     : 16349                TID  : 46921230051648PROC : 
db2sysc 1 
INSTANCE: <inst-name>             NODE : 001          DB   : 
<db-name> 
APPHDL  : 1-51699              APPID: <app-id> 
AUTHID  : <auth-id> 
EDUID   : 6165                 EDUNAME: db2agent (<db-name>) 1 
FUNCTION: DB2 UDB, database utilities, sqludrsa, probe:793 
MESSAGE : Restore Complete. 
 
2012-06-07-09.56.21.594829-240 I3308914E490        LEVEL: 
Warning 
PID     : 16349                TID  : 46921230051648PROC : 
db2sysc 1 
INSTANCE: <inst-name>             NODE : 001          DB   : 
<db-name> 
APPHDL  : 1-51699              APPID: <app-id> 
AUTHID  : <auth-id> 
EDUID   : 6165                 EDUNAME: db2agent (<db-name>) 1 
FUNCTION: DB2 UDB, RAS/PD component, 
pdEDUIsInDB2KernelOperation, probe:600 
DATA #1 : String, 12 bytes 
 _Z8sqlplfre 
DATA #2 : String, 4 bytes 
sqlp 
 
2012-06-07-09.56.21.595247-240 I3309405E566        LEVEL: Severe 
PID     : 16349                TID  : 46921230051648PROC : 
db2sysc 1 
INSTANCE: <inst-name>            NODE : 001          DB   : 
<db-name> 
APPHDL  : 1-51699              APPID: <app-id> 
AUTHID  : <auth-id> 
EDUID   : 6165                 EDUNAME: db2agent (<db-name>) 1 
FUNCTION: DB2 UDB, RAS/PD component, 
pdResilienceIsSafeToSustain, probe:800 
DATA #1 : String, 37 bytes 
Trap Sustainability Criteria Checking 
DATA #2 : Hex integer, 8 bytes 
0x0000000401003801 
DATA #3 : Boolean, 1 bytes 
false 
 
------------------------------------- 
 
The signal 11 stack will look  similar  to following  : 
 
0x00002AAAAC3D4524 _Z8sqlplfreP9sqeBsuEduP8SQLP_LCBP8SQLP_LRBm + 
0x01a8 
                (/var/ibmdb2/nytxt850/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAC3B273A _Z13sqlpTermAgentP9sqeBsuEdum + 0x0142 
                (/var/ibmdb2/nytxt850/sqllib/lib64/libdb2e.so.1) 
0x00002AAAABF6A050 _ZN8sqeAgent11AppDisassocEii + 0x02d0 
                (/var/ibmdb2/nytxt850/sqllib/lib64/libdb2e.so.1) 
0x00002AAAABF73B61 
_ZN14sqeApplication12AppStopUsingEP8sqeAgenthP5sqlca + 0x0acf 
                (/var/ibmdb2/nytxt850/sqllib/lib64/libdb2e.so.1) 
0x00002AAAABFCCA8C _Z11sqlesrspWrpP14db2UCinterface + 0x00b4 
                (/var/ibmdb2/nytxt850/sqllib/lib64/libdb2e.so.1) 
0x00002AAAABFCC6D7 sqleUCagentConnectReset + 0x00a1 
                (/var/ibmdb2/nytxt850/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAC0334D9 address: 0x00002AAAAC0334D9 ; dladdress: 
0x00002AAAAAEE4000 ; offset in lib: 0x000000000114F4D9 ; 
                (/var/ibmdb2/nytxt850/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAC030CC7 address: 0x00002AAAAC030CC7 ; dladdress: 
0x00002AAAAAEE4000 ; offset in lib: 0x000000000114CCC7 ; 
                (/var/ibmdb2/nytxt850/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAC030999 _Z17sqljsDrdaAsDriverP18SQLCC_INITSTRUCT_T + 
0x0111 
                (/var/ibmdb2/nytxt850/sqllib/lib64/libdb2e.so.1) 
0x00002AAAABF681EA _ZN8sqeAgent6RunEDUEv + 0x09ea 
                (/var/ibmdb2/nytxt850/sqllib/lib64/libdb2e.so.1) 
0x00002AAAAC615E72 _ZN9sqzEDUObj9EDUDriverEv + 0x00a8 
                (/var/ibmdb2/nytxt850/sqllib/lib64/libdb2e.so.1)
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users running restore                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The  problem is related to a timing hole  as described in    * 
* the   Error Description section of this APAR                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 2 or higher to avoid    * 
* experiencing this issue.                                     * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 10.1 Fix Pack 2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.11.2012
31.12.2012
31.12.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.2 FixList
10.5.0.2 FixList