Set the Oracle database to non-Archive

In archive log mode, there may be an annoying ORA-00257 error when the size of the archive log exceeds the maximum, as we have discussed how to increase the archive log space. However

In archive log mode, there may be an annoying ORA-00257 error when the size of the archive log exceeds the maximum, as we have discussed how to increase the archive log space. However

In archive log mode, there may be an annoying ORA-00257 error when the size of the archive log exceeds the maximum, as I mentioned above how to increase the archive log space. In a common development environment, there is no need to archive logs. At this time, we disable the archive logs of the database, that is, to change the database to the non-archive log mode, what should I do.

All operations here must be performed on the database's machine. Log On with the SYS user and set the archive process to close.

Alter system set log_archive_start = false scope = spfile;

Close the database.

Shutdown immediate

Then, start the database to the mount mode.

Startup mount

Close the flash back database mode, if not closed, there will be a nasty ORA-38774 error when you close archiving logs later.

Alter database flashback off

Change the database to non-archive mode.

Alter database noarchivelog;

After modification, open the database

Alter database open;

Check the space of archived logs.

Select * from v $ recovery_file_dest;

Next, let's take a look at the log status.

Select * from v $ log;

Check the usage of the flash back log.

Select * from v $ flash_recovery_area_usage;