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 IC84351 Status: Closed

DATA BUFFER IN LIST HISTORY COMMAND IS ALWAYS DISPLAYED AS 0

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Problem Description: 
 
DATA BUFFER in LIST HISTORY COMMAND is always displayed as 0. 
 
For example using a simple load in DB2 9.7 
 
db2 load from org.del of del insert into org data buffer 888 
 
the list history command shows 0 data buffers: 
 
Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log 
Backup ID 
 -- --- ------------------ ---- --- ------------ ------------ 
-------------- 
  L  T  20110920142858001   I    I  S0000000.LOG S0000000.LOG 
 --------------------------------------------------------------- 
------------- 
  "DIMITRI "."ORG" resides in 1 tablespace(s): 
 
  00001 IBMDB2SAMPLEREL 
 --------------------------------------------------------------- 
------------- 
    Comment: DB2 
 Start Time: 20110920142858 
   End Time: 20110920142859 
     Status: A 
 --------------------------------------------------------------- 
------------- 
  EID: 18 Location: DB2 Autoloader. Data was partitioned on 2 
node(s), and loaded on node 1. 
 
 DDL: OFFLINE LOAD DEL AUTOMATIC INDEXING INSERT COPY NO DIMITRI 
.ORG, CPU_PARALLELISM [1], DISK_PARALLELISM [1], DATA BUFFER 
[0], TEMPFILES PATH 
[/home/dimitri/dimitri/NODE0001/SQL00001/load/DB200003.PID/DB200 
005.OID], 
DUMPFILE [none] 
 --------------------------------------------------------------- 
-------------
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP1.                                     * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
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

Solution
Problem was first fixed in DB2 10.1 FP1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
01.11.2012
01.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList