suche 36x36
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 IT27001 Status: Closed

POSSIBLE TRAPS AND/OR EBADF (ERRNO 9) ERRORS WHEN USING UTL_MAIL.SEND()
AND THE ROUTINES FAILS

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Db2 might crash with errors like the following in the
db2diag.log, pointing to a possible Disk issue, although there
is no relevant disk problem.

FUNCTION: DB2 UDB, oper system services, sqloSystemErrorHandler,
probe:10
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found."
DIA8411C A file "" could not be found.
CALLED : OS, -, fstat64
OSERR  : EBADF (9) "Bad file number"

The problem is due to calling UTL_MAIL.SEND() (not limited to
just this routine)
When such a routine fails it will attempt to close the 'file
descriptor' to the
SMTP server 3 times in a row instead of 1. If something else
opened a file and got the same  file descriptor in between then
results can end up in trap or
errors (EBADF - errno 9) for any system call dealing with a file
descriptor.

One way to check for this issue is to use traces:

  cat > trcmask
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.11.2018
16.01.2020
04.03.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)