SAP Knowledge Base Article - Preview

3769958 - DB6: Table or file system access error OSERR: EIO (5)

Symptom

The db2diag.log reports the following error when performing a Db2 activity.
The EIO (5) error is typically accompanied in db2diag.log by OS-level read/write failure entries (ossErrorIOAnalysis),
 
2025-04-09-00.00.00.258496+600 XXXXXXXXXXX          LEVEL: Error (OS)
PID     : XXXXXXX          TID : XXXXXXXXXXXXXXXPROC : db2sysc 0
INSTANCE: db2<SID>            NODE : 000            DB   : <SID>     
APPHDL  : XXXXXXXXX
HOSTNAME: XXXXXXXXX
EDUID   : XXXXXXXXX              EDUNAME: db2agent () 0
FUNCTION: DB2 Common, OSSe, ossErrorIOAnalysis, probe:100
CALLED  : OS, -, read                             OSERR: EIO (5)
DATA #1 : String, 118 bytes
A total of 3 analysis will be performed :
 - User info
 - Target file info
 - I/O attempt

Depending on the type of access, sometimes the path where the failure occurs is not recorded as seen above opposite "Target file info"

There can also be DB2 file access errors (often SQL0294N / container errors), and sometimes agent termination messages if the failure impacts database structures or communication paths. 
For example 

2025-04-09-00.00.00.258496+600 XXXXXXXXXXXXX          LEVEL: Error (OS)
PID     : XXXXXXX          TID : XXXXXXXXXXXXXXXPROC : db2sysc 0
INSTANCE: db2<SID>            NODE : 000            DB   : <SID>     
APPHDL  : XXXXXXXXX
HOSTNAME: XXXXXXXXX
EDUID   : XXXXXXXXX              EDUNAME: db2agent () 0
FUNCTION: DB2 UDB, common communication, sqlcctcptest, probe:11
MESSAGE : Detected client termination
DATA #1 : Hexdump, 2 bytes
0x00007F1CFABFA316 : 3600                                       6.

025-04-09-00.00.00.258496+600 XXXXXXXXXXXXX       LEVEL: Error (OS)
PID     : XXXXXXX          TID : XXXXXXXXXXXXXXXPROC : db2sysc 0
INSTANCE: db2<SID>            NODE : 000            DB   : <SID>     
APPHDL  : XXXXXXXXX
HOSTNAME: XXXXXXXXX
EDUID   : XXXXXXXXX              EDUNAME: db2agent () 0
FUNCTION: DB2 UDB, common communication, sqlcctest, probe:50
MESSAGE : sqlcctest RC
DATA #1 : Hexdump, 2 bytes
0x00007F1CFABFC35E : 3600 






Read more...

Environment

Db2 LUW IBM 

Product

SAP ERP 6.0

Keywords

DB2 Common, OSSe, ossErrorIOAnalysis, OS, -, read, OSERR: EIO (5), User info, Target file info, I/O attempt, CALLSTCK: OSERR: EINVAL (22), DIA8555C An invalid message queue handle was encountered, SQLO_QUE_BAD_HANDLE "Bad Queue Handle" , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.