Here is the main report:

When you click on ‘General’ you will see:

Theses errors come from ‘prc_process_details’ oracle table.

Use the following SQL: select count(*), LOG_MESSAGE from prc_process_details group by LOG_MESSAGE having count(*)>1; ------

When you click on ‘Extract’ report you will see: Click on ‘Press to see error message’

You will get:

The errors in this report exist at ./ncl50/scratch

For example, file “p_arc_01_a_1.log” has:

I/O error : file '/exlibris/aleph/u18_1/ncl50/files/mrr_opac.seq.681' error code: 9/194 (ANS74), pc=0, call=1, seg=0 194 File size too large

This means that the ‘mrr_opac.seq.681’ which was created by the ETL process in ./ncl50/files is too big (probably more than 2 G). This probably caused the second error message: ‘Table mrr_opac Loaded 6213762 of 6213761 - Not all records were loaded’ (inside p_arc_01.log).

If you want, you can open a separate SI for this.

------

When you click on ‘Ref Integrity’ you will see:

From release notes of ARC 2.0.0:

Referential Integrity Test The purpose of the report is presenting values from the fact tables which do not have corresponding values in the dimension tables. Missing values are completed in the dimension tables. The Source of Data fields that were added to all dimensions in ARC V.1.1 contain the origin of the added values. The origin is one of the fact tables. Explanation of each column:  Dimension Table – The name of the dimension table from the DWH layer.  Fact Table – The name of the fact table from the DWH layer.  Compared Fields – The field which exists in both dimension and fact tables and is being compared.  Inserted Records Count – The content of this column is a number which represent the number of problematic values that were added to the dimension table. Clicking on the number displays another report: Referential Integrity Test Detailed. Referential Integrity Test Detailed This report presents the values that were added to the dimension table. Explanation of each column:  Dimension Table – The name of the dimension table from the DWH layer to which values were added.  Inserted record – This column contains the following information separated by semicolons: The inserted ID, its description, and its Source of Data. In the example below, ‘-‘ is a new ID, ‘-UnKnown’ is its new description, and its Source of Data is INVOICE_HEADER. - ; -UnKnown- ; INVOICE_HEADER Also: ‘APPROVAL 1‘ is a new ID, ‘APPROVAL 1UnKnown-‘ is its new description, and its Source of Data is INVOICE_HEADER. APPROVAL 1 ; APPROVAL 1UnKnown- ; INVOICE_HEADER Another example: ‘0‘ is a new ID, ‘0UnKnown-‘ is its new description, and its Source of Data is CASH. 0 ; 0UnKnown- ; CASH

------

When you click on ‘Value Validation’ you will see:

From Release Notes of ARC 2.0.0:

Value Validation Test The purpose of the report is identifying illegal values in columns. Most of the validations are date validations. Explanation of each column:  Table Name – The DWH table in which a value is not valid. Validation Field – The field in which a value is not valid.  Test Description – The description of the problem (for example: Invalid Date Value). Number of Invalid Rows – The content of this column is a number which represent the number of invalid values. Clicking on the number displays another report: Value Validation Test Detailed. Value Validation Test Detailed This report presents the values one of each DWH table that did not pass the validation test. Explanation of each column:  Field Name – The field in which the erroneous value exists.  Erroneous Value – The erroneous value it self.

In this example the ‘month’ is incorrect:

In this example the whole date is incorrect:

======For more information please refer to: ‘ARC 2.0.0 Release Notes’ document – section 5.2