|
Problem IT40442
|
Status: Closed |
ON AIX GETMAXCOMPRESSEDSIZE MIGHT RETURN A TOO LOW VALUE
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
When using ZLIB based backup or log file compression,
GetMaxCompressedSize part of libdb2zcompr.a /
libdb2zcompr_encr.a might return a too low value, which can lead
to errors when performing compressed backups.
Pre-requisite is that HW acceleration is enabled.
nxstat -S
returns
nx_accel_mask = 1
GZIP accelerator available
in this case.
A backup will fail with
SQL2079N An error was reported by the shared library
"libdb2zcompr.a".
Return code: "1".
And in the db2diag.log you can find entries like:
2022-03-30-10.08.00.005280-240 E11531A688 LEVEL: Error
PID : 21365128 TID : 6862 PROC :
db2sysc
INSTANCE: db2inst1 NODE : 000 DB :
SAMPLE
APPHDL : 0-157 APPID:
*LOCAL.db2inst1.220330140759
AUTHID : USER1 HOSTNAME: myhost1
EDUID : 6862 EDUNAME: db2bm.2493.2 (SAMPLE)
FUNCTION: DB2 UDB, database utilities,
sqlubManageCompressedOrdinaryObject, probe:1671
DATA #1 : String, 86 bytes
GetMaxCompressedSize promised that this buffer would be big
enough.
srcSize / tgtSize:
DATA #2 : signed integer, 4 bytes
425984
DATA #3 : signed integer, 4 bytes
433867 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* AIX Power9/10 users using zlib backup or log file *
* compression. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 v11.5.8 *
**************************************************************** |
| Local Fix: |
n/a |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* AIX Power9/10 users using zlib backup or log file *
* compression. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 v11.5.8 *
**************************************************************** |
| Comment |
Fix will be included in Db2 v11.5.8. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.03.2022
09.04.2022
10.04.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
