|
Problem IC63919
|
Status: Closed |
A SEVERE DB2DIAG.LOG ENTRY IS LOGGED, DIA8000C AN UNEXPECTED END OF FILE WAS REACHED "" BUT THE DB STARTS SUCCESSFULLY. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| 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. |
| Problem Summary: |
****************************************************************
* 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: |
|
| available fix packs: |
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
|
| Solution |
Fix contained in v97 fixpack 1. Customer should no longer see
these messages in db2diag.log. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.10.2009
02.03.2010
02.03.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
