Can anybody let me know the difference between ARCHIEVELOG mode and NO ARCHIVELOG mode of database operations. Please let me know the differences. Thank you very much in advance.
Can anybody let me know the difference between ARCHIEVELOG mode and NO ARCHIVELOG mode of database operations. Please let me know the differences. Thank you very much in advance.
If you run in NOARCHIVELOG mode, if your database crashes, you can only recover to the point of time of your last backup.
ARCHIVELOGMODE allows you to recover to the point of the crash. Downside is it takes more diskspace and can cause the db to freeze if that disk fills up. If you have a production system with no tolerance for loss, this isn't an option.
If you're running a DW that does nightly loads, then you can get away with NOARCHIVELOG mode most likely.
Please go read the Oracle Certification docs on the Backup & Recovery process. Pay special attention to the RMAN section.
Toad has answered this question. Answer is : If we run in NOARCHIVELOG mode, if the database crashes, we can only recover to the point of time of our last backup.
ARCHIVELOGMODE allows us to recover to the point of the crash. Downside is it takes more diskspace and can cause the db to freeze if that disk fills up. If we have a production system with no tolerance for loss, this isn't an option.
I have used NOARCHIVELOG mode for some Dev Databases. Performance is a little better with NOARCHIVELOG as there is no overhead for writing the Archived Redo Logs to the Archive Log Destinations. (Keep in mind that ONLINE redo logs are always written to, no way around that).
That being said the customer was informed of and accepted the fact that they could only restore to the previous full backup. Since they were Development systems that could be rebuilt with scripts this was not an issue.
Running in archivelog mode also enables you to run a dataguard standby that you can switch(or fail)over to as and when necessary.
No one has followed this question yet.