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

LOG REPLAY FAILS WITH DB2DIAG.LOG MESSAGE SQLDLOADTCB, PROBE:10553
ZRC=SQLD_REC_DELETED "DELETED RECORD ID"

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
During replay of certain log records generated by Data 
Definition Language (DDL) statements, depending on the 
recovery window, DB2 may fail with a message similar to the 
following being written to the db2diag.log: 
 
2015-08-26-19.39.09.225529-240 I1668        LEVEL: Severe 
PID     : 7536700          TID : 8740           PROC : db2sysc 0 
INSTANCE: svtdbm          NODE : 000           DB   : HADRDB 
APPHDL  : 0-8                APPID: *LOCAL.DB2.150826233212 
HOSTNAME: tempsvt02 
EDUID   : 8740                EDUNAME: db2redom (HADRDB) 0 
FUNCTION: DB2 UDB, data management, sqldLoadTCB, probe:10553 
RETCODE : ZRC=0x8704007A=-2029780870=SQLD_REC_DELETED "DELETED 
RECORD ID" 
 
The recovery window must contain log records for operations on a 
multidimensional clustering (MDC) table, the DROP TABLE log 
record for that table, a CREATE TABLE for a non-MDC table that 
reuses the same table id and tablespace id as the former MDC 
table, followed by a REORG on that new table.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest fix pack.                              * 
****************************************************************
Local-Fix:
Lösung
Problem is first fixed in DB2 UDB version 10.5 fix pack 7.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
28.09.2015
20.01.2016
20.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList