Oracle Database User-managed backup and recovery-recovery redo log

 

The restoration process of redo logs in Oracle databases based on user-managed backup and recovery is described in detail.

A log member in the log group is damaged as follows:

 

You have selected 6 rows.

-- Use 360 to forcibly Delete the REDO01_ADD.LOG file to simulate log member corruption.

-- Switch logs multiple times to make the deleted redo file invalid.

SQL> alter system switch logfile;

The system has been changed.

SQL> alter system switch logfile;

The system has been changed.

 

You have selected 6 rows.

-- If the member is a member of the current log group, the member cannot be deleted. In this case, you must switch the log to delete the member.

 

Row 3 has an error:

ORA-01609: Log 1 is the current log of thread 1-member cannot be deleted

ORA-00312: Online log 1 thread 1: 'f: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ ORCL \ redo01.log'

ORA-00312: Online log 1 thread 1: 'f: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ ORCL \ REDO01_ADD.LOG'

SQL> alter system switch logfile;

The system has been changed.

 

The database has been changed.

-- Add a member of the log Group

SQL> alter database add logfile member 'f: \ ORACLE \ PRODUCT \ 10.2.0 \ ORADATA \ ORCL \ REDO01_ADD_NEW.LOG 'to group 1;

The database has been changed.

 

You have selected 6 rows.

Note that the status of the new log group member is also invalid.

Here we will introduce the restoration of Oracle Database redo logs based on user-managed backup and recovery. We hope this introduction will bring you some gains!