|
Problem IC62772
|
Status: Closed |
SQLDFETCHDIRECT REPORTS A BAD DATA PAGE WHEN A SPECIAL RECORD TYPE IS ENCOUNTERED |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Customer's fetch request may encounter Bad Data Page error and
dump FODC_DBMarkedBad_xxxxx file.
The following message will be logged in db2diag.log:
FUNCTION: DB2 UDB, data management, sqldFetchDirect, probe:4407
RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data
Page"
DIA8500C A data file error has occurred, record id is
""
.
From <StackTrace>
-------Frame------ ------Function + Offset------
0x0900000000B3D450 pthread_kill + 0xB0
0x0900000002FC32C8 sqloDumpEDU + 0x34
0x0900000001F2FF88 MarkDBBad__16sqeLocalDatabaseFi + 0x210
0x0900000001F2F5B4 sqldDumpContext__FP8sqeAgentiN42PCcPvT2 +
0x788
0x0900000001F39E44
sqldDumpBadPage__FP8sqeAgentP8SQLD_TCBP13SQLD_PAGESLOTP9SQLB_PAG
EUliT6
+ 0x6E0
0x0900000002427690
sqldDumpBadPage__FP8sqeAgentP8SQLD_TCBP13SQLD_PAGESLOTP9SQLB_PAG
EUliT6
@glue850 + 0x78
0x09000000021320D0 sqldFetchDirect__FP13SQLD_DFM_WORK + 0x1A0
But, the DART command reports no error as follows:
The requested DB2DART processing has completed successfully!
All operation completed without error;
no problems were detected in the database. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* Customer's fetch request may encounter Bad Data Page error *
* and *
* dump FODC_DBMarkedBad_xxxxx file. *
* *
* The following message will be logged in db2diag.log: *
* *
* FUNCTION: DB2 UDB, data management, sqldFetchDirect, *
* probe:4407 *
* *
* RETCODE : ZRC=0x87040001=-2029780991=SQLD_BADPAGE "Bad Data *
* Page" *
* DIA8500C A data file error has occurred, record id *
* is *
* "" *
* . *
* *
* From <StackTrace> *
* *
* -------Frame------ ------Function + Offset------ *
* *
* 0x0900000000B3D450 pthread_kill + 0xB0 *
* *
* 0x0900000002FC32C8 sqloDumpEDU + 0x34 *
* *
* 0x0900000001F2FF88 MarkDBBad__16sqeLocalDatabaseFi + 0x210 *
* *
* 0x0900000001F2F5B4 sqldDumpContext__FP8sqeAgentiN42PCcPvT2 + *
* 0x788 *
* 0x0900000001F39E44 *
* *
* sqldDumpBadPage__FP8sqeAgentP8SQLD_TCBP13SQLD_PAGESLOTP9SQLB_P
* EUliT6 *
* *
* + 0x6E0 *
* *
* 0x0900000002427690 *
* *
* sqldDumpBadPage__FP8sqeAgentP8SQLD_TCBP13SQLD_PAGESLOTP9SQLB_P
* EUliT6 *
* *
* @glue850 + 0x78 *
* *
* 0x09000000021320D0 sqldFetchDirect__FP13SQLD_DFM_WORK + *
* 0x1A0 *
* *
* *
* But, the DART command reports no error as follows: *
* *
* The requested DB2DART processing has completed successfully! *
* All operation completed without error; *
* no problems were detected in the *
* database. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 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 |
Problem is first fixed in DB2 Version 9.7 Fix Pack 1. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.08.2009
13.01.2010
13.01.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
|
 |
