About
Oracle Database lets you save filled groups of Oracle Database - Redo Log (Transaction Log Files) files to one or more offline destinations, known collectively as the archived Oracle Database - Redo Log (Transaction Log Files), or more simply the archive log. The process of turning redo log files into archived redo log files is called archiving. This process is only possible if the database is running in ARCHIVELOG mode. You can choose automatic or manual archiving.
You can use archived redo logs to:
- Recover a database
- Update a standby database
- Get information about the history of a database using the LogMiner utility
A database is CREATED in noarchivelog to avoid the generation of tons of archives from the create itself.
Article
Development/ production environment
In development, our bulk inserts work very fast and generate very little redo. When we move into production, our Oracle Database - Direct (path insert|load) (/*+ APPEND */) statements work much slower and generate many gigabytes of Oracle Database - Redo Log (Transaction Log Files), filling up our Oracle Database - Mode Archive Log / Archiving destination. What's going wrong ?
It is not that anything is going wrong. It is that many people run the development and test machines in Oracle Database - NOARCHIVELOG mode and production in Oracle Database - ARCHIVELOG mode.