home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IT17190 Status: Closed

db2audit hit EFAULT when trying to format the output.

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
db2audit may hit EFAULT in write() when trying to format audit 
data. 
 
 At that time, db2audit will insert diag entry as following to 
db2diag.log 
 
2016-08-30-11.08.14.309568+540 I924412E2012          LEVEL: 
Error (OS) 
PID     : 25148                TID : 140454268876608 PROC : 
db2audit 
INSTANCE: db2inst1             NODE : 000 
HOSTNAME: host1 
FUNCTION: DB2 Common, OSSe, ossErrorIOAnalysis, probe:100 
CALLED  : OS, -, write                            OSERR: EFAULT 
(14) 
DATA #1 : String, 115 bytes 
A total of 3 analysis will be performed : 
- User info 
- Target file info 
- I/O attempt 
 
Target file handle = 4 
DATA #2 : String, 192 bytes 
  Real user ID of current process       = 10100 
  Effective user ID of current process  = 10100 
  Real group ID of current process      = 10100 
  Effective group ID of current process = 10100 
DATA #3 : String, 41 bytes 
current sbrk(0) value: 0x00000000024d5000 
DATA #4 : String, 264 bytes 
Target File Information : 
  Size               = 1294316 
  Link               = No 
  Reference path     = N/A 
  Type               = 0x8000 
  Permissions        = rw-rw-rw- 
  UID                = 10100 
  GID                = 10100 
  Last modified time = 1472522894 
DATA #5 : String, 33 bytes 
I/O attempt not implemented yet. 
CALLSTCK: (Static functions may not be resolved correctly, as 
they areresolved to the nearest symbol) 
  [0] 0x00007FBE0B35FBFB /db2inst1/sqllib/lib64/libdb2osse.so.1 
+0x236BFB 
  [1] 0x00007FBE0B3610B4 ossLogSysRC + 0xB4 
  [2] 0x00007FBE0B352E62 /db2inst1/sqllib/lib64/libdb2osse.so.1 
+0x229E62 
  [3] 0x00007FBE0B35076D ossErrorAnalysis + 0x2D 
  [4] 0x00007FBE0CA5339B sqloSystemErrorHandler + 0x6BB 
  [5] 0x00007FBE0C9D0D71 sqlowrite + 0x721 
  [6] 
0x00007FBE0C6DF07D_Z39sqlex_db2audit_writerecord_comp_env_logP20 
sqlrr_generic_headerP22sqlexExtractOutputFileP20sqlexAuditSyslog 
Info + 0xC0D 
  [7] 0x00007FBE0C6D5AA3 /db2inst1/sqllib/lib64/libdb2.so.1 + 
0xDFCAA3 
  [8] 0x00007FBE0C6CE99C sqlexDb2auditExtractAPI + 0x1D7C 
  [9] 0x00000000004061D7 db2audit + 0x61D7 
  [10] 0x0000000000403711 main + 0x171 
  [11] 0x00007FBE0A56AAF5 __libc_start_main + 0xF5 
  [12] 0x00000000004034D9 db2audit + 0x34D9
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 11.1 Fix Pack 1                               * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 11.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.09.2016
09.05.2017
09.05.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
11.1.1.1 FixList