DB2 FOR LUW / DB2FORLUW / A10 - DB2

When performing a Restore-TRANSPORT operation using a 
backup-image created from a database with log-archiving enabled, 
the staging database will inherit the log-archive configuration. 
Since some of the activity performed on the staging database 
during the Restore-TRANSPORT generates log records, it's 
possible for the staging database to archive log files (using 
the archive log path inherited from the backup image, which it 
may not have access to).  This will fail and cause the 
Restore-TRANSPORT operation to fail with an SQL2590N error, like 
the db2diag.log entry below: 
 
INSTANCE: target_inst              NODE : 000        DB  : 
SYSTG001 
APPHDL  : 0-20                APPID: 
*LOCAL.target_inst.100816163356 
FUNCTION: DB2 Common, OSSe, ossErrorIOAnalysis, probe:100 
CALLED  : OS, -, mkdir 
OSERR  : EACCES (13) "Permission denied" 
DATA #1 : String, 126 bytes 
A total of 2 analysis will be performed : 
- User info 
- Path access permission 
Target file = /db1/source_inst/archlog/target_inst

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V101 FP3                                      * 
****************************************************************

After the first phase of the Restore-TRANSPORT operation is 
complete, before updating container paths and continuing the 
Restore, you can connect to the staging database and disable 
log-archiving (LOGARCHMETH1) by using following command: 
db2 "update db cfg for <dbname> using logarchmeth1 off"

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
 

First Fixed in DB2 V101 FP3

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

22.04.2013
08.10.2013
08.10.2013