DB2 FOR LUW / DB2FORLUW / A10 - DB2

Backup with compress option might fail with 
 
SQL2079N  An error was reported by the shared library 
"db2compr.dll". 
Return code: "1". 
 
The following messages will be seen in the db2diag.log 
 
FUNCTION: DB2 UDB, database utilities, 
sqlubManageCompressedObject, probe:1002 
MESSAGE : Compression library returned tgtAct > tgtSize.  tgtAct 
/ tgtSize: 
DATA #1 : signed integer, 4 bytes 
127573 
DATA #2 : signed integer, 4 bytes 
127570    << Note these values could be different 
 
FUNCTION: DB2 UDB, database utilities, 
sqlubManageCompressedObject, probe:1006 
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes 
-2079 
DATA #2 : Hexdump, 21 bytes^M 
0x0000001661F90BF8 : E1F7 FFFF 6462 3263 6F6D 7072 2E64 6C6C 
....db2compr.dll 
0x0000001661F90C08 : 0001 0000 00 
..... 
 
FUNCTION: DB2 UDB, database utilities, 
sqlubManageCompressedObject, probe:1006 
MESSAGE : SQL2079N  An error was reported by the shared library 
"".  Return 
          code: "". 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -2079   sqlerrml: 
14 
 sqlerrmc: db2compr.dll 1 
 sqlerrp : sqlubMan 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00000000      (5) 0x00000000      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
 
Note this is a very rare case and unlikely to be hit. It is not 
the same as APAR IT03814 (note that in this APAR tgtSize value 
is < 5, example: 
MESSAGE : Compression library returned tgtAct > tgtSize.  tgtAct 
/ tgtSize: 
DATA #1 : signed integer, 4 bytes 
5 
DATA #2 : signed integer, 4 bytes 
3)

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 and Fix Pack 5                   * 
****************************************************************

Problem was first fixed in DB2 Version 10.1 and Fix Pack 5

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

13.03.2015
13.07.2015
13.07.2015