|
Problem IC63919
|
Status: Geschlossen |
A SEVERE DB2DIAG.LOG ENTRY IS LOGGED, DIA8000C AN UNEXPECTED END OF FILE WAS REACHED "" BUT THE DB STARTS SUCCESSFULLY. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
The following db2diag.log entry is logged when starting the
database:
YYYY-MM-DD-HH.MM.SS.MMMMMM-xxx I1414486E479 LEVEL: Severe
PID : <pid> TID : <tid> PROC : db2sysc
INSTANCE: <db2 instance> NODE : 000 DB : <db alias>
APPHDL : <apphdl> APPID: *LOCAL.<db2instance>.######
AUTHID : <authid>
EDUID : <eudid> EDUNAME: db2agent (<db alias>)
FUNCTION: DB2 UDB, base sys utilities, sqleserl, probe:911
RETCODE : ZRC=0x00000001=1
DIA8000C An unexpected end of file was reached "".
but the database starts successfully eventhough log entry is at
the 'severe' level.
If the database starts successfully then this db2diag.log entry
can be ignored and will be removed for future FixPak releases. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* The following db2diag.log entry is logged when starting the *
* *
* database: *
* *
* *
* *
* YYYY-MM-DD-HH.MM.SS.MMMMMM-xxx I1414486E479 LEVEL: *
* Severe *
* PID : <pid> TID : <tid> PROC : db2sysc *
* *
* INSTANCE: <db2 instance> NODE : 000 DB : <db alias> *
* *
* APPHDL : <apphdl> APPID: *
* *LOCAL.<db2instance>.###### *
* AUTHID : <authid> *
* *
* EDUID : <eudid> EDUNAME: db2agent (<db alias>) *
* *
* FUNCTION: DB2 UDB, base sys utilities, sqleserl, probe:911 *
* *
* RETCODE : ZRC=0x00000001=1 *
* *
* DIA8000C An unexpected end of file was reached "". *
* *
* *
* *
* but the database starts successfully eventhough log entry is *
* at *
* the 'severe' level. *
* *
* *
* *
* If the database starts successfully then this db2diag.log *
* entry *
* can be ignored and will be removed for future FixPak *
* releases. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v97 fixpack 1. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 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 |
Fix contained in v97 fixpack 1. Customer should no longer see
these messages in db2diag.log. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 21.10.2009
02.03.2010
02.03.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP1
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.1
|
 |
