DB2 FOR LUW / DB2FORLUW / A50 - DB2

A Redirected Restore may cause EACCES (13) "Permission denied" 
errors in db2diag.log if the source and target database are 
located on the same machine. The SET TABLESPACE CONTAINERS 
statement might attempt to access the old container paths from 
the source database/instance. In such a case you may observe the 
following messages in db2diag.log: 
 
2014-02-03-21.05.08.457378+060 E159544A1190         LEVEL: Error 
(OS) 
PID     : 11928422             TID : 11567          PROC : 
db2sysc 0 
INSTANCE: db2inst4             NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-46                 APPID: 
*LOCAL.db2inst4.140203200227 
AUTHID  : DB2INST4             HOSTNAME: localhost 
EDUID   : 11567                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, oper system services, sqloopenp, probe:80 
MESSAGE : ZRC=0x840F0001=-2079391743=SQLO_ACCD "Access Denied" 
          DIA8701C Access denied for resource "", operating 
system return code 
          was "". 
CALLED  : OS, -, open 
OSERR   : EACCES (13) "Permission denied" 
DATA #1 : Codepath, 8 bytes 
4:11:18:20:24:40 
DATA #2 : File name, 38 bytes 
/db/data1/db2inst3/syscat.cont 
DATA #3 : SQO Open File Options, PD_TYPE_SQO_FILE_OPEN_OPTIONS, 
4 bytes 
SQLO_REVISE, SQLO_READWRITE, SQLO_SHAREWRITE, 
SQLO_FORCE_NON_BUFFERED, SQLO_WRITETHRU 
DATA #4 : Hex integer, 4 bytes 
0x00000180 
DATA #5 : signed integer, 4 bytes 
DATA #6 : Hex integer, 4 bytes 
0x08000080 
DATA #7 : String, 105 bytes 
Search for ossError*Analysis probe point after this log entry 
for further 
self-diagnosis of this problem. 
 
This error message can be ignored and the subsequent restore 
should be successful.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5.                      * 
****************************************************************

First fixed in DB2 Version 10.5 Fix Pack 5.

not known / see Local fix

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

11.03.2014
13.03.2015
13.03.2015