{"id":150,"date":"2011-07-15T18:02:19","date_gmt":"2011-07-15T16:02:19","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=150"},"modified":"2015-12-10T10:05:56","modified_gmt":"2015-12-10T09:05:56","slug":"reorganisation-der-internen-datenbank","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2011\/07\/reorganisation-der-internen-datenbank\/","title":{"rendered":"Internal Database error &#8211; reorganize your IDB"},"content":{"rendered":"<p><strong>Update: <\/strong>There are still a lot of old Data Protector installations (version 6.0, 6.1) and in all cases I&#8217;ve seen there is still the old errror described below. Thats why I updated and enhanced this article from August 2010.<br \/>\nWhen 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 <code>omnidbutil -chktblspace<\/code>. If the output is <code>Please run omnidbutil -modifytblspace to make IDB consistent.<\/code> you are need to run the steps below.<br \/>\nIn addition you can do a check using the command <code>omnidbutil -extendinfo<\/code>. When the maximum size for the database files (dirs.dat, fn1.ext, fnames.dat, &#8230;) 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).<br \/>\nSteps to complete:<\/p>\n<ul>\n<li>Make a backup of the internal database<\/li>\n<li>Create some directories with enough free space, in our example e:&nbsp;omniback.bak, cdb, mmdb.<\/li>\n<li>Stop the Data Protector services (<code>omnisv -stop<\/code>)<\/li>\n<li>Make an additional backup of your installation (<code>robocopy \"d:\\program files\\omniback\" e:\\omniback.bak *.* \/e \/r:1 \/w:1<\/code>)<\/li>\n<li>Start the Data Protector services (<code>omnisv -start<\/code>)<\/li>\n<li>Make some screenshots regarding your fnames extensions and the count of your DCBF folders<\/li>\n<li>Export of the internal database\n<ul>\n<li><code>omnidbutil -writedb -mmdb e:\\mmdb -cdb e:\\cdb<\/code><\/li>\n<li>Keep in mind: at the end of the export make a copy of the msg and dcbf folders<\/li>\n<\/ul>\n<\/li>\n<li>Reintialize the internal database\n<ul>\n<li><code>omnidbinit -force<\/code><\/li>\n<\/ul>\n<\/li>\n<li>Check the datafiles size und fix it if needed\n<ul>\n<li><code>omnidbutil -chktblspace<\/code> (see above, if you receive the error follow the next step)<\/li>\n<li><code>omnidbutil -modifytblspace<\/code> (limit the datafile size)<\/li>\n<li><code>omnidbutil -chktblspace<\/code> (do an additional check)<\/li>\n<\/ul>\n<\/li>\n<li>Import of the internal database\n<ul>\n<li>Create additional DCBF folders (see above) und extend fnames (GUI &#8211;&gt; Internal Database &#8211;&gt; Usage)<\/li>\n<li><code>omnidbutil -readdb -mmdb e:\\mmdb -cdb e:\\cdb<\/code><\/li>\n<li>Stop the Data Protector services (<code>omnisv -stop<\/code>)<\/li>\n<li>Copy back the msg and DCBF folders<\/li>\n<li>Start the Data Protector services (<code>omnisv -start<\/code>)<\/li>\n<\/ul>\n<\/li>\n<li>On demand reset the session counter\n<ul>\n<li>omnidbutil -set_session_counter XXX (XXX is a integer value &#8211; must be larger than your last session ID)<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>Update: There are still a lot of old Data Protector installations (version 6.0, 6.1) and in all cases I&#8217;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 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[11],"tags":[71,69,70,72,68,16],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"en","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":false,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-2q","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":4340,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/09\/appserver-issues-when-upgrading-to-10-x\/","url_meta":{"origin":150,"position":0},"title":"AppServer issues when upgrading to 10.x","date":"26. September 2018","format":false,"excerpt":"{:en}The AppServer has become an integral part of Data Protector. When it fails neither user authentication, scheduling or reporting will work. A critical issue has been identified that may cause upgrades to fail and\/or run-time issues caused by invalid data stored in the jce_service_description and jce_service_property tables in the Data\u2026","rel":"","context":"In &quot;Advisory&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1892,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/03\/migrate-dp-8-xx-dp-8-xx-hardware-ms-windows-operating-system\/","url_meta":{"origin":150,"position":1},"title":"Migrate DP 8.XX to DP 8.XX using new hardware or different MS Windows operating system","date":"26. March 2014","format":false,"excerpt":"{:en}The migration of the internal database to new hardware or to a new Microsoft Windows operating system was no big deal in the past and before the release of Data Protector 8.xx. With the introduction of PostgreSQL as the new internal database this has been changed and several steps are\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":3004,"url":"https:\/\/www.data-protector.org\/wordpress\/2016\/07\/runbook-migrate-data-protector-7-0x-data-protector-9-0x\/","url_meta":{"origin":150,"position":2},"title":"RUNBOOK \u2013 Migrate Data Protector 7.0x to Data Protector 9.0x","date":"5. July 2016","format":false,"excerpt":"{:en} Update 2016\/0705: In section installation source it was recommended to use a patched installation source for the upgrade. This method must not be used for upgrades from Data Protector versionen 8.13 and newer, as it will cause serious damages in the internal database (no fix available\/possible). For versions older\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":4432,"url":"https:\/\/www.data-protector.org\/wordpress\/2018\/12\/data-protector-10-updated-release-a-10-20-build-115\/","url_meta":{"origin":150,"position":3},"title":"Data Protector 10 \u2013 Updated Release A.10.20 (Build 115)","date":"10. December 2018","format":false,"excerpt":"{:en}Data Protector\u00a0A.10.20 (Build 115)\u00a0has been released on December 6, 2018. The new version is another full install to simplify the upgrade and installation process.This will continue to be the default for all future Data Protector versions. Data Protector 10.20 does not require any previous version to install the latest version\u2026","rel":"","context":"In &quot;DP A.10.00&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":62,"url":"https:\/\/www.data-protector.org\/wordpress\/2010\/06\/export-import\/","url_meta":{"origin":150,"position":4},"title":"Export \/ Import","date":"28. June 2010","format":false,"excerpt":"{:en}No translation for this article available.{:} {:de} Immer wieder mal findet man Anleitungen wie ein Export \/ Import der internen Datenbank von Data Protector vorzunehmen ist. Diese Prozedur wird immer dann eingesetzt wenn Probleme in der Datenbank auftreten (korrupte Medien, ...) - Stichwort Healthcheck und omnidbcheck. Bei der nachfolgenden Prozedur\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1350,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/05\/connections-gateway-storeonce-software-store\/","url_meta":{"origin":150,"position":5},"title":"No available connections on gateway for StoreOnce Software Store","date":"7. May 2013","format":false,"excerpt":"{:en}When using the StoreOnce Software Store in Data Protector for jobs an error might be displayed: There are no available connections on gateway. This can occur when there are locked devices in the media managemt database of Data Protector. Normally the devices are released automatically or when the Data Protector\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/150"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=150"}],"version-history":[{"count":20,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/150\/revisions"}],"predecessor-version":[{"id":2732,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/150\/revisions\/2732"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=150"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=150"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=150"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}