Skip to main content
ExLibris
  • Subscribe by RSS
  • ExLibris Dev

    Clean-up of z73 table and last-loader-log-no

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

    Description:
    First, do you know if there happens to be anything coming down the pike from EL software development with regard to cleaning out the z73 tree of old data?

    Second, if there is not and I need to write my own, will I need to also reset the last-loader-log-no value when I locally empty out the z73 table? Or would you suggest I just let it keep going up?

    I know that I set the value of that parameter to 0 when we upgraded, and I thought that z73 started out empty, but I cannot be sure about that
    part. I'm a bit surprised that we did not find this problem a bit faster because I thought that this value had something to do with OCLC loading as well as BNA and Marcive loads, but perhaps I'm forgetting something with regard to this. Anyway, I do want to clean up regularly in the future, but don't want to cause other problems if/when I do so.
    [ <Jerry Specht > ]

    Resolution:
    1. I don't know of any plan for an ALEPH job to clean up the z73.

    2. You would *not* want to reset the last-loader-log-no. The Z73's with the highest log numbers -- the ones which you will be most likely to want to preserve -- will be the ones with the highest last-loader-log-no's.


    • Article last edited: 10/8/2013
    //doorbell.io feedback widged