KB223177: How to use MD Doctor to detect and fix certain physical inconsistencies in Microstrategy metadata?

Metadata Doctor (MD Doctor) is a utility that detects and fixes certain physical inconsistencies in Strategy 9.4.x - 9.5.x metadatas that may prevent Strategy 9.4.x - 9.5.x products from functioning correctly. 
In simple terms, it detects physical inconsistencies by running SQL against different metadata tables and then comparing results.  If an entry is found in one table but not in the main lookup table of the metadata then that denotes a physical inconsistency and MD Doctor will delete that orphan entry. 
Note: MD Doctor is not a supported tool for Strategy 10.x metadatas. Contact Strategy Technical Support to report issues which you believe might be fixed via MD Doctor.
NOTE:  MD Doctor should be used only after a metadata backup has been taken.  MD Doctor should not be used repeatedly.  It is meant to primarily serve as a quick-fix to physical inconsistencies and get environments up and running.  If repeated use of MD Doctor is needed then a possible recurrent-metadata physical inconsistency is being encountered.  Contact Strategy Technical Support to report repeated use of MD Doctor against a metadata and attempt to find the root cause of the problem.
          MD Doctor v6
To obtain details on the checks performed by MD Doctor review: KB8529: "What checks are performed by MD Doctor and how should the results be interpreted?"
 
MD Doctor Best Practices
Remember the following Best Practices when running MD Doctor:

• Running MD Doctor should not be a routine operation.  MD Doctor is meant to be used as a fix once Technical Support identifies that there is a metadata physical inconsistency causing an issue in the platform.
• Before running MD Doctor (fix/scan mode), all operations against the metadata should be stopped.
• Before running MD Doctor (fix mode), a backup of the metadata must be taken. 
• Always save the MD Doctor logs.

Pre-Requisites:
The following are pre-requisites for the use of MD Doctor:

• Strategy Developer 9.4.x - 9.5.x installed.  The product and metadata versions should match exactly.
  
• A Direct (2-tier) Project Source to the target Metadata. 
  

 
Certified DBMS Configurations:
MD Doctor has been certified for the following database platforms:
 
IBM DB2 UDB 9.7 for Linux, Windows and Unix
IBM Informix Dynamic Server 11.7
PostgreSQL 9.1
PostgreSQL 9.2
MySQL Enterprise 5.5
Sybase Adaptive Server Enterprise 15.5
Sybase Adaptive Server Enterprise 15.7
Microsoft SQL Server 2005
Microsoft SQL Server 2008
Microsoft SQL Server 2012
Oracle 10g Release 2
Oracle 11g Release 2
Teradata 13.1
Teradata 14.0
Microsoft Access 2003
 
 
Using Metadata Doctor:

• Run the setup.exe and follow installations instructions.
• Go to the Start menu and look for the MD Doctor executable under Strategy -> Tools
• Select the Direct Strategy data source which points to the metadata to be checked. If a direct data source to the metadata does not exist, use Strategy Developer or Strategy Configuration Wizard to create one before running this application.
   
  

•  
  Metadata Login-- Connection information to the actual metadata repository. Login and Table Prefix are read from the select Direct Datasource created through Desktop.  The user must specify a password.
   
  Data Source Login-- Strategy login and password in order to be able to check the metadata translations table.    
  
• Select Detect and Fix options:
  Detect only. Do not fix errors -- Also known as running MD Doctor in scan-mode.
  Prompt me to fix errors-- Also known as running MD Doctor in fix-mode.  Every time an error is encountered the user will be prompted to fix it.  Used for targeted fixes.
  Fix all errors automatically -- Also known as running MD Doctor in fix-mode.  No prompts to the user when an error is encountered. Used for fixing all encountered inconsistencies. 
   
  IMPORTANT:  Users should always backup their entire metadata before allowing Metadata Doctor to fix any inconsistencies. 
   
  Log File-- The location of the log file.  MD Doctor produces a detailed log file that records metadata statistics, errors log and actions taken; moreover it can include the SQL run against the metadata when the Include SQL in log file option is enabled. By default, the log file is generated in the same directory where the MD Doctor executable resides. A new log is created each time MD Doctor is run, and the log file name has a timestamp of the corresponding execution.
   
  
• Select the 'Start' button to begin. MD Doctor may be interrupted by clicking on the 'Stop' button. However, do not stop/interrupt MD Doctor while it is fixing inconsistencies in the metadata.
• A Status window will appear to display the checks performed by MDf Doctor:
   
  

WARNING:
Manually editing values in the Strategy Metadata incorrectly may cause serious, project-wide problems that may make your project unusable. Since these are user-initiated changes, they are not covered by any Strategy warranty. Users are strongly encouraged to backup the metadata prior to any alteration.
 
This issue has been logged as KB ID: 13727