• Article Type: General
• Product: Aleph
• Product Version: 20, 21, 22, 23

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:

There are two reasons you might want to turn archiving off in running manage-01 (or manage-02):  

  1. Disk space -- there have been problems with the /arch directory filling up the disk it resides on; see the following article in this regard:  Analyzing space problems due to excessive Oracle archive logs .  You should check how much space is available on the ./oradata/arch disk.

  2. Time -- Running manage-01 on 1.5 million records used to take 12 - 20 hours. Turning archiving off while it was running could save 4-6 hours.  But recently (in 2017), with modern disks, controllers, etc., sites have found manage-01 running much faster (in one case, 5 hours for 2 million bib records)

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