- Article Type: General
- Product: Primo
- Product Version: 2
On our staging server we are sized for 1,000,000 records and have allocated 50Gb of space for redo/archive logging. Our library catalogue is approximately 690,000 records in size. When harvesting the full set of records we note that 11Gb of redo/archive logging space is used up.
The production environment is sized for 5,000,000 records but has the same allocation of space for redo/archive logging (50Gb). Based on the above figures for ueadbs16, if we harvested the full 5m records would we need closer to 80Gb of redo/archive logging in the production environment?
We are not planning to reach 5m records anytime soon but this is a query for future planning.
It is highly recommended to switch OFF the archiving during initial loads of millions of records. Archiving for such processes is both redundant and slowing performance.
It would be better to backup the DB before such large initial load, switch off the archiving, make a backup again at the end of the load, and then switch the archive on.
For ongoing small loads, you should manage the backup to remove old files.
If you are using Exlibris backup package, or any other RMAN script, then this is done automatically.
If you are using another mode of backup, you should do this on your own.
- Article last edited: 10/8/2013