Skip to main content
ExLibris
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Z73: its purpose and mechanism for cleaning

    • Article Type: General
    • Product: Aleph
    • Product Version: 18.01

    Description:
    I've been reviewing the z73 table which is a new log of MARCIVE and OCLC loader information. I'm unclear on the purpose for this table. Were there previously no logs for these activities, or just no logs to a database table? What drove the decision to start logging this information into a database table?

    And is this information expected to be saved permanently? I see no util command which is meant to clean out the information in this table, but it seems like this kind of data has very little usefulness after a load is completed. I can see wanting to know the status shortly after the load was completed, but why would I care about a load which happened months ago. As it stands, the information stored in this table would remain there indefinitely, which seems a little overkill.

    Resolution:
    > Were there previously no logs for these activities, or just no logs to a database table?

    <<js Just no logs to a database table.

    > What drove the decision to start logging this information into a database table?

    <<js One factor may be the ability to have a common logging location for both the batch (p_file_99, p_file_93) and the oclc_server, that is, everything using the generic loader programs.

    > And is this information expected to be saved permanently?

    <<js No, it is not.

    I am passing this on as an enhancement request. In the meantime, you can periodically use the following SQL to delete older z73 records:

    SQL> delete from z73 where Z73_OPEN_DATE_X < 'yyyymmdd';

    <where "yyyymmdd" is the cutoff date for saving z73 records>


    This issue is still open and was escalated to Development for further investigation <2007-10-21 01:00:04>.


    • Article last edited: 10/8/2013
    • Was this article helpful?