If a LOAD operation fails in a small window due to limited
resources when recreating the indexes of the table being loaded,
a mismatch between the table and index might occur. You might
hit this mismatch problem if you ran the LOAD command with the
following options and have it failed when recreating one of the
root pages of the index:
- ALLOW READ ACCESS or ALLOW WRITE ACCESS
- INDEXING MODE REBUILD or INDEXING MODE AUTOSELECT where
REBUILD is selected by DB2
If you hit this mismatch problem, you will see db2diag.log
messages from the following functions and probes:
FUNCTION: DB2 UDB, catalog services, sqlrlRecreateSingleIndex,
probe:200
FUNCTION: DB2 UDB, catalog services, sqlrlRecreateIndexObject,
probe:10
FUNCTION: DB2 UDB, catalog services, sqlrlRecreateIndexObject,
probe:20
FUNCTION: DB2 UDB, catalog services, sqlrlRecreateIndexes,
probe:99
FUNCTION: DB2 UDB, database utilities, sqluRecreateIndexObjects,
probe:7042
If the problem is hit, then at this point the index object
descriptor will indicate an error while page zero of the index
object will not. As a result, the index is not maintained on
undo, and the index can become out-of-sync with the table. This
could result in a number of different symptoms. The following
symptoms are two examples:
1) Row is not found in the table during data fetch from index.
A message with the following text might appear in the
db2diag.log file:
FUNCTION: DB2 UDB, data management, sqldDataFetch, probe:4623
MESSAGE : Row not found on data fetch from index!
2) Row is not found in the index during the update or delete of
a row in the table. A message with the following text might
appear in the db2diag.log file:
FUNCTION: DB2 UDB, index manager, procT2Leaf2Del, probe:7
RETCODE : ZRC=0x8709002C=-2029453268=SQLI_NOKEY "Key not found
within node"
DIA8541C The index key could not be found, the value
was "". |
