This section describes how to run diagnostics test to ensure a successful configuration. You can run diagnostic tests in the system to ensure that Data Mart is working properly.
To run the diagnostic tests:
In Reporting Center, from the left navigation, select Reporting Tools > Datamart > Manage Marts > Data Mart.
You see the Data Mart workspace.Click the Administration link and then click Diagnostics.
You see the Data Mart Diagnostics dialog box.
Select the test you want to run from the Data Mart Diagnostic Dialog box.
Click Run Diagnostics.
The system initiates the diagnostic tests. Results are displayed in the Status column on the Data Mart Diagnostics dialog box.If a test is successful, a green check appears in the Status column. If a test fails, a red X appears in the Status column and an explanation of the error appears in the Error column of the row of the failed test.
Click Save Diagnostics to save diagnostics results as an Excel file.
Select Diagnostics Options
The following table describes each test you can run using the Data Mart Diagnostics dialog box.
Test | Description |
|---|---|
Engine Limit Ratios | Determines the proportion of available PACE Server engine events that can be taken up by the Model Manager Engines and the OLAP engines. The recommended figure is 0.25 (25%) for each engine type. The test fails if either ratio is set to 1.0. |
Event Instances | Determines whether each of the two Mart engine types has an entry in the PACE_MASTERDBO.EVENTS table. The test fails if either engine is absent from the table. |
Field Attributes | Data Mart uses two internal field attributes when you select the Always Composite Holdings check box on the Data Mart Configuration dialog box. Determines whether the two internal field attributes have a null value of field_type in the RULESDBO.FIELD_ATTRIBUTES table. The test fails if the field_type value = not null for either field. |
Field Indicator Mismatches | Checks for Field Indicator Mismatches. If you change a field attribute so that its Field Indicator changes, this causes a mismatch with a Data Mart field created from that field attribute. This is because a Data Mart table contains the Field Indicator. As a result of a Field Indicator change, the field attribute may not appear at all in the Fields tab of the Data Mart model user interface. You can fix mismatched from the Diagnostics dialog box. |
Get Column Info Procedure | Determines whether the Get Column Info stored procedure is present in each PACE database so that the Mart is able to insert new columns in Mart tables. The database user ID used to launch the PACE Application Server (typically pace_masterdbo) must have privileges to run the Get Column Info procedure in each database. The test fails if both criteria are not met. |
Get Unused Data Mart Fields | Displays a list of any problem fields. In early releases of PACE, deletion of fields from models did not always remove the fields from PACE system tables. This prevented a field attribute from being re-used with a different column name. |
Model Maintenance Permissions | Determines whether the database user ID that launches the PACE Application Server has privileges to create and delete group level models. The test fails if permissions do not exist. |
Multilingual Status | Determines if multilingual status is update. This option is available when using multilingual marts. If the status is up to date, a checkmark appears next to this option after you run diagnostics. |
Next Instances | Determines if the instance number of each Data Mart table is less than or equal to its next instance value in the PACE_MASTERDOB.NEXT_INSTANCE table. The test fails if this is not true for any Data Mart table. |
Add Comment