Introduction to the location of corrupted redo logs in Oracle databases

The following article describes how to determine the location and status of the damaged redo log of an Oracle database, I hope that you will read the following articles to help you learn about the location and status of damaged redo logs of Oracle databases.

1. If the database is available:

 
 

  
  
select * from v$logfile;  
  
  
svrmgrl>select * from v$log; 
 
 

2. If the Oracle database is terminated abnormally:

 
 

  
  
svrmlgr>startup mount;  
  
  
svrmgrl>select * from v$logfile;  
  
  
svrmgrl>select * from v$log; 
 
 

Among them, the status of logfile is INVALID, indicating that this set of log files are damaged; the status of log is Inactive, indicating that the redo log files are Inactive; the status of Active indicates that the redo log files are Active; current: indicates that the redo log is a log file currently in use.

The corrupted log file is not activated:

1. Delete the corresponding log group:

 
 

  
  
svrmgrl>alter database drop logfile group group_number; 
 
 

2. Recreate the corresponding log group:

 
 

  
  
svrmgrl>alter database add log file group group_number 
’log_file_descritpion’，…） size log_file_size; 
 
 

The corrupted log file is active and non-current:

1. Clear the corresponding log group:

 
 

  
  
svrmgrl>alter database clear unarchived logfile group group_number; 
 
 

The corrupted log file is the current active log file. Run the following command to clear the corresponding log group:

 
 

  
  
svrmgrl>alter database clear unarchived logfile group group_number; 
 
 

If clearing fails, incomplete restoration based on time points is allowed. Open the Oracle database and back up the database in an appropriate way:

 
 

  
  
svrmgrl>alter database open; 
 
 

The above content describes the location and status of the redo logs that are damaged to the Oracle database. We hope this will help you in this regard.

Article by: http://www.programbbs.com/doc/3406.htm