When you run your database in NOARCHIVELOG mode, you disable the archiving of the redo log. Get information about the history of a database using the LogMiner utility The database starts multiple archiver processes as needed to ensure that the archiving of filled redo logs does not fall behind. The background process ARC n automates archiving operations when automatic archiving is enabled. When the database is running in ARCHIVELOG mode, the log writer process (LGWR) cannot reuse and hence overwrite a redo log group until it has been archived. The archived redo log contains a copy of every group created since you enabled archiving. Should a_log1 become corrupted, then ARC n can still archive the identical b_log1. For example, if you are multiplexing your redo log, and if group 1 contains identical member files a_log1 and b_log1, then the archiver process (ARC n) will archive one of these member files. It includes the redo entries and the unique log sequence number of the identical member of the redo log group. You can choose automatic or manual archiving.Īn archived redo log file is a copy of one of the filled members of a redo log group. This process is only possible if the database is running in ARCHIVELOG mode. The process of turning redo log files into archived redo log files is called archiving. Oracle Database lets you save filled groups of redo log files to one or more offline destinations, known collectively as the archived redo log.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |