Troubleshooting the data loading process

If a data load does not complete or is not moving statistics for a project as you expected, you can check items that prevent the data load from working properly. You can also turn on logging features and then search those log files and table for causes of the problem. These are explained below.

• What can prevent a data load from working properly?

• Checking Enterprise Manager log files

What can prevent a data load from working properly?

Below are some of the reasons why a data load might not work for a project:

• Data cannot be loaded from a project that is not already loaded on Intelligence Server. Data also cannot be loaded from a project that is set to Request Idle, Execution Idle, or Full Idle mode.

Before loading data from a project, make sure the project is not in any of these idle modes and is set to Loaded status. For an explanation of the different project modes, including instructions on how to set a project's mode, see the System Administration Guide.

• If you have changed the password for the user that configured a project for Enterprise Manager, data cannot be loaded from that project until you reconfigure it. For steps, see Modifying a data load.

• If you have deleted a project in Developer that is being monitored by Enterprise Manager, the data load process fails until you remove that project from the list of projects being monitored.

• If Intelligence Server and Enterprise Manager cannot get to the statistics and Enterprise Manager repository, data cannot be recorded in the statistics database, and the data load process cannot run. Make sure the DSN for the repository is correct and that the database user has the permissions needed connect to and write data in the database. For steps, see Creating the Enterprise Manager repository.

• If the database connection for the statistics repository is not configured for parameterized queries the data load will fail. See Configuring database connections to use parameterized queries for more information.

• Data can be recorded only if statistics logging is enabled for a project. Make sure you configured your projects to log statistics to the statistics database. For steps on doing this, see the Monitoring the System chapter in the System Administration Help.

• If the project is not selected as part of a data load schedule, information for that project is not loaded into the Enterprise Manager repository. To ensure that it is enabled, see Modifying a data load.

• Check that the data load schedule is turned on. Also, if the MicroStrategy Enterprise Manager Data Loader service has stopped, no scheduled data loads occur. For steps on enabling a data load and on starting the data loader service, see Data loading.

Checking Enterprise Manager log files

Enterprise Manager can log information about the data load process, including all errors, into a table and several files. If a data load does not finish or has errors, you can search the table and files to find the cause of the problem. You can configure the following logging options:

• Information is recorded in the MAEntMgr.xml log file about the steps in the data load process, including any errors. This information includes the timestamp of steps such as the data load start, the project or object being processed, fact migration, any errors, and so on. This log is populated for every data load and cannot be turned off. You can, however, control how large the file gets before it is backed up. To do this, configure the Backup log every _ MB option. By default this file is stored in these locations, but you can change it for your system (see Configuring what Enterprise Manager data load information is logged):

  • In Windows: C:\Program Files (x86)\MicroStrategy\Enterprise Manager \

  • In UNIX/Linux: /<MSTR Home Path>/install/EnterpriseManager/

• If an error occurs when a SQL query executes as part of a data load, the MAEntMgr.xml file records that the error occurred, but does not store the SQL query that caused the error. To obtain the SQL query that caused the error open the MigrationSQL.log file, which is found in the following default locations:

  • In Windows: C:\Program Files (x86)\Common Files\MicroStrategy\Log\MigrationSQL.txt

  • In UNIX/Linux: /<MSTR Home Path>/log/MigrationSQL.log

• You can configure Enterprise Manager to record information into the EM_LOG table about the data load process. The information includes when data load started, the steps performed, and so on, which is similar to what is in the MAEntMgr.xml file. The EM_LOG table is in the Enterprise Manager repository. To view its contents, use a tool to query the database, such as the MicroStrategy DB Query Tool. You can also control how much history to keep in the table by configuring the Populate EM_LOG table and purge every _ rows option. For steps to enable this logging and control the table size, see Configuring what Enterprise Manager data load information is logged.

• You can configure Intelligence Server to record information in a diagnostics file that you specify, such as the DSSErrors.log file, about the data load process. This records detailed information for steps that Intelligence Server performed in the process. To turn on this logging, from the MicroStrategy Diagnostics and Performance Logging Tool, select the EM Migration Trace check box, from the File Log drop-down list, select the name of the log file to record the information in, and click Save. For steps to enable this logging and control the table size, see Configuring what Enterprise Manager data load information is logged. To view the log file, you can use the MicroStrategy Health Center Console.