Users that run DB2 on Windows will see severe error messages,
similar to the ones shown below, in their db2diag.log file when
performing different DB2 operations, such as database creation,
database activation/first connect or tablespace creation, to
name a few.
2011-11-01-14.09.42.583000-240 I1603H1240 LEVEL: Error
(OS)
PID : 4320 TID : 5904 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : MYDB
APPHDL : 0-8614 APPID: *LOCAL.DB2.111101180938
AUTHID : DBUSER
EDUID : 5904 EDUNAME: db2agent (MYDB) 0
FUNCTION: DB2 Common, OSSe, ossPathTest, probe:40
MESSAGE : ECF=0x90000007=-1879048185=ECF_UNKNOWN
Unknown
CALLED : OS, -, access
OSERR : 123 "The filename, directory name, or volume label
syntax is incorrect."
DATA #1 : String, 43 bytes
D:\DB2\NODE0000\MYDB\T0000000\C0000000.CAT\
DATA #2 : Hex integer, 4 bytes
0x00000001
DATA #3 : Hex integer, 4 bytes
0x00000000
DATA #4 : signed integer, 4 bytes
0
CALLSTCK:
[0] 0x6CD3B12A pdOSSeLoggingCallback + 0x216
[1] 0x6D290C84 ossLogSysRC + 0xB4
[2] 0x6D28E99F ossSystemErrorHandler + 0x137
[3] 0x6D2761F9 ossPathTest. + 0x17F
[4] 0x6D27600F ossPathExists + 0x35
[5] 0x6D2819F4 ossGetDiskInfo + 0x2EE
[6] 0x6CC996B4 sqloFetchAndStoreFSInfoInFileHandle + 0xFC
[7] 0x6D5BD318 sqlbFetchAndStoreContainerFSInfo + 0x3E
[8] 0x6D62D2A2 sqlbDMSStartPool + 0x128
[9] 0x6D5D0BEE sqlbStartPools + 0x1FA
2011-11-01-14.09.42.583000-240 I2845H591 LEVEL: Severe
PID : 4320 TID : 5904 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : MYDB
APPHDL : 0-8614 APPID: *LOCAL.DB2.111101180938
AUTHID : DBUSER
EDUID : 5904 EDUNAME: db2agent (MYDB) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbFetchAndStoreContainerFSInfo, probe:10
MESSAGE : ECF=0x9000001A=-1879048166=ECF_FILE_DOESNT_EXIST
File doesn't exist
DATA #1 : File name, 42 bytes
D:\DB2\NODE0000\MYDB\T0000000\C0000000.CAT
2011-11-01-14.09.42.599000-240 I3438H1212 LEVEL: Error
(OS)
PID : 4320 TID : 5904 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : MYDB
APPHDL : 0-8614 APPID: *LOCAL.DB2.111101180938
AUTHID : DBUSER
EDUID : 5904 EDUNAME: db2agent (MYDB) 0
FUNCTION: DB2 Common, OSSe, ossPathTest, probe:40
MESSAGE : ECF=0x90000007=-1879048185=ECF_UNKNOWN
Unknown
CALLED : OS, -, access
OSERR : 123 "The filename, directory name, or volume label
syntax is incorrect."
DATA #1 : String, 43 bytes
D:\DB2\NODE0000\MYDB\T0000000\C0000000.CAT\
DATA #2 : Hex integer, 4 bytes
0x00000001
DATA #3 : Hex integer, 4 bytes
0x00000000
DATA #4 : signed integer, 4 bytes
0
CALLSTCK:
[0] 0x6CD3B12A pdOSSeLoggingCallback + 0x216
[1] 0x6D290C84 ossLogSysRC + 0xB4
[2] 0x6D28E99F ossSystemErrorHandler + 0x137
[3] 0x6D2761F9 ossPathTest. + 0x17F
[4] 0x6D27600F ossPathExists + 0x35
[5] 0x6D2819F4 ossGetDiskInfo + 0x2EE
[6] 0x6D621B2B sqlbCountContsOnCriticalPaths + 0x2B5
[7] 0x6D62D55E sqlbDMSStartPool + 0x3E4
[8] 0x6D5D0BEE sqlbStartPools + 0x1FA
[9] 0x6D5BA61F sqlbinit + 0x5DD
2011-11-01-14.09.42.599000-240 I4652H738 LEVEL: Severe
PID : 4320 TID : 5904 PROC :
db2syscs.exe
INSTANCE: DB2 NODE : 000 DB : MYDB
APPHDL : 0-8614 APPID: *LOCAL.DB2.111101180938
AUTHID : DBUSER
EDUID : 5904 EDUNAME: db2agent (MYDB) 0
FUNCTION: DB2 UDB, buffer pool services,
sqlbCountContsOnCriticalPaths, probe:30
MESSAGE : Could not get fsID info for container
DATA #1 : File name, 42 bytes
D:\DB2\NODE0000\MYDB\T0000000\C0000000.CAT
DATA #2 : unsigned integer, 4 bytes
2415919130
DATA #3 : unsigned integer, 4 bytes
2415919106
DATA #4 : Pool ID, PD_TYPE_SQLB_POOL_ID, 2 bytes
0
DATA #5 : unsigned integer, 4 bytes
0
These severe error messages report containers as not existing
even though the containers do exist in their respective paths.
The reporting of these messages is caused by a bug in DB2. |
