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

SQLEPSTP AND DB2INSTANCESTOP FAILED WITH "SQL1652N FILE I/O ERROR
OCCURRED" ON AIX6.1

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
Occasionally while stopping the instance using either API 
db2InstanceStop or sqlepstp(), 
an "SQL1625N File I/O error occurred" error would 
be received. 
 
 
This error is seen in the db2diag.log, with an entry like: 
 
2010-03-05-14.01.22.952999-300 I64243A357         LEVEL: Severe 
PID     : 5067406              TID  : 1           PROC : 
darkstar 
INSTANCE: db2inst                NODE : 000 
EDUID   : 1 
FUNCTION: DB2 UDB, base sys utilities, sqlepstp, probe:100 
RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not found." 
          DIA8411C A file "" could not be found. 
 
2010-03-05-14.01.22.957922-300 I64601A296         LEVEL: Severe 
PID     : 5067406              TID  : 1           PROC : 
darkstar 
INSTANCE: db2inst                NODE : 000 
EDUID   : 1 
FUNCTION: DB2 UDB, base sys utilities, sqlepstp, probe:105 
MESSAGE : /home/db2inst/sqllib/tmp/db2stop.11760454.da
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Occasionally while stopping the instance using either API    * 
*                                                              * 
* db2InstanceStop or sqlepstp(), an "SQL1625N File I/O error   * 
* occurred" error would be received.                           * 
*                                                              * 
*                                                              * 
*                                                              * 
* This error is seen in the db2diag.log, with an entry like:   * 
*                                                              * 
*                                                              * 
*                                                              * 
* 2010-03-05-14.01.22.952999-300 I64243A357         LEVEL:     * 
* Severe                                                       * 
* PID     : 5067406              TID  : 1           PROC :     * 
*                                                              * 
* darkstar                                                     * 
*                                                              * 
* INSTANCE: db2inst                NODE : 000                  * 
*                                                              * 
* EDUID   : 1                                                  * 
*                                                              * 
* FUNCTION: DB2 UDB, base sys utilities, sqlepstp, probe:100   * 
*                                                              * 
* RETCODE : ZRC=0x860F000A=-2045837302=SQLO_FNEX "File not     * 
* found."                                                      * 
*           DIA8411C A file "" could not be found.             * 
*                                                              * 
*                                                              * 
*                                                              * 
* 2010-03-05-14.01.22.957922-300 I64601A296         LEVEL:     * 
* Severe                                                       * 
* PID     : 5067406              TID  : 1           PROC :     * 
*                                                              * 
* darkstar                                                     * 
*                                                              * 
* INSTANCE: db2inst                NODE : 000                  * 
*                                                              * 
* EDUID   : 1                                                  * 
*                                                              * 
* FUNCTION: DB2 UDB, base sys utilities, sqlepstp, probe:105   * 
*                                                              * 
* MESSAGE : /home/db2inst/sqllib/tmp/db2stop.11760454.da       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v97 fixpack 2.                                    * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
This problem occurs when the db2sysc process id is 8 digits 
long. This issue is first fixed in v97fixpack 2. With this fix 
the customer should no longer see this error.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66992 IC67528 IC68134 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.03.2010
26.04.2010
26.04.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FIXPACK,
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList