‘switch logfile’ not a correct method after hot backup
In order to be sure that all changes generated during a hot backup
are available for a recovery, Oracle recommends that the current online
log be archived after the last tablespace in a hot backup is taken out
of backup mode. A similar recommendation stands for after a recovery
manager online database backup is taken.
Many DBA’s or Oracle books will suggest using the ‘alter system switch logfile’ command to achieve this. The use of ‘switch logfile’ to obtain archives of the current logs is not a perfect to follow. Because the command returns success as soon as the log writer has moved to the next log, but before the previous log has been completely archived. This could allow a backup script to begin copying that archived redolog before it is completely archived, resulting in an incomplete copy of the log in the backup.
A better command to use for archiving the current log is ‘alter system archive log current.’
This command will not return until the current log is completely archived.
For the same reasons outlined above, a backup script should never just back up “all the archived redologs.” If a script does not restrict itself only to those logs that it knows to be archived, it may improperly try to back up an archived redolog that is not yet completely archived.
To determine which logs are archived, a backup script should query the v$archived_log view to obtain a file list for copying.
Many DBA’s or Oracle books will suggest using the ‘alter system switch logfile’ command to achieve this. The use of ‘switch logfile’ to obtain archives of the current logs is not a perfect to follow. Because the command returns success as soon as the log writer has moved to the next log, but before the previous log has been completely archived. This could allow a backup script to begin copying that archived redolog before it is completely archived, resulting in an incomplete copy of the log in the backup.
A better command to use for archiving the current log is ‘alter system archive log current.’
This command will not return until the current log is completely archived.
For the same reasons outlined above, a backup script should never just back up “all the archived redologs.” If a script does not restrict itself only to those logs that it knows to be archived, it may improperly try to back up an archived redolog that is not yet completely archived.
To determine which logs are archived, a backup script should query the v$archived_log view to obtain a file list for copying.
No comments:
Post a Comment