This is a file permission problem. Did you recreate your db2 users or
change file permission on your directories? Perhaps the db2diag.log
can tell you which file/directory is giving you a problem.
What I found doesn't tell me much:
'Access denied for resource "", operating system return code was "".'
Here's a full log entry:
2007-02-05-06.54.46.125000-480 I3624H268 LEVEL: Warning
PID : 1284 TID : 3604 PROC : db2bp.exe
INSTANCE: DB2 NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqlemgdb, probe:10
MESSAGE : Begin engn migration
2007-02-05-06.54.46.171000-480 I3894H729 LEVEL: Severe
PID : 1664 TID : 4068 PROC : db2syscs.exe
INSTANCE: DB2 NODE : 000
APPHDL : 0-7 APPID: *LOCAL.DB2.070205145446
AUTHID : HANSHORN
FUNCTION: DB2 UDB, data protection services, sqlpMigrate, probe:10
MESSAGE : ZRC=0x840F0001=-2079391743=SQLO_ACCD "Access Denied"
DIA8701C Access denied for resource "", operating system return
code
was "".
DATA #1 : String, 35 bytes
Unable to migrate LFH and MFH files
DATA #2 : unsigned integer, 4 bytes
16
DATA #3 : unsigned integer, 4 bytes
4294967295
DATA #4 : Pointer, 4 bytes
0x00000000
DATA #5 : Pointer, 4 bytes
0x00000000
> This is a file permission problem. Did you recreate your db2 users or
> change file permission on your directories? Perhaps the db2diag.log
> can tell you which file/directory is giving you a problem.
Serge Rielau - 05 Feb 2007 19:49 GMT
> What I found doesn't tell me much:
> 'Access denied for resource "", operating system return code was "".'
[quoted text clipped - 30 lines]
>> change file permission on your directories? Perhaps the db2diag.log
>> can tell you which file/directory is giving you a problem.
Well that's actually limits the scope of the problem by quite a bit...
"Unable to migrate LFH and MFH files"
http://publib.boulder.ibm.com/infocenter/db2luw/v9/topic/com.ibm.db2.udb.admin.d
oc/doc/c0005420.htm
Cheers
Serge

Signature
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab