Hi,
We want to change to hot backups to be able to do point in time recovery but without using RMAN. In order to do this, we want to change our database archiving mode to archivelog mode which I have never worked with before. Could someone help me please on the following:
- how best to estimate the amount of space required for the archive log destination.
- what happens if the space becomes full and database shuts down? If at that point the space is expanded and the database reopened, does everything continue as normal? If I'm unable to immediately get the space expanded and I manually copy the archive logs to a different destination and then restart the database, does everything continue as normal? Let us assume that I have only one archive log destination defined in my parameter file i.e. LOG_ARCHIVE_DEST = 'xyz_local'
- In a situation where there are 3 redo log groups (not multiplexed) - redo1.log, redo2.log, redo3.log - about how many archived log files am I expecting, presumably this will depend on log switches and how busy the database is? I'm not familiar with how this works so any help will be appreciated.
- How do the archived logs get cleared?
- I plan to schedule, locally on the database server (using a script), a nightly hot backup which will backup all the datafiles, control files, online redo, spfile, pw file and the archived logs to another partition on the server (This will then be backed up as part of the nightly server file system backup). Do I include in that script a delete of the logs in the archive log destination at that point? Presumably the archiver will not try to archive any full online redo log at that point as the database will be in backup?
Any helpful information on how best to implement this will be much appreciated. Thank you very much in advance. Please note that I have done some reading up on the subject but still not clear on the above points.