How do I deal with the errors reported in the ETL status report?

• https://knowledge.exlibrisgroup.com/@api/deki/files/45884/ETL_errors_explanation.docArticle Type: General
• Product: Aleph
• Product Version: 2

Description:
In ARC2 the ETL Status report contains 8 separate reports, but there seem to be no instructions for what to do about the errors they report.

For example both the General Error Messages and the Transfrom and Load Detailed reports report unique constraint violations - what should I do about these? If records are wrong, I need to know which records, but for example the latest Transfrom and Load Detailed one says the "Transform Load Bad Record" is "BOOK;Book;".

Similarly, the Value Validation Test Detailed reports gives lists like "Field Name - Arrival_date, Erroneous value - 20030023", or "Field Name - Issue_date, Erroneous value - 70000" I need to know which records in Aleph have these erroneous values in. In these cases I suppose I can find them by sql but surely it would be easier to have the information in the ARC report?

The detailed report from "Extract from Aleph to Disk", apart from the known issue with Mrr_opac, shows two errors concerning the p_arc_01 log files - one says "File size too large" and the other "Error - can't write to file" - what should I do about these?

The Mirror tables creation one does show that a tablespace needs extending, so that is useful.

Several of the reports have columns in for Start time' and 'End time' but in fact they are formatted (I presume) to just show the date, not the times, which is not helpful.

Resolution:
Please see the detailed explanation in the attached document.
This issue is still open and was escalated to Second line support for further analysis <2008-01-06 01:00:02>.