home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT06840 Status: Closed

SET_MAINT_MODE_RECORD_NO_TEMPORALHISTORY PROCEDURE AFFECTS REGULAR TABLES
THAT ARE DEFINED WITH GENERATED COLUMNS

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
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 Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all LUW                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v105fp7                                           * 
****************************************************************
Local Fix:
N/A
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.01.2015
19.01.2016
19.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList