Metadata Doctor (MD Doctor) in Microstrategy

Metadata Doctor (MD Doctor) is a utility that detects and fixes certain physical inconsistencies in MicroStrategy 9.4.x - 9.5.x metadatas that may prevent MicroStrategy 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 MicroStrategy 10.x metadatas.

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.

MSTR WARNING:

Manually editing values in the MSTR 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 MicroStrategy warranty. Users are strongly encouraged to backup the metadata prior to any alteration.

Pre-Requisites for using MD Doctor:

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

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

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.

Using Metadata Doctor:

Run the setup.exe and follow installations instructions.
Go to the Start menu and look for the MD Doctor executable under MicroStrategy -> Tools
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 Developer or MicroStrategy 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-- MicroStrategy 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:

Comments

Microstrategy "Error type: Odbc error. Odbc operation attempted

"Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HYT00:0: on SQLHANDLE] [MicroStrategy][ODBC Oracle Wire Protocol driver]Timeout expired" is shown when executing reports from Web When users are trying to execute some reports in MicroStrategy web in particular, they may receive the Error “SQL Generation Complete Index out of range” and “Timeout expired” error as shown below: Possible Causes: One possible cause is that the MicroStrategy Intelligence Server using a cached database connection that was already dropped by the RDBMS. To resolve this: Admin should delete the database connection caches and create a new DSNs in case they are sharing DSNs to connect to different databases. In addition, change the settings for the ‘Connection lifetime’ and the ‘Connection idle time out’. Follow the steps below to perform the mentioned changes and verify the report after each step and some of the settings require i-server r...

mstrio – Python and R wrappers for the MicroStrategy

mstrio – Python and R wrappers for the MicroStrategy REST APIs Connecting to MicroStrategy Create a connection to the Intelligence Server using Connection() and  connect() in Python and R, respectively. Required arguments for the   Connection()  function are the URL for the MicroStrategy REST API server, MicroStrategy Intelligence Server username and password, as well as the MicroStrategy project name. By default, the  connect()  function anticipates your MicroStrategy Intelligence Server username and password. LDAP authentication is also supported. Use the optional argument  login_mode=16  in the  connect()  function for LDAP authentication. Extract data from cubes and reports To extract data from MicroStrategy cubes and reports, use the get_cube()  and  get_report() functions. Use...

Microstrategy Dossiers explained

Microstrategy Dossiers With the release of MicroStrategy 10.9, we’ve taken a leap forward in our dashboarding capabilities by simplifying the user experience, adding storytelling, and collaboration.MSTR has evolved dashboards to the point that they are more than dashboards - they are interactive, collaborative analytic stories . Ultimately, it was time to go beyond dashboards, both in concept and in name, and so the've renamed VI dashboards to ‘ dossiers ’. Dossiers can be created by using the new Desktop product or Workstation or simply from the Web interface which replaces Visual Insights. All the existing visual Insights dashboards will be converted to Dossiers With MicroStrategy 10.9, there was an active focus on making it easier to build dashboards for the widest audience of end users. To achieve this, some key new capabilities were added that make it easier to author, read, interact and collaborate on dashboards ...

MicroStrategy URL API Parameters

MicroStrategy URL Structure The following table summarizes the root URL structure used for every request to MicroStrategy Web. Environment Main Application URL Administration URL J2EE http://webserver/MicroStrategy/servlet/mstrWeb http://webserver/MicroStrategy/servlet/mstrWebAdmin .NET http://webserver/MicroStrategy/asp/Main.aspx http://webserver/MicroStrategy/asp/Admin.aspx Every request sent to MicroStrategy Web calls a central controller. Parameters are appended to Main.aspx or mstrWeb (in a .NET and J2EE environment, respectively) to indicate to the controller how the request should be internally forwarded and handled. The following examples show a URL for accessing a MicroStrategy folder when the user does not have an existing session. The URL contains not only the parameters needed to connect to MicroStrategy Web, but also the parameters needed to log on and create a session. J2EE environment: <a href="http:...

Prompt-in-prompt(Nested Prompts) in Microstrategy

Prompt-in-prompt(Nested Prompts) in Microstrategy Nested prompts allows you to create one prompt based on the other and other bases on another, nested prompts allows us to prompt the highest level(Like year) to middle level(like Quarter, then to the low level(like Month). Here you can see how to create a 3-level deep nested prompt that will prompt the user to select a year, then a quarter within that year, then a month within that quarter. Prompt-in-prompt is a feature in which the answer to one prompt is used to define another prompt. This feature is only implemented for element list prompts . The following procedure describes how to achieve this: Create the highest level filter. This is a filter which contains a prompt on an attribute element list. Create a filter on the attribute "Year." Click "prompt on attribute element list" and click "Next" through the rest of the screens to accept the default values. Do not set any additio...

MicroStrategy VLDB properties with Hive

Recommended VLDB Properties for use of MicroStrategy 9 with Hive 0.7x The recommended VLDB optimizations for Hive 0.7x are listed below. These values are set by default when the "Hive 0.7x" database object is used (set at Configuration Managers > Database Instances > Database Instance > Database connection type ) Selected Default VLDB Properties for Hive 0.7x VLDB Category VLDB Property Setting Value Tables Fallback Table Type Permanent Table Tables Maximum SQL Passes Before FallBack 0 (no threshold) Tables Maximum Tables in FROM Clause Before FallBack 0 (no threshold) Tables Drop Temp Table Method Drop after final pass Tables Table Creation Type Implicit Table Query Optimizations Sub Query Type Use Temporary Table, falling back to IN (SELECT COL) for cor...

Create an alert-based subscription in MicroStrategy Distribution Services

Create an alert-based subscription in MicroStrategy Distribution Services on Web Subscription to a report or Report Services document which will be executed when a certain conditional threshold is met based on another executing report. For example, a scheduled report executes which shows the Revenue by day for the past week. If the Revenue on any one day falls below a certain value, a subscription to another report or Report Services document can be triggered and delivered to a recipient. An alert based subscription can only be created directly on a report; however, another report or Report Services document can be delivered when the alert based subscription is triggered. Note: you need a grid report to create an alert and you cannot create if you want to create on a document with text boxes. The following example will walk through the basic steps on how to setup a subscription based on an alert like this: Follow the brief steps bel...

Create a Visualization Filter in a Dossier

Create a Visualization Filter You can select attribute values to filter data that appears in a visualization by creating an attribute filter. Create a visualization filter by dragging attributes and metrics from the Datasets panel. To create an attribute filter Open the dossier you want to modify. Select the chapter that contains the visualization to filter. Click Filter . An empty filter appears in the dossier. Drag the attributes and metrics for filtering from the Datasets panel to the empty filter. Use the Ctrl key to select multiple attributes and metrics. In the filter, click Select Target . Click on target visualizations or visualization filters to select them. You can select targets across chapters and pages, as long as they are all on the same page. Click Apply . Click More in the filter and select options for modifying the filter. The available options are based on the objects you select.

HyperIntelligence and its Architecture

HyperIntelligence and its Architecture When you open a web page the extension automatically scans web pages in your browser and underlines keywords that you can hover over to trigger cards. Cards present predefined KPIs associated with a selected keyword sourced securely from MicroStrategy. This feature is similar to what we see in web pages particularly stock related web sites. MicroStrategy introduced HyperCards, a new object that is built, managed, and deployed using MicroStrategy Workstation(Not by using Developer or Desktop as far as I know). Cards can be consumed in a web browser via the MicroStrategy HyperIntelligence Chrome extension and on iOS devices via the MicroStrategy HyperMobile app. This feature can help the users to inject Zero-Click Intelligence (as it requires the users to hover only and no need to click!) about customers, products, people, and more directly onto words within websites or web application or emails. This feature can display the conte...

Microstrategy Caches explained

Microstrategy Caches Improving Response Time: Caching A cache is a result set that is stored on a system to improve response time in future requests. With caching, users can retrieve results from Intelligence Server rather than re-executing queries against a database. To delete all object caches for a project 1 In Developer, log into a project. You must log in with a user account that has administrative privileges. 2 From the Administration menu, point to Projects , and then select Project Configuration . The Project Configuration Editor opens. 3 Expand Caching , expand Auxiliary Caches , then select Objects . To delete all configuration object caches for a server 1 Log in to the project source. 2 From the Administration menu in Developer, point to Server , and then select Purge Server Object Caches . 4 Click Purge Now . To purge web cache follow the steps in the link ...

Microstrategy Analytics

Search This Blog