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

SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY PROCEDURE AFFECTS REGULAR TABLES
THAT ARE DEFINED WITH GENERATED COLUMNS

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
When running the procedure 
SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY against a table that 
contains the columns ROW BEGIN , ROW END AND TRANSACTION START 
ID, even though this is not a temporal table, the procedure will 
enable write activity to these columns. 
 
You can check if the table isn't considered as "temporal" by 
running the query below: 
 
db2 "select temporaltype from syscat.tables where 
tabname='NONTEMPORAL_POLICY_INFO'" 
 
        TEMPORALTYPE 
 
        ------------ 
 
        N 
 
This behavior isn't correct since this procedure should affect 
only temporal tables. So this APAR is to fix it.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all LUW                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v105fp7                                           * 
****************************************************************
Local-Fix:
N/A
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
29.01.2015
19.01.2016
19.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList