NAV Database Test fails

melsadek

All,

Our customer has encountered a NAV database crash over the holidays. In fact the entire VM that housed the SQL Server and NAV crashed. Long story short, the NAV Database is back up and running, SQL Services are back up and running, however when we ran CHECKDB and File->Database->Test, we encountered the following errors:

8934,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 71723358, index ID 1, partition ID 72057596749676544, alloc unit ID 72057596779298816 (type In-row data). The high key value on page (3:19496106) (level 0) is not less than the low key value in the parent (3:7934865), slot 232 of the next page (3:19496107).
8934,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 71723358, index ID 1, partition ID 72057596749676544, alloc unit ID 72057596779298816 (type In-row data). The high key value on page (3:19496106) (level 0) is not less than the low key value in the parent (3:7934865), slot 232 of the next page (3:19496107).
8934,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 71723358, index ID 1, partition ID 72057596749676544, alloc unit ID 72057596779298816 (type In-row data). The high key value on page (3:19496107) (level 0) is not less than the low key value in the parent (3:7934865), slot 233 of the next page (3:19496108).
8934,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 71723358, index ID 1, partition ID 72057596749676544, alloc unit ID 72057596779298816 (type In-row data). The high key value on page (3:19496107) (level 0) is not less than the low key value in the parent (3:7934865), slot 233 of the next page (3:19496108).
8934,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 71723358, index ID 1, partition ID 72057596749676544, alloc unit ID 72057596779298816 (type In-row data). The high key value on page (3:19496108) (level 0) is not less than the low key value in the parent (3:7934865), slot 234 of the next page (3:19496109).
8934,"42000",[Microsoft][ODBC SQL Server Driver][SQL Server]Table error: Object ID 71723358, index ID 1, partition ID 72057596749676544, alloc unit ID 72057596779298816 (type In-row data). The high key value on page (3:19496108) (level 0) is not less than the low key value in the parent (3:7934865), slot 234 of the next page (3:19496109).

The database seems to be stable, but we want to eliminate these issues altogether. And before you ask, YES, these errors resulted AFTER the database crashed, since an earlier backup prior to the crash showed no such errors.

Does anyone have previous experience in dealing with AND resolving issues like the one above? The Object ID being referenced above turns out to be the Value Entry table?

Regards,

RaniShoura

Do you use table partitions ? are you using the same version of SQL server or it was changed ? if you had done any database design change from outside NAV to the table / Index ?
Did you try to run a rebuild to the index ?

melsadek

RaniShoura wrote: »

Do you use table partitions ?

I am not sure what you mean. Please clarify and elaborate.

RaniShoura wrote: »

are you using the same version of SQL server or it was changed ?

No. It's still the same version of SQL.

RaniShoura wrote: »

if you had done any database design change from outside NAV to the table / Index ?

No.

RaniShoura wrote: »

Did you try to run a rebuild to the index ?

I attempted to rebuild the indexes using DBCC DBREINDEX, but that resulted in the following error:

The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name XXX$Value Entry' and the index name XXX$Value Entry$0'. The duplicate key value is (78023971).

parm

Hi,

You should try to run DBCC CHECKDB with REPAIR_FAST to try to recover the error.
If fail, try DBCC CHECKDB with REPAIR_REBUILD option.
Even if it still fails the last option is running with REPAIR_ALLOW_DATA_LOSS.

Is this case, some records could be lost.
In case of need to run with repair_allow_data_loss option, try before to find the object with sql ID 71723358 (not nav Id) to find the object where the data loss could happen.

Regards and good luck.

parm

melsadek

Thanks guys for the feedback. Unfortunately none of the DBCC CHECKDB flags worked. So we're rebuilding the Value Entry table by exporting it out, and then removing the inconsistencies. Any thoughts you can give me or things to watch out for?