Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84344 Status: Closed

DB2 CREATE TABLESPACE COMMAND CAN CRASH THE INSTANCE IF THE CONTAINER PATH
DOES NOT EXIST.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When the file specified in the create table space command refers 
to a link and not the actual file and if the link exists but not 
the actual file then db2 instance can trap with following 
symptoms. 
 
db2diag.log snippet: 
-------------------- 
2011-09-20-16.17.16.100234-300 E4124880A852       LEVEL: Error 
(OS) 
PID     : 42594                TID  : 29889       PROC : db2sysc 
42 
INSTANCE: xxxxx              NODE : 042         DB   : xxxxxx 
APPHDL  : 0-37769              APPID: *N0.tedpi01.110920211716 
AUTHID  : xxxxxx 
EDUID   : 29889                EDUNAME: db2agntp (xxxxxxx) 42 
FUNCTION: DB2 UDB, oper system services, sqlomkdirp, probe:10 
MESSAGE : ZRC=0x870F000A=-2029060086=SQLO_FEXS "file already 
exists" 
          DIA8722C A file already exists. 
CALLED  : OS, -, mkdir 
OSERR   : EEXIST (17) "File exists" 
DATA #1 : File name, 32 bytes 
/opt/udb/tedpi01/data/data001_41 
DATA #2 : signed integer, 4 bytes 
457 
DATA #3 : signed integer, 4 bytes 
457 
DATA #4 : String, 105 bytes 
Search for ossError*Analysis probe point after this log entry 
for further 
self-diagnosis of this problem. 
 
2011-09-20-16.17.16.111165-300 E4125733A876       LEVEL: Error 
(OS) 
PID     : 42594                TID  : 29889       PROC : db2sysc 
42 
INSTANCE: xxxxxx              NODE : 042         DB   : xxxxxx 
APPHDL  : 0-37769              APPID: *N0.tedpi01.110920211716 
AUTHID  : xxxxxxx 
EDUID   : 29889                EDUNAME: db2agntp (xxxxxx) 42 
FUNCTION: DB2 UDB, oper system services, sqlomkdirp, probe:10 
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." 
          DIA8411C A file "" could not be found. 
CALLED  : OS, -, mkdir 
OSERR   : ENOENT (2) "No such file or directory" 
DATA #1 : File name, 40 bytes 
/opt/udb/tedpi01/data/data001_41/tedpi01 
DATA #2 : signed integer, 4 bytes 
457 
DATA #3 : signed integer, 4 bytes 
457 
DATA #4 : String, 105 bytes 
Search for ossError*Analysis probe point after this log entry 
for further 
self-diagnosis of this problem. 
 
and the following stack trace in the trap file generated: 
 
<StackTrace> 
-------Frame------ ------Function + Offset------ 
0x090000000008371C pthread_kill + 0x88 
0x090000000EC867A8 sqloDumpEDU + 0x54 
0x090000000F36DD64 MarkDBBad__16sqeLocalDatabaseFi + 0x344 
0x090000000E4FB4B0 MarkDBBad__16sqeLocalDatabaseFi@glue293 + 
0x78 
0x090000000F16DAD0 sqlrr_rds_common_post__FP14db2UCinterfaceiT2l 
+ 0x98 
0x090000000E96647C sqlrr_commit__FP14db2UCinterface + 0x94 
0x090000000F0D08C0 
sqljs_ddm_rdbcmm__FP14db2UCinterfaceP13sqljDDMObject + 0x150 
0x090000000F0D06E8 
sqljsParseRdbAccessed__FP13sqljsDrdaAsCbP13sqljDDMObjectP14db2UC 
interface 
+ 0xC 
0x090000000F0BB804 
.sqljsParse.fdpr.clone.116__FP13sqljsDrdaAsCbP14db2UCinterfaceP8 
sqeAgentb 
+ 0x260 
0x090000000F0FE440 @64@sqljsSqlam__FP14db2UCinterfaceP8sqeAgentb 
+ 0xACC 
0x090000000F2479BC 
@64@sqljsDriveRequests__FP8sqeAgentP14db2UCconHandle + 0xEC 
0x090000000F2477CC 
@64@sqljsDrdaAsInnerDriver__FP18SQLCC_INITSTRUCT_Tb + 0x26C 
0x090000000F2471EC sqljsDrdaAsDriver__FP18SQLCC_INITSTRUCT_T + 
0xE8 
0x090000000EEE8E08 RunEDU__8sqeAgentFv + 0x234 
0x090000000EEE9F90 EDUDriver__9sqzEDUObjFv + 0xE4 
0x090000000EEE9E6C sqlzRunEDU__FPcUi + 0x24 
0x090000000EEFEB5C sqloEDUEntry + 0x264 
</StackTrace>
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1.                      * 
****************************************************************
Local Fix:
Make sure the container path refers to an existing path and NOT 
a link.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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

Solution
First fixed in Version 10.1 Fix Pack 1.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
09.01.2013
09.01.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList