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

    Turning Oracle archive logging off for p_manage_01

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

    Description:
    We have 1.5 million bib records. We are planning to run p_manage_01. Should we turn Oracle archive logging off when we do this?

    Resolution:
    I estimate that p_manage_01 on 1.5 million records will take 12 - 20 hours. Running the job with archiving off requires a complete cold backup both before and after the job. Savings from turning archiving off depends on how long the cold backup takes.

    Running the job with Oracle archiving off involves:

    Prepare p_manage_01 csh command to run from command line
    Shut down Aleph and Oracle
    Do complete cold Oracle backup
    Bring Oracle and Aleph back up
    Immediately do:
    util w/2/1 to shut down all servers
    util w/5 T 1 to Toggle System down
    Do util o/7/2 (or native Oracle command) to turn Oracle archiving off
    Enter p_manage_01 csh command prepared in first step
    <p_manage_01 runs>
    util w/5 T 2 to toggle www_server UP
    util w/3/1 to start www_server
    Do test OPAC Word searches to confirm Word indexing is OK
    Shut down Aleph and Oracle
    Do complete cold Oracle backup
    Bring Oracle and Aleph back up
    Do util o/7/1 (or native Oracle command) to turn Oracle archiving on
    Make sure that util w/5 shows the processes as Up and available

    [Note: This information will be added to Section 3 ("Turning Off Archive Logging") of the "How To Run Index Jobs" document.]

    I am unable to find the "Aleph batch jobs and oracle archive logging" document. I'm pretty certain that this document is no longer available. The reference to it will be removed from Section 3.

    Additional Information

    Oracle archive logging p_manage_01


    • Article last edited: 10/8/2013