Internal Database error – reorganize your IDB

Update: There are still a lot of old Data Protector installations (version 6.0, 6.1) and in all cases I’ve seen there is still the old errror described below. Thats why I updated and enhanced this article from August 2010.
When updating from a former Data Protector (5.X to 6.0 to 6.11) version to current version it might be nessecary to reorganize the internal database. You can check that with the command omnidbutil -chktblspace. If the output is Please run omnidbutil -modifytblspace to make IDB consistent. you are need to run the steps below.
In addition you can do a check using the command omnidbutil -extendinfo. When the maximum size for the database files (dirs.dat, fn1.ext, fnames.dat, …) shows a vlaue of 2097152 instead of 2096128 (2091752/1024=2048 instead of 2096128/1024=2047) your internal database structure has the wrong size. You need to downsize the database files in the case you upgraded your Data Protector to version 6.0 (and later to current version).
Steps to complete:

• Make a backup of the internal database
• Create some directories with enough free space, in our example e: omniback.bak, cdb, mmdb.
• Stop the Data Protector services (omnisv -stop)
• Make an additional backup of your installation (robocopy "d:\program files\omniback" e:\omniback.bak *.* /e /r:1 /w:1)
• Start the Data Protector services (omnisv -start)
• Make some screenshots regarding your fnames extensions and the count of your DCBF folders
• Export of the internal database
  • omnidbutil -writedb -mmdb e:\mmdb -cdb e:\cdb
  • Keep in mind: at the end of the export make a copy of the msg and dcbf folders
• Reintialize the internal database
  • omnidbinit -force
• Check the datafiles size und fix it if needed
  • omnidbutil -chktblspace (see above, if you receive the error follow the next step)
  • omnidbutil -modifytblspace (limit the datafile size)
  • omnidbutil -chktblspace (do an additional check)
• Import of the internal database
  • Create additional DCBF folders (see above) und extend fnames (GUI –> Internal Database –> Usage)
  • omnidbutil -readdb -mmdb e:\mmdb -cdb e:\cdb
  • Stop the Data Protector services (omnisv -stop)
  • Copy back the msg and DCBF folders
  • Start the Data Protector services (omnisv -start)
• On demand reset the session counter
  • omnidbutil -set_session_counter XXX (XXX is a integer value – must be larger than your last session ID)