sandeep vig

• Oct 13th, 2005

 

although u can perform any type of recovery while the database in archive log mode and if u have to configure dataguard environment then the database should be in archivelog mode.

Guest

• Jan 30th, 2006

 

database in archivelog mode  chance to take hot backup and no  data loss in recovery. you can use RMAN for backup and recovery .disadvantage is poor ferformance, and more chance to crash disc.

KS

• May 31st, 2006

 

If the database is in archieve log mode then performance is bit slower as compared to the no archieve log mode.

rush

• Nov 12th, 2006

 

hi,

A database backup guarantees that you can recover all committed transactions in the event of an operating system or disk failure.

           You can use a backup taken while the database is open and in normal system use if you keep an archived log.

              You can keep a standby database current with its original database by continually applying the original?s archived redo logs to standby

regards

rush

Chiranjeevi Manne

• Mar 30th, 2007

 

The main advantage of maintaining a database in Archivelog Mode is that it is possible to take the full backup of database while the database is up and running which in turn facilitates the Point In Time Recovery in case of database failure using the archived redologs and last known full backup

ora10g_dba

 Profile Answers by ora10g_dba 

• May 13th, 2008

 

In the Archivelog mode complet database recovery can be possilbe and in No Archivelog mode incomplet database recovery is possible.

oracleofdelphi

 Profile Answers by oracleofdelphi 

• Sep 9th, 2009

 

The one and only thing is that we can perform recovery where as in no archivelog mode we can only perform restore that is previous backup all transactions from then on is lost.

pandish

 Profile Answers by pandish Questions by pandish

• Dec 31st, 2010

 

Archivelog mode

============

Pros -

1. In this we can recover the database to any point in time between 2 backup timings this is called incomplete recovery.

 

2. We can use these archive logs to build/maintain standby database.

 

3. We can mine these logs to do analysis on past activity in database

 

Cons -

Some outdated cons -

1. Database performance is affected.

2. More space needed.

sandy8m

 Profile Answers by sandy8m 

• Apr 5th, 2011

 

Archive log is for maintaining the database in safest mode. If any data is loss in future, u can easily recover using archive logs. Recover command and reco background process uses archive logs to do their work. 

Transactions of redo logs are moved to archive logs. 

Archive logs are nothing but offline copies of online redos

kiran

• Jul 20th, 2011

 

If a Database is running in NoArchive log mode , when ever log switch happens there will be a loss of some redo log information in order to avoid this, redo logs must be archived. This can be achived by configuring database to run in Archivelog mode

Ganesh dere

• Aug 6th, 2014

 

In archivelog mode we can do point in time recovery of database. Noarchivelog mode it is not possible
and No archivelog mode performance will be better.

hari shankar

• Aug 5th, 2016

 

We can do a lot of things in archivelog mode.
1. Can take Hot backup
2. Complete or incomplete recovery
3. Can manage several policy
4. Take incremental back
5. No need to shutdown or offline or unavailability of database. and several other things can do in archivelog mod which can not do in noarchivelog mod.

Vikas

• Jan 9th, 2018

 

Too many !! High Availability (DATAGUARD,RAC), Point in time recovery, Flashback , Audits and many more.....