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

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
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

Lösung
Problem was first fixed in DB2 version 10.1 fixpack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.04.2013
02.10.2013
02.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList