|
Problem IT08320
|
Status: Closed |
NATIVE ENCRYPTION: COMPRESS BACKUP PRODUCES COMPRESS_INTERNAL FAILED:RC 100 IN DB2DIAG.LOG. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Large number of errors like as below might be printed in the
db2diag.log if users backup a database with native encryption
and compress options.
2015-03-17-18.17.25.296119+540 I815853882E533 LEVEL:
Error
PID : 11119 TID : 140734158071552 PROC :
db2sysc 0
INSTANCE: db2inst1 NODE : 000 DB :
ENCDB
APPHDL : 0-111 APPID:
*LOCAL.db2inst1.150317090848
AUTHID : db2inst1 HOSTNAME: host01
EDUID : 1154 EDUNAME: db2bm.1031.0 (ENCDB) 0
FUNCTION: DB2 UDB, database utilities, Compress, probe:168
DATA #1 : String, 27 bytes
Compress_Internal failed:rc
DATA #2 : unsigned integer, 4 bytes
100 (= SQLUV_BUFFER_TOO_SMALL)
The following steps illustrate how to hit this condition.
db2 "update db cfg for ENCDB using ENCRLIB
<path_to_lib>/libdb2compr_encr.so ENCROPTS
'<encryption_options>'"
db2 "backup db ENCDB to <target_path> compress"
This error messages should not be printed in the db2diag.log
because the error has been recovered automatically and no user
intervention is required.
The backup image is healthy, and it can be used for restore
without problems. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who run backup with encrypt option. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 V10.5 FixPack 7 or later. *
**************************************************************** |
| Local Fix: |
Please ignore the error messages in the db2diag.log. |
| Solution |
This problem was first fixed in DB2 V10.5 FixPack 7. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.04.2015
08.02.2016
08.02.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
|
 |
