Solution to accidental deletion of Oracle Database Files

We all know that the rollback segment is a part of the database, and its main function is to record the change information of the Oracle database. This information enables read consistency and restoration of Oracle databases. If the rollback segment fails, the database cannot be started normally, resulting in database paralysis and the user cannot read or write data.

If the rollback segment can be eliminated, the actual data of the user will not be affected. I recently encountered a problem in my practical work:

The user deletes the Oracle database file (rbs01.dbf) of the tablespace (rbs) in the rollback segment by mistake, so that the database cannot run properly. Next I will exclude the processing steps of this method.

Steps:

1. First, modify the parameter file init. ora so that the Oracle database can be mounted.

There is a system rollback segment in the system tablespace, which is required by the database on the rollback segment. When the database is created for the first time, it is created accordingly, and automatically online as the database is opened. We usually use a public rollback segment instead of a system rollback segment. If a public rollback segment fails, we can replace the system rollback segment temporarily, enables the Oracle database to be mounted.

 
 

  
  
svrmgrl >Shutdown abort   
  
  
$ vi $ORACLE_HOME/dbs/init< sid >.ora   
  
  
rollback_segments=(system)   
  
  
_corrupted_rollback_segments=(r01,r02,r03,r04)   
  
  
svrmgrl >Startup mount  
 
 

2. Restore the database and open it again.

Remove the rbs data file rbs01.dbf In the rollback segment from the control file of the Oracle database.

 
 

  
  
svrmgrl >alter database datafile   
  
  
‘##/##/rbs01.dbf’ offline drop;  
 
 

Restore the database.

 
 

  
  
svrmgrl >recover database using backup controlfile;  
 
 

At this time, the screen may appear:

 
 

  
  
ORA_00280 Change #### for thread# is in sequence#   
  
  
specify log:[< RET > for suggested|AUTO|from   
  
  
logsource|cancel] 
 
 

You can find the online log file you need based on the sequence # And enter the log file (including the full path ), when searching online log files, you can use svrmgrl> select * from v $ log. At this time, the Oracle database is restored. Then open the database.

 
 

  
  
svrmgrl >alter database open resetlogs;  
 
 

3. recreate a rollback segment

Delete the old rollback segment and the rollback tablespace.

 
 

  
  
svrmgrl >alter rollback_segment r01 offline drop;   
  
  
svrmgrl >alter rollback_segment r02 offline drop;   
  
  
svrmgrl >alter rollback_segment r03 offline drop;   
  
  
svrmgrl >alter rollback_segment r04 offline drop;   
  
  
svrmgrl >drop tablespace rbs including contents;  
 
 

Create a new table space and rollback segment.

 
 

  
  
svrmgrl >connect internal   
  
  
svrmgrl >create rollback segment ro tablespace system;   
  
  
svrmgrl >alter rollback segment ro online;   
  
  
svrmgrl >create tablespace rbs datafile   
  
  
‘##/##/rbs01.dbf’ size ##k;   
  
  
svrmgrl >create rollback segment r01 tablespace rbs;   
  
  
svrmgrl >create rollback segment r02 tablespace rbs;   
  
  
svrmgrl >create rollback segment r03 tablespace rbs;   
  
  
svrmgrl >create rollback segment r04 tablespace rbs;   
  
  
svrmgrl >alter rollback segment r01 online;   
  
  
svrmgrl >alter rollback segment r02 online;   
  
  
svrmgrl >alter rollback segment r03 online;   
  
  
svrmgrl >alter rollback segment r04 online;  
 
 

4. Use the new rollback segment to start the database

 
 

  
  
Svrmgrl> Shutdown abort
  
  
$ Vi $ ORACLE_HOME/dbs/init <sid>. ora
  
  
Rollback_segments = (r01, r02, r03, r04)
  
  
Remove the parameter _ uploupted_rollback_segment.
  
  
Svrmgrl> Startup normal
 
 

Conclusion:

The Troubleshooting of this fault is performed by Oracle Database in archive mode, which has been successfully passed through on HP-UX 10.20 and Solaris2.5.

Article by: http://www.programbbs.com/doc/class10-3.htm