Oracle DBA Tutorial 7 - How to disable archive log mode

*****************************************************************************************
* How to disable archive log mode *
*****************************************************************************************

Running a Database in NOARCHIVELOG Mode

When you run your database in NOARCHIVELOG mode, you disable the archiving of the redo log. The database control file indicates that filled groups are not required to be archived. Therefore, when a filled group becomes inactive after a log switch, the group is available for reuse by LGWR.

NOARCHIVELOG mode protects a database from instance failure but not from media failure. Only the most recent changes made to the database, which are stored in the online redo log groups, are available for instance recovery. If a media failure occurs while the database is in NOARCHIVELOG mode, you can only restore the database to the point of the most recent full database backup. You cannot recover transactions subsequent to that backup.

In NOARCHIVELOG mode you cannot perform online tablespace backups, nor can you use online tablespace backups taken earlier while the database was in ARCHIVELOG mode. To restore a database operating in NOARCHIVELOG mode, you can use only whole database backups taken while the database is closed. Therefore, if you decide to operate a database in NOARCHIVELOG mode, take whole database backups at regular, frequent intervals.

NOARCHIVELOG mode is basically the absence of ARCHIVELOG mode and has the disadvantage of not being able to recover to any point in time.

Archive logs are archived redo(online) log files. In redo log files are all changes that happened to your data. If your database is in archivelog mode, than redo logs can't be overwritten, they are archived in some other location when they are full. Redo and archive logs are used in various database recovery scenarios.

Steps: ---
1. Log in as OS user, oracle and enter the following commands:

$ export ORACLE_SID=orcl
where orcl is the name of the database

In windows open cmd pront and login with following commands.

$ sqlplus /nolog
SQL⇒ connect / as sysdba
Connected.

To enable ARCHIVELOG mode status, enter the following SQL commands:

Lets check the archive log is enable or not.
SQL⇒ archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 29
Next log sequence to archive 31
Current log sequence 31

arhivelog is enabled here. Run the below command.

SQL⇒ Shutdown
or
SQL⇒ shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.

SQL⇒ Startup mount
ORACLE instance started.

Total System Global Area 3390558208 bytes
Fixed Size 2180464 bytes
Variable Size 1996491408 bytes
Database Buffers 1375731712 bytes
Redo Buffers 16154624 bytes
Database mounted.

SQL⇒ Alter database noarchivelog;
Database altered.

SQL⇒ alter database open;

To check the ARCHIVELOG mode status, enter the following SQL command:
SQL⇒ archive log list;

Database log mode No Archive Mode
Automatic archival Disabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 30
Current log sequence 32

Now you can see the archive log is Disabled here.

Note : Flow the Process shown in video.

😉Subscribe and like for more videos:
💛Don't forget to, 💘Follow, 💝Like, 💖Share 💙&, Comment

Tutorial Link :

Thanks & Regards,
Chitt Ranjan Mahto "Chirag"
_________________________________________________________________________________________
Note: All scripts used in this demo will be avilable in our website.
Link will be available in description.

#oracle
#oracletutorial
#chiragstutorial
#chiragsdatabasetutorial
#oracledatabase
#chiragsdbatutorial
#databasetutorial
#bestDatabaseTutorial
#oracletutorialchirags