Skip to main content

Using Scan MD Microstrategy

ScanMD 

WHAT IS SCAN MD?
ScanMD is a troubleshooting application whose aim is to provide a quick resolution to known metadata logical inconsistencies.  Logical inconsistencies are errors within an object's definition structure. The word 'known" means that those erroneous structures have already been investigated and processed by MicroStrategy Technical Support and, as a result, a Test has been implemented in ScanMD. 
It is not the intention that ScanMD be used as a proactive method for addressing metadata inconsistencies.  If you find yourself proactively running ScanMD and/or finding inconsistencies through ScanMD then please contact MicroStrategy Technical Support as this means that there is, most likely, a deeper problem to be investigated.
Refer to the following technical note if ScanMD is going to be executed against a 10.3 and higher metadata:
CONSIDERATIONS/GUIDELINES
  • ScanMD is to be used as a troubleshooting application and a vehicle to provide a quick resolutionafter a problem has been identified as a metadata inconsistency. In other words, ScanMD should not be run on a "schedule" or "after every migration". 
  • Before running ScanMD, a database backup of the metadata must be made. With a backup of the metadata in place, proposed fixes should only be accepted if the full impact of the fix is understood.
  • When a Fix is performed on a project, the MicroStrategy Intelligence Server should be stopped, or that Project unloaded.  No users should be connected to the project undergoing a fix.
  • Always use the latest version of ScanMD, which is the one supplied in this document.
  • For cases where ScanMD is used, there may still be questions as to how the metadata got into this state.  To help answer that question --  customers encountering inconsistency issues should make note of Schema-related changes (if the problem is affecting Schema objects), Object Migrations, or error messages prior to experiencing the problem.  Change Journaling, if it has been enabled, can help in preserving this information.
Microstrategy's disclaimers and Limitation of Liabilities about using ScanMD:

Disclaimer:The utility application is provided "as is" and without warranty of any kind. Microstrategy Expressly disclaims all warranties, express, implied or statutory, including, without limitation, the implied warranties of merchantability, fitness for a particular purpose, satisfactory quality and noninfringement.
Limitation of Liability: Microstrategy shall have no liability to licensee for any damages of any kind, including, but not limited to, liability for direct, indirect, special, incidental or consequential, damages (which shall include, but not be limited to, loss of data or information, loss of revenue or anticipated profits or lost business).
SCANMD CHECK-ONLY MODE
The current version of ScanMD does not provide the ability to execute one or more common tests in check-only mode. Due to the new feature enforcing the inter-object dependencies, check-only mode is not possible in this release. Consider one example, before executing  Schema Collection Verification test which ensures all schema objects are in the Schema collection, the ScanMD will execute Table Verification test and eliminate table objects with invalid definition. Therefore, the execution sequence is crucial to maintain the metadata consistency. Check-only mode may generate misleading results by ignoring inter-object dependencies and execution sequence.
HOW TO USE SCANMD
Follow steps below:
  1. Go to Start -> Programs -> MicroStrategy -> Tools, run ScanMD
  2. Click Nextto pass ScanMD introduction to the next step, which is Step 1of ScanMD
  3. In Step 1, choose a Project Source from the drop down list, and enter a Login and a Passwordthat have administrative privileges to the metadata. Click Next to go to Step 2
  4. In Step 2, choose a single project, All Projects , or Configuration from the drop down list. Select a different location for log file if desired. Click Next to go to Step 3

      
    NOTE: During the transition from Step2 to Step3, ScanMD will check the compatibility between the Metadata Version and the version of the MicroStrategy platform present on the machine where ScanMD is running.


  5. In Step 3, choose between Common Tests and Custom Tests. If a Custom Test is not yet added, click Add test to browse to its location. Make your test selections, and Click Next to go to Step 4;



    NOTE:
    - Multiple Common Tests can be chosen at once, but only one Custom Test can run one at a time.
    - Either Common Tests or Custom Tests can be selected, but not both.

  6. In Step 4, adjust tests against project(s) chosen in Step 2, select a Number of concurrent test executions, choose whether to Fix all errors automatically or not, and click Next to begin the scan; If any errors are found, ScanMD will pop up a dialog for each set of Common Tests that was executed.


    NOTE:
    - Some ScanMD Common Tests must be run in a specific order. As of ScanMD 8, the execution order of the Tests is enforced. If Common Tests is chosen in Step 3, ScanMD will automatically add any other Common Tests that are required. 

    Based on your test selections, Scan MD has identified some additional tests which need to be run in order to ensure the integrity of your Metadata.
The required tests will be added to your selections.

    Though only "Attribute Verification" and "Hierarchies Verification" are selected, four other common tests are added with suffix "(Required)":

    - Those Tests which do not have any dependencies are still allowed to execute in parallel.
    - "Concurrent test executions" usually reduce the overall execution time when running on a computer with multiple cores or CPUs and against remote MDs (i.e. not a local DB such as Access).

  7.  In the Summary Step, select "Check here to open the log file" if you wish to review, after clicking Close, the actions that ScanMD performed. Otherwise, simply click Close. 

    ScanMD Test Results:

    ScanMD Summary step:

  8. Restart Intelligence Server if the changes cannot be reflected in 3-tier environemnt.  

Labels:

Comments

Post a Comment

Popular posts from this blog

Microstrategy Custom number formatting symbols

Custom number formatting symbols If none of the built-in number formats meet your needs, you can create your own custom format in the Number tab of the Format Cells dialog box. Select  Custom  as the Category and create the format using the number format symbols listed in the table below. Each custom format can have up to four optional sections, one each for: Positive numbers Negative numbers Zeros Text Each section is optional. Separate the sections by semicolons, as shown in the example below: #,###;(#,###);0;"Error: Entry must be numeric" For more examples, see  Custom number formatting examples . To jump to a section of the formatting symbol table, click one of the following: Numeric symbols Character/text symbols Date and time symbols Text color symbols Currency symbols Conditional symbols Numeric symbols For details on how numeric symbols apply to the Big Decimal data type, refer to the  Project Design Guide . ...
4 comments
Read more

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:...
2 comments
Read more

Case functions Microstrategy

Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. In general, a user specifies a list of conditions and corresponding return values. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. If all conditions are false, a default value is returned.  Case  can be used for categorizing data based on multiple conditions. This is a single-value function. Syntax Case ( Condition1 ,  ReturnValue1 ,  Condition2 , ReturnValue2 ,...,  DefaultValue ) Example Case(([Total Revenue] < 300000), 0, ([Total Revenue] < 600000), 1, 2) sum(Case (Day@DESC in (“Sat”,”Sun”), Sales, 0) {~+} Sum(Case(Category@DESC In("Books","Electronics"),Revenue,0)){~+} CaseV (case vector) CaseV  evaluates a single metric and returns different values according to the results. It can be used to perfo...
3 comments
Read more

Settings for Outer Join between metrics in MicroStrategy

Settings for Outer Join between metrics in MicroStrategy MicroStrategy adopts multi-pass logic to determine the execution plan for a report. This means that every metric is evaluated in separate SQL passes. Outer Joins come into play when MicroStrategy Engine merges the results from all SQL passes into one report. For a multi-pass report, different Outer Join behaviors can give the user completely different results. In addition, report metrics can be of different types which can, in some cases, influence the result of the outer join. In MicroStrategy, there are two settings that users can access to control Outer Join behavior : Formula Join Type and Metric Join Type . Metric Join Type: VLDB Setting at Database Instance Level Report and Template Levels Report Editor > Data > Report Data Options Metric Level   Metric editor > Tools > Metric Join Type Control Join between Metrics Formula Join Type: Only at Compound/Split...
Post a Comment
Read more

Control the display of null and zero metric values

Show   Control the display of null and zero metric values in a grid report You can determine how to display or hide rows and columns in a grid report that consist only of null or zero metric values. You can have MicroStrategy hide the rows and columns in the following ways: Hide rows and columns that consist only of null metric values Hide rows and columns that consist only of zero metric values Hide rows and columns that consist only of null or zero metric values (default) Once you have defined how MicroStrategy hides null and zero metric values in the grid, you can quickly show or hide the grid using the Hide Nulls/Zeros option in the Data menu, as described below, or by clicking the  Hide Nulls/Zeros  icon  in the Data toolbar. To determine how null and zero metric values are displayed or hidden in a grid report Open the report in Edit mode. From the  Tools  menu, select  Report Options . The Report Options...
Post a Comment
Read more

Types of filters in Microstrategy

Types of filters in Microstrategy Below are the types of filters: 1. Attribute qualification filter These types of qualifications restrict data related to attributes on the report. a) Attribute form qualification Filters data related to a business attribute’s form(s), such as ID or description. •  For example, the attribute Customer has the forms ID, First Name, Last Name, Address, and Birth Date. An attribute form qualification might filter on the form Last Name, the operator Begins With, and the letter H. The results show a list of customers whose last names start with the letter H. b) Attribute element list qualification Filters data related to a business attribute’s elements, such as New York, Washington, and San Francisco, which are elements of the attribute City. • For example, the attribute Customer has the elements John Smith, Jane Doe, William Hill, and so on. An attribute element list qualification can filter data to display only those customer...
5 comments
Read more

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...
3 comments
Read more

Types of result caches in Microstrategy

Types of result caches Microstrategy The following types of  result caches are created by Intelligence Server: • Matching caches • History caches • Matching-History caches • XML caches All document caches are Matching caches; documents do not generate History caches or XML caches. Intelligent Cube reports do not create Matching caches. Matching caches Matching caches  are the  results of reports and documents that are retained for later use by the same requests later on. In general, Matching caches are the type of result caches that are used most often by Intelligence Server. When result caching is enabled, Intelligence Server determines for each request whether it can be served by an already existing Matching cache. If there is no match, it then runs the report or document on the database and creates a new Matching cache that can be reused if the same request is submitted again. This caching process is managed by the system administrator and ...
Post a Comment
Read more

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...
Post a Comment
Read more

Images in Microstrategy PDF Export shows Red X

When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9.4.1 and 10.x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X". When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9.4.1 and 10.x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X" as shown below: However, the images in the report display properly when the report is executed in MicroStrategy Developer and Web. Furthermore, when the report is exported to PDF on Desktop (with the original images saved in WebASPX\Images), the images in the report display properly, as indicated below: CAUSE This is expected behavior. When the report is displayed in MicroStrategy Developer and Web, or when the report is exported to PDF from MicroStrategy Dev...
1 comment
Read more