MicroStrategy ONE

Statistics Are Not Being Logged

If statistics are being logged but some data is being lost, the load on your system may be too high. For ways to decrease the system load, see Tune Your System for the Best Performance.

If statistics do not appear to be logged for your project, first verify that the Intelligence Servers to be monitored are correctly logging information in the statistics tables and that these tables are in the correct locations in the statistics and Enterprise Manager repository. The table names beginning with STG_ are the staging tables. The Intelligence Server logs information there until the Enterprise Manager data load process moves the information to the table of the same name without the STG_ prefix.

When the statistics tables are created using the MicroStrategy Configuration Wizard, they must be created in the database to be used as the Enterprise Manager warehouse.

The following Structured Query Language (SQL) scripts can confirm whether statistics are being recorded correctly. They should be executed using a native layer query tool (for example, SQL+ for Oracle, Query Analyzer for SQL Server).

  • Check statistics logged by user sessions:

    Copy 
    SELECT * FROM STG_IS_SESSION_STATS;
    SELECT * FROM IS_SESSION_STATS;

  • Check report-related statistics:

    Copy 
    SELECT * FROM STG_IS_REPORT_STATS;
    SELECT * FROM STG_IS_REP_STEP_STATS;
    SELECT * FROM STG_IS_REP_SQL_STATS;
    SELECT * FROM STG_IS_REP_SEC_STATS;
    SELECT * FROM IS_REPORT_STATS;
    SELECT * FROM IS_REP_STEP_STATS;
    SELECT * FROM IS_REP_SQL_STATS;
    SELECT * FROM IS_REP_SEC_STATS;

  • Check schedule-related statistics:

    Copy 
    SELECT * FROM STG_IS_SCHEDULE_STATS;
    SELECT * FROM IS_SCHEDULE_STATS;

  • Check cache-related statistics:

    Copy 
    SELECT * FROM STG_IS_CACHE_HIT_STATS;
    SELECT * FROM IS_CACHE_HIT_STATS;

  • Check document-related statistics:

    Copy 
    SELECT * FROM STG_IS_DOCUMENT_STATS;
    SELECT * FROM STG_IS_DOC_STEP_STATS;
    SELECT * FROM IS_DOCUMENT_STATS;
    SELECT * FROM IS_DOC_STEP_STATS;

For a detailed list of the statistics tables and columns, see Enterprise Manager Data Dictionary.

If data is not being logged to statistics, or the information is not up to date, possible reasons include:

  • Intelligence Server has shut down while jobs were still executing. Statistics are not logged for jobs that do not complete beforE Intelligence Server shuts down. This applies to both a manual shutdown and to an unexpected shutdown.
  • The statistics database is not selected in the Project Configuration dialog box.

    To check this, right-click a project that should be logging statistics and select Project Configuration. Then select the Statistics category and confirm that the correct database instance is selected.

  • The statistics database instance has not been configured correctly.

    To check this, expand the Administration section for the project source that should be logging statistics. Select Database Instance Manager. Right-click the statistics database instance and select Edit. Then verify the database connection type, data source name (DSN), and default database connection.

  • The statistics database DSN has not been configured correctly.

    To check this, open the Windows Open Database Connectivity (ODBC) Data Sources for the machines where the Intelligence Servers logging statistics are installed. Verify that the DSN used by the Statistics Database Instance are defined correctly using certified drivers to connect to the statistics and Enterprise Manager repository. For a list of certified databases, see the Readme.

  • If the Intelligence Servers for the projects being monitored and the database server do not have synchronized clocks, some data may be incorrect in the statistics tables. For example, if statistics appear for "Deleted report" in Enterprise Manager reports, it may be because statistics are being logged for reports that according to the warehouse's timestamp should not exist.
  • If you are using single instance session logging and the specified project is not one of the monitored projects, no data for any monitored project is logged. To check this, open the Intelligence Server Configuration Editor to the Statistics: General category and confirm that the project selected in the single instance session logging drop-down list is one of the monitored projects. For more information about single instance session logging, see Logging All Statistics from a Project Source to the Same Database.

Statistics Logging Suddenly Stops

If statistics logging for a project suddenly stops, one or more of the following factors may be the cause:

  • The database server hosting the statistics database may not be running.
  • The database connection from Intelligence Server to the statistics database server may have failed.
  • A heavy load on the statistics database may have caused statistics logging to shut down.
  • The login or password for the statistics database may have been modified or expired.
  • Intelligence Server may have stopped logging statistics.