MicroStrategy - ScanMD and MD Doctor

mstr

Should we arbitrarily run MD Doctor?

No. 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.

What are the recommended steps to run MD Doctor?

Steps to run MD Doctor while minimizing potential metadata inconsistencies are as follows:

  1. Take a backup of the metadata in question.
  2. Create a 2-tier project source pointing to the metadata.
  3. Stop the Intelligence Server(s)
  4. Install and run MD Doctor per TN223177
  5. Start the Intelligence Server(s).

Should MD Doctor be used repeatedly?

No. 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 Technical Support to report repeated use of MD Doctor against a metadata and attempt to find the root cause of the problem.

What are the best practices regarding 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.

How can we use MD Doctor?

  1. Run the setup.exe and follow installations instructions.
  2. Go to the Start menu and look for the MD Doctor executable under MicroStrategy -> Tools
  3. Select the Direct MicroStrategy data source which points to the metadata to be checked. If a direct data source to the metadata does not exist, use MicroStrategy Desktop or MicroStrategy Configuration Wizard to create one before running this application. See TN223177 for the screenshot.
  4. Provide appropriate credential for the metadata database
  5. Provide appropriate credential for the metadata (typically this is the MSTR administrator account)
  6. Select appropriate 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.
  7. Provide the name and location for the log file. 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.
  8. 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.
  9. A Status window will appear to display the checks performed by MDf Doctor.
  • TN223177
  • TN8529 - What checks are performed by MDDoctor and how should the results be interpreted?

*

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License