Database checker fails with "Error 43 Index header contains incorrect object type" (4043470)

Date - Sep 2007
Affected Product & Version - NetVault: Backup 8.0
Affected Module & Version -
OS Version - Windows 2000/2003
Application Information - N/A

Description:
Specific problem with NetVault: Backup 8.0, nvmeddbcheck and nvscheddbcheck database checkers.

Symptoms:
Trying to back up the NetVault database results in an error:
Media Manager 'XXX' table failed raw database check (46)

When running the database checkers the routines fail with:
Error 43 Index header contains incorrect object type

Specifically:
C:\Program Files\BakBone Software\NetVault\util>nvmeddbcheck.exe check
nvmeddbcheck version 5.1
Raw database check failed on table 'DriveStatistics'
Error 43: Index header contains incorrect object type
Unable to initialize database

C:\Program Files\BakBone Software\NetVault\util>nvscheddbcheck.exe check
nvscheddbcheck version 1.0
Raw database check failed on table 'Policies'
Error 43: Index header contains incorrect object type
Raw database check failed on table 'RestoreSelectionSets'
Error 43: Index header contains incorrect object type
Raw database check failed on table 'RestoreTargetClientSets'
Error 43: Index header contains incorrect object type
Raw database check failed on table 'RestoreAdOptsSets'
Error 43: Index header contains incorrect object type
Raw database check failed on table 'BackupSelOptionsSets'
Error 43: Index header contains incorrect object type
Unable to initialize database

1) run a full backup of the NVDB - for this to work, untick the option "Check database tables before backup" for the job
2) stop the services
3) delete or rename %NV_HOME%/db/MediaDatabase and %NV_HOME%/db/ScheduleDatabase
4) restart the services
5) add and reconfigure the tape drive containing the database backup tape
6) scan this tape
7) perform a full restore of the Netvault DB.
8) run a full backup of the NVDB this time with option "Check database tables before backup" for the job selected to verify the problem has been resloved

Explanation.

This problem occurs with Netvault Databases that were created pre 7.4 release, there were some changes to the internal structures between 7.1x & 7.4.