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

AUTO_RUNSTATS MIGHT TERMINATE EARLY IN FEDERATED DATABASES THAT HAVE BOTH
NICKNAMES AND LOCAL TABLES WITH STATISTICS PROFILES

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Symptoms, as seen in statistics logs: 
1. function Atm::process_tables Error entry with: 
        [IBM][CLI Driver][DB2/LINUXX8664] SQL0423N  Locator 
variable "1" does not currently represent any value. 
SQLSTATE=0F001 
    2. START and STOP database EVALUATION entries without table 
COLLECT entries
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Federated environment only                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1 fixpack 3                        * 
****************************************************************
Local Fix:
Exclude nicknames in the AUTO_RUNSTATS auto maintenance policy.
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 version 10.1 fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.04.2013
02.10.2013
02.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList