DB2 FOR LUW / DB2FORLUW / A10 - DB2

If the user tries to restore a database from a backup image and 
transaction log files archived using a vendor library and later 
extracted to the disk, and if the vendor library cannot be 
initialized, then the restore will fail with SQL2071N, and the 
entire restore operation will be terminated. 
. 
This will cause problems for example in cases where the backup 
image is created on a machine with the vendor library 
configured, but the restore needs to be performed out on a 
different machine where the vendor code does not exist. 
. 
Sample steps to reproduce: 
. 
1) update LOGARCHMETH1 or LOGARCHMETH2 to TSM 
2) take a backup 
3) try to restore the backup on a system where there is 
   something wrong with sqllib/adsm/libtsm.a (e.g. missing) 
. 
The entire restore operation will be rolled back. 
. 
Example: 
. 
* db2sampl 
* db2 update db cfg for sample using LOGARCHMETH1 TSM 
* db2 backup db sample 
* db2 drop db sample 
* <rename sqllib/adsm/libtsm.a to sqllib/adsm/libtsm.a.old> 
* db2 restore db sample 
. 
SQL2071N  An error occurred while accessing the shared library 
"/home/db2inst1/sqllib/adsm/libtsm.a". Reason code: "2". 
. 
The purpose of this APAR is make DB2 independent on the 
original vendor location if all of the data necessary to 
carry out a successful restore, i.e. the backup image and the 
log files, is already present on the disk.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users running DB2 v10.1 FP2 or earlier.                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 FP3.                                    * 
****************************************************************

Fix the vendor initialization problems on the target machine 
where the restore should be performed, or (temporarily) 
disable vendor code on the source machine before the backup 
is taken, so that the backup image does not contain any 
information about the vendor library. 
. 
Upgrading to a FixPak containing this fix will cause that the 
SQL2071N error will be ignored during the restore, i.e. the 
error will not be returned to the end user. At the end of the 
successful restore the user will have an opportunity to set 
LOGARCHMETH1 and LOGARCHMETH2 to new values.

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

The problem was first fixed in DB2 v10.1 FP3.

Fix the vendor initialization problems on the target machine 
where the restore should be performed, or (temporarily) 
disable vendor code on the source machine before the backup 
is taken, so that the backup image does not contain any 
information about the vendor library. 
 
Upgrading to a FixPak containing this fix will cause that the 
SQL2071N error will be ignored during the restore, i.e. the 
error will not be returned to the end user. At the end of the 
successful restore the user will have an opportunity to set 
LOGARCHMETH1 and LOGARCHMETH2 to new values.

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

28.05.2013
27.09.2013
27.09.2013