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

BACKUP TAKEN WITH NX842 COMPRESSION MIGHT REPORT GETMAXCOMPRESSEDSIZE
PROMISED THAT THIS BUFFER WOULD BE BIG ENOUGH

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
When taking a backup on AIX using NX842 comopression the
following message can be reported in the db2diag.log:

2019-09-30-14.58.56.794708+120 E1658977A643     LEVEL: Error
PID   : 22478944       TID : 10808     PROC : db2sysc 2
INSTANCE: db2jkl       NODE : 002      DB  : JKL
APPHDL : 2-104        APPID: *N2.db2jkl.190930125850
AUTHID : DB2JKL       HOSTNAME: hal9000
EDUID  : 10808        EDUNAME: db2bm.6169.0 (JKL) 2
FUNCTION: DB2 UDB, database utilities,
sqlubManageCompressedObject, probe:1737
DATA #?1 : String, 86 bytes
GetMaxCompressedSize promised that this buffer would be big
enough.
srcSize / tgtSize:
DATA #?2 : signed integer, 4 bytes
278
DATA #?3 : signed integer, 4 bytes
281

The backup is terminated and incomplete.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* All                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* None                                                         *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : 
follow-up : IT32063 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.10.2019
23.11.2020
23.11.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)