home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT03965 Status: Geschlossen

SQL0901N IS RETURNED WITH "EPE: NO MATCHING Z-VAL FOR PROBE KEY IN
RECV TQ" ERROR IN DPF ENVIRONMENT

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Query execution might fail with the following error 
message: 
 
SQL0901N  The SQL statement or command failed because of a 
database system error. (Reason "EPE: No matching z-val for probe 
key in recv TQ".) SQLSTATE=58004 
 
You will find a similar entry in the db2diag.log: 
 
2014-06-14-04.36.38.092081-240 I428236196A915       LEVEL: 
Severe 
PID     : 14615464             TID : 41301          PROC : 
db2sysc 0 
INSTANCE: db2inst1             NODE : 000           DB   : 
SAMPLE 
APPHDL  : 0-8194               APPID: *N0.db2inst1.140801083628 
AUTHID  : DB2INST1             HOSTNAME: server1 
EDUID   : 41301                EDUNAME: db2agent (SAMPLE) 0 
FUNCTION: DB2 UDB, relation data serv, sqlrr_dump_ffdc, 
probe:300 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -901   sqlerrml: 47 
 sqlerrmc: EPE: No matching z-val for probe key in recv TQ 
 sqlerrp : SQLNG1FC 
 sqlerrd : (1) 0x00000000      (2) 0x00000000      (3) 
0x00000000 
           (4) 0x00084CDD      (5) 0xFFFFFC52      (6) 
0x00000000 
 sqlwarn : (1)      (2)      (3)      (4)        (5)       (6) 
 
           (7)      (8)      (9)      (10)        (11) 
 sqlstate: 
 
and the following call stack will be produced: 
 
sqlnn_erds 
sqlng_process_hsjn_op 
sqlng_process_hsjn_op 
sqlngProcessLolepop 
sqlng_process_mate_op 
sqlngProcessLolepop 
sqlng_process_pipe_op 
sqlngProcessLolepop 
sqlng_build_thread 
[...]
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above                                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5                       * 
****************************************************************
Local-Fix:
You can avoid this problem by disabling the EPE optimization 
using the registry variable setting: 
DB2_REDUCED_OPTIMIZATION=NO_EPE 
You can apply this at the application or statement level by 
applying an optimization profile containing a guideline with a 
REGISTRY request.
Lösung
First fixed in DB2 Version 10.5 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.08.2014
31.03.2015
31.03.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList