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 IC93746 Status: Closed

DB2 ABEND WITH MEMORY CORRUPTION DURING LOAD PROCESSING.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
DB2 may abend at the end of load during file closure with 
SIGSEV. 
 
FODC Trap will be created and stack dump may look as follows: 
 
Stack #1             Signal #11        Timestamp 
2013-06-04-12.19.46.971129 
0        strlen 
1        _doprnt 
2        vsnprintf 
3        ossSnprintf 
4        pdFormat_SQLO_FHANDLE 
5        pdFormatArg 
6        pdInvokeFmtFnc 
7        @132@formatPDType 
8        @132@pdTypeFormatOrDump 
9        @132@pdLogInternal 
10       pdLogInternal 
11       pdLogSysRC 
12       sqloSystemErrorHandler 
13       sqloSystemErrorHandler@glue7CE 
14       sqlodelete 
15       sqloDeleteNamedPipe 
16       sqluCSerializablePipeBase::iClose 
17       sqluCSerializablePipeBase::iCleanUp 
18       sqluCSerializablePipe::iCleanUp 
19       @88@sqluCleanupUserExitPipes 
20       sqluCleanupUserExitCB 
21       sqluAppCbCleanup 
22       sqluCommitCallBack 
23       sqlrr_tran_router 
24       sqlrr_subagent_router 
25       sqleSubRequestRouter 
26       sqleProcessSubRequest 
27       sqeAgent::RunEDU 
28       sqzEDUObj::EDUDriver 
29       sqloEDUEntry 
 
Memory may be also consumed fully during this abend. Core dump 
may be generated as well. 
 
db2diag.log may look as follows: 
 
2013-06-04-12.19.47.171008-240 I43934143A490      LEVEL: Warning 
PID     : 12780076             TID  : 265047      PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   :sample 
APPHDL  : 1-15207              APPID: *N1.db2inst1.130604132421 
AUTHID  : LOADPROD 
EDUID   : 265047               EDUNAME: db2agnta (EDWDBP01) 0 
FUNCTION: DB2 UDB, RAS/PD component, 
pdEDUIsInDB2KernelOperation, probe:600 
DATA #1 : String, 13 bytes 
 ossSnprintf 
DATA #2 : String, 3 bytes 
oss 
 
2013-06-04-12.19.47.172227-240 I43934634A566      LEVEL: Severe 
PID     : 12780076             TID  : 265047      PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   :sample 
APPHDL  : 1-15207              APPID: *N1.db2inst1.130604132421 
AUTHID  : LOADPROD 
EDUID   : 265047               EDUNAME: db2agnta (EDWDBP01) 0 
FUNCTION: DB2 UDB, RAS/PD component, 
pdResilienceIsSafeToSustain, probe:800 
DATA #1 : String, 37 bytes 
Trap Sustainability Criteria Checking 
DATA #2 : Hex integer, 8 bytes 
0x0000000302001849 
DATA #3 : Boolean, 1 bytes 
false 
 
2013-06-04-12.21.45.561356-240 E43981275A1383     LEVEL: Error 
(OS) 
PID     : 12780076             TID  : 22963       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   :sample 
APPHDL  : 1-15866              APPID: *N1.db2inst1.130604161934 
AUTHID  : LOADPROD 
EDUID   : 22963                EDUNAME: db2agnta (EDWDBP01) 0 
FUNCTION: DB2 UDB, oper system services, sqlodelete, probe:50 
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." 
          DIA8411C A file "" could not be found. 
CALLED  : OS, -, unlink 
OSERR   : ENOENT (2) "No such file or directory" 
DATA #1 : File name, 137 bytes 
/gpfs/dba/db2utlgn/edwdbp01/s41f400n01/temp_files/cdwdba.lda_tas 
er_txns_ltr_tags_daily/DB200041.PID/DB200597.OID/db2loadpipe3974 
7.000.000 
DATA #2 : File handle, PD_TYPE_SQO_FILE_HDL, 8 bytes 
  File Handle              = 125829120 
  File System Block Size   = 0 bytes 
  File System Type         = UNKNOWN 
  File Handle Flags : 
    Require Sector Align   = No 
    DIO/CIO Mode           = Yes 
    Raw Block Device       = No 
    Reserved Handle        = No 
    Flush On Close         = No 
    Thread-Level Lock      = Yes 
    Write-through Mode     = Yes 
    File Not Tracked       = No 
DATA #3 : unsigned integer, 4 bytes 
1 
DATA #4 : String, 105 bytes 
Search for ossError*Analysis probe point after this log entry 
for further 
self-diagnosis of this problem. 
 
2013-06-04-12.21.45.561868-240 E43982659A526      LEVEL: Error 
PID     : 12780076             TID  : 22963       PROC : db2sysc 
0 
INSTANCE: db2inst1             NODE : 000         DB   :sample 
APPHDL  : 1-15866              APPID: *N1.db2inst1.130604161934 
AUTHID  : LOADPROD 
EDUID   : 22963                EDUNAME: db2agnta (EDWDBP01) 0 
FUNCTION: DB2 UDB, oper system services, sqloDeleteNamedPipe, 
probe:10 
MESSAGE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." 
          DIA8411C A file "" could not be found.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V97 FP9                                       * 
****************************************************************
Local Fix:
No Local Fix
available fix packs:
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First Fixed in DB2 V97 FP9
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.06.2013
16.12.2013
16.12.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.9 FixList
9.7.0.9 FixList