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

"VAR ENV NOT FOUND" ERROR MESSAGE IN DB2DIAG.LOG FOLLOWED BY DUMP
FILE CREATION

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
The db2diag.log may report a message like : 
 
2009-09-24-10.54.21.404231+120 I71990244A472      LEVEL: Error 
PID     : 9397                 TID  : 1           PROC : 
db2agntp (SAMPLE) 0 
INSTANCE: db2inst1             NODE : 000 
APPHDL  : 0-2762               APPID: 
9.121.225.89.41233.092403233340 
AUTHID  : db2inst1 
FUNCTION: DB2 UDB, access plan manager, sqlra_find_var_env, 
probe:20 
DATA #1 : String, 108 bytes 
Var Env not found (fill == FALSE)! 
p_anchor->id: 162 
p_stmt anchor_id: 162 
p_stmt stmt uid: 14223 
env_id: 1 
 
 
Followed by the creation of a trap and dump file. 
The trap file may show the following stack trace : 
 
sqlzeDumpFFDC 
sqlzeSqlCode 
sqlrrSqlCode 
sqlra_find_var_env 
sqlra_find_var 
sqlra_rpc_apm_ship 
sqlrk_apm_router 
sqlrr_rpc_router 
sqlrr_subagent_router 
... 
 
Although error -901 will also be reported in the db2diag.log, 
this should not be sent back to the client application. 
This problem can occur when a coordinating agent has been 
interrupted but the subagents working on the request failed to 
be notified in time. 
The database stays online and is not affected in any way by 
these events, other than possibly large dump files in the 
db2dump subdirectory.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* v95, v97 users                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* 1. Problem abstract                                          * 
* -901 raised by subagent seen in db2diag.log                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v95fp6 or v97                                     * 
****************************************************************
Local Fix:
n/a
available fix packs:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Patch included that increases the size of the registry.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC96239 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.10.2009
08.06.2010
25.09.2013
Problem solved at the following versions (IBM BugInfos)
9.5.FP6,
9.7.
Problem solved according to the fixlist(s) of the following version(s)