Dynamic sourcing log files

In the Diagnostics and Performance Logging tool, all of the dynamic sourcing log files are available on the Diagnostics Configuration tab as part of the Dynamic Sourcing component, as shown in the image below. For information on accessing the Diagnostics and Performance Logging tool, see the System Administration Help.

With the Diagnostics and Performance Logging tool, you can enable the following dynamic sourcing log files to track information about the use of dynamic sourcing.

Intelligent Cube parse log

Information about an Intelligent Cube is included in the Intelligent Cube parse log when the Intelligent Cube is published and made available by Intelligence Server.

This log displays whether an Intelligent Cube has been defined to be available for dynamic sourcing. It also lists any metrics included in the Intelligent Cube that are disabled for dynamic sourcing, and other issues that may prevent the Intelligent Cube from being available for dynamic sourcing. For explanations of various error codes that can be included in this log, see Dynamic sourcing error codes and explanations.

If the entries in this log for an Intelligent Cube end with CMI_NO_ERROR, this means the Intelligent Cube is available to reports for dynamic sourcing. Be aware that some of the metrics in an Intelligent Cube still may not be available for dynamic sourcing. You can review this log to determine whether any metrics for the Intelligent Cube are not available for dynamic sourcing.

You can also display this log in the SQL View of Intelligent Cubes. This can help determine which reports use dynamic sourcing to connect to the Intelligent Cube, as well as why some reports cannot use dynamic sourcing to connect to the Intelligent Cube. The steps below show you how to include this log for Intelligent Cubes in a project.

To display the Intelligent Cube parse log in Intelligent Cubes

In Developer, log in to a project.
Right-click the project and select Project Configuration. The Project Configuration Editor opens.
Expand the Project definition category, and select the Advanced category.
Within the Analytical Engine VLDB properties area, click Configure. The VLDB Properties Editor opens.

The VLDB property defined using the steps below can also be defined for individual Intelligent Cubes. To access the VLDB Properties Editor for an Intelligent Cube, with the Intelligent Cube open, from the Data menu, select VLDB Properties.
From the Tools menu, ensure that the Show Advanced Settings option is selected.
In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Cube Parse Log in SQL View.
Clear the Use default inherited value check box.
Select Enable Cube Parse Log in SQL View.
Click Save and Close to save your changes and close the VLDB Properties Editor.
Click OK.

Report parse log

When a report is executed, information about the report is included in the report parse log.

Reports connected to a specific Intelligent Cube do not send information to the report parse log.

This log lists any reasons why a report cannot use dynamic sourcing. For explanations of various error codes that can be included in this log, see Dynamic sourcing error codes and explanations.

If the entries in this log for a report end with CMI_NO_ERROR, this means the report can use dynamic sourcing. However, this does not necessarily mean that dynamic sourcing is used; an Intelligent Cube that meets the data requirements for the report must be available.

The report parse log can increase in size quickly and thus is best suited for troubleshooting purposes.

You can also display this log in the SQL View of reports. This log helps determine whether a report can use dynamic sourcing to connect to an Intelligent Cube. The steps below show you how to include this log for reports in a project.

To display the report parse log in reports

In Developer, log in to a project.
Right-click the project and select Project Configuration. The Project Configuration Editor opens.
Expand the Project definition category, and select the Advanced category.
Within the Analytical Engine VLDB properties area, click Configure. The VLDB Properties Editor opens.

The VLDB property defined using the steps below can also be defined for individual reports. To access the VLDB Properties Editor for a report, with the report open, from the Data menu, select VLDB Properties.
From the Tools menu, ensure that the Show Advanced Settings option is selected.
In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Report Parse Log in SQL View.
Clear the Use default inherited value check box.
Select Enable Report Parse Log in SQL View.
Click Save and Close to save your changes and close the VLDB Properties Editor.
Click OK.

Mismatch log

When a report that can use dynamic sourcing is executed, which can be verified with the report parse log, and Intelligent Cubes are available for dynamic sourcing, information about whether a matching Intelligent Cube can be found for the report is included in the mismatch log.

The mismatch log can increase in size quickly and thus is best suited for troubleshooting purposes.

This log lists any reasons why a report cannot use a specific Intelligent Cube to satisfy its data requirements. For explanations of various error codes that can be included in this log, see Dynamic sourcing error codes and explanations.

If the entries in this log for a report and Intelligent Cube combination end with CMI_NO_ERROR, this means the report can use dynamic sourcing to access the Intelligent Cube.

If dynamic sourcing cannot be used because of a metric (CMI_NO_GOOD_METRIC_FOUND), information on why the metric prevents the use of dynamic sourcing is provided in the extended mismatch log.

You can also display this log in the SQL View of reports. This log helps determine why a report that can use dynamic sourcing cannot connect to a specific Intelligent Cube. The steps below show you how to include this log for reports in a project.

To display the mismatch log in reports

In Developer, log in to a project.
Right-click the project and select Project Configuration. The Project Configuration Editor opens.
Expand the Project definition category, and select the Advanced category.
Within the Analytical Engine VLDB properties area, click Configure. The VLDB Properties Editor opens.

The VLDB property defined using the steps below can also be defined for individual reports. To access the VLDB Properties Editor for a report, with the report open, from the Data menu, select VLDB Properties.
From the Tools menu, ensure that the Show Advanced Settings option is selected.
In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Mismatch Log in SQL View.
Clear the Use default inherited value check box.
Select Enable Mismatch Log in SQL View.
Click Save and Close to save your changes and close the VLDB Properties Editor.
Click OK.

Extended mismatch log

However, if dynamic sourcing cannot be used because of a metric (CMI_NO_GOOD_METRIC_FOUND), information on why the metric prevents the use of dynamic sourcing is provided in the extended mismatch log. This information is listed for every metric that prevents the use of dynamic sourcing.

The extended mismatch log can increase in size quickly and thus is best suited for troubleshooting purposes.

You can also display this log in the SQL View of reports. This log helps determine why a metric prevents the use of dynamic sourcing is provided in the extended mismatch log. The steps below show you how to include this log for reports in a project.

To display the extended mismatch log in reports

In Developer, log in to a project.
Right-click the project and select Project Configuration. The Project Configuration Editor opens.
Expand the Project definition category, and select the Advanced category.
Within the Analytical Engine VLDB properties area, click Configure. The VLDB Properties Editor opens.

The VLDB property defined using the steps below can also be defined for individual reports. To access the VLDB Properties Editor for a report, with the report open, from the Data menu, select VLDB Properties.
From the Tools menu, ensure that the Show Advanced Settings option is selected.
In the VLDB Settings list, expand Dynamic Sourcing, and then select Enable Extended Mismatch Log in SQL View.
Clear the Use default inherited value check box.
Select Enable Extended Mismatch Log in SQL View.
Click Save and Close to save your changes and close the VLDB Properties Editor.
Click OK.

Metric levels log

When a report that can use dynamic sourcing is executed, which can be verified with the report parse log, information about the report is included in this log, including:

The lowest level attributes on a report, which defines the report level
The formulas of metrics on the report

This information can help determine what attributes and metrics need to be included in an Intelligent Cube for the report to be able to connect to it through dynamic sourcing.

This log file can also be used with MicroStrategy Cube Advisor to recommend and create Intelligent Cubes that could be connected to by reports using dynamic sourcing. For information on how Cube Advisor allows you to create and support a dynamic sourcing strategy that can best support the reports in your projects, see Using Cube Advisor to support dynamic sourcing.

Fact levels log

When a report that can use dynamic sourcing is executed, which can be verified with the report parse log included in this log. This log tracks the same information as the metrics levels log. The only difference is that the fact levels log lists the facts used for metrics rather than the metric formulas.