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

ADMIN_CMD FOR AUTOCONFIGURE COMMAND THROWS SQL1042C IN WINDOWS OS

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
call admin_cmd('AUTOCONFIGURE USING ISOLATION RS APPLY DB ONLY') 
 
SQL1042C  An unexpected system error occurred.  SQLSTATE=58004
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of autoconfigure command using admin_cmd on windows    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* call admin_cmd('AUTOCONFIGURE USING ISOLATION RS APPLY DB    * 
* ONLY')                                                       * 
* SQL1042C  An unexpected system error occurred.               * 
* SQLSTATE=58004                                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 v9.5 fp6                                      * 
****************************************************************
Local-Fix:
Copy db2sg.DLL from ~sqllib\bin to ~sqllib\function  directory.
verfügbare FixPacks:
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

Lösung
problem is first fixed in DB2 V9.5 FP6
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.10.2009
30.03.2010
30.03.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.FP6
Problem behoben lt. FixList in der Version