DB2 FOR LUW / DB2FORLUW / B10 - DB2

An online compressed and encrypted database 
backup that ran without errors might create a corrupted 
backup file.  There are no errors logged to indicate a failure, 
however, you may use the program db2ckbkp to check for corrupted 
backup files. 
 
Sample database BACKUP command: 
 
db2 "BACKUP DATABASE TEST ONLINE to /tmp/DB2Backup encrypt 
encrlib 'libdb2compr_encr.so' include logs without prompting" 
 
 
You will not be able to restore a database using the corrupted 
backup file.  A restore operation on a corrupted backup file 
will fail and the db2diag.log will have the following error 
logs: 
 
2016-08-11-04.27.43.521193-300 I3206096E595          LEVEL: 
Error 
PID     : 2271                 TID : 139739762255648 PROC : 
db2ckbkp 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: #### 
FUNCTION: DB2 UDB, bsu security, Decrypt, probe:1634 
MESSAGE : ZRC=0x870F00CD=-2029059891=SQLO_UNEXPECTED_SYSERR 
          "Unexpected System Error" 
CALLED  : DB2 Common, Cryptography, cryptDecryptBufferHP 
RETCODE : ECF=0x90000403=-1879047165=ECF_CRYPT_UNEXPECTED_ERROR 
          Unexpected cryptographic error 
DATA #1 : String, 27 bytes 
cryptDecryptBufferHP failed 
 
2016-08-11-04.27.43.524682-300 I3206692E967          LEVEL: 
Error 
PID     : 2271                 TID : 139739762255648 PROC : 
db2ckbkp 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: #### 
FUNCTION: DB2 UDB, bsu security, Decrypt, probe:1634 
MESSAGE : ZRC=0x870F00CD=-2029059891=SQLO_UNEXPECTED_SYSERR 
          "Unexpected System Error" 
DATA #1 : String, 27 bytes 
cryptDecryptBufferHP failed 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x00007F17C0A7EEC3 _Z7DecryptP8COMPR_CBPKciPciPiPjb + 
0x213 
  [1] 0x00007F1772517D0A Decompress + 0x6A 
  [2] 0x000000000041BB4D 
_Z19comprDumpDecompressPPcP7sqlubmhP7sqlubohPji + 0x5D 
  [3] 0x0000000000418D54 
_Z12verifyObjectP7sqlubmhP7sqlubohPcPjP15sqluExtractPagePKcS8_iP 
b + 0x1C34 
  [4] 0x0000000000414153 main + 0xEA3 
  [5] 0x0000003E56A1ED1D __libc_start_main + 0xFD 
  [6] 0x0000000000413219 __gxx_personality_v0 + 0x301 
 
2016-08-11-04.27.43.528550-300 I3207660E365          LEVEL: 
Error 
PID     : 2271                 TID : 139739762255648 PROC : 
db2ckbkp 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: #### 
FUNCTION: DB2 UDB, database utilities, Decompress, probe:431 
MESSAGE : Decrypt failed:rc 
DATA #1 : unsigned integer, 4 bytes 
2265907405

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to fix pack                                          * 
****************************************************************

There are two options: 
1) Do not use compression with encryption for your backup. 
Create an encrypted backup without compression. 
2) If the backup image you created is corrupted then you can 
retry the backup operation but it will require that the data in 
the database has changed sufficiently to alter the compressed 
data.  Hence, you will need to allow some database activities to 
occur before retrying the backup.

DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
 DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
 

See APAR Description

not known / see Local fix

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

02.09.2016
10.10.2017
10.10.2017