The Oracle tutorial you are looking at is: Oracle7. X Rollback table space data file deletion processing method. ----One, Introduction:
----Rollback segment is part of a database that records information about changes to the database. Use this information to implement the read consistency of the database and its recovery. If the rollback segment fails, the database does not start normally, causing the database to be paralyzed and the user cannot read or write data. If you can troubleshoot the rollback segment, the user's actual data will not be affected. The author recently encountered a problem in the actual work: the user will rollback segment table space (RBS) of the database file (rbs01.dbf) error deleted, so that the database can not run correctly, the following I exclude the method of processing steps.
----Two, steps:
----1, first change the parameter file Init.ora, so that the database can mount up.
----There is a system rollback segment in the system tablespace, which is necessary for the database to be set up when the database is first established, and automatically online as the database is opened. The rollback segment that we usually use is a public rollback segment, not a system rollback segment, and if the common rollback segment fails, we can temporarily replace the system rollback segment to enable the database to mount.
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 then open it
----from the control file of the database, rbs01.dbf the data file for the rollback segment table space RBS offline and removed.
SVRMGRL >alter Database DataFile
' ##/##/rbs01.dbf ' offline drop;
----Restore the database.
SVRMGRL >recover database using Backup controlfile;
----may appear on the screen at this point:
ora_00280 Change # for thread# are in sequence#
Specify log:[< RET > for suggested| Auto|from
Logsource|cancel]
----You can find the online log file you need based on the sequence# number, and enter the log file (including the full path) to use SVRMGRL >select * from V$log when looking for an online log file; The database restore is complete at this time. Open the database again.
SVRMGRL >alter database open resetlogs;
----3, rebuild the new rollback segment
----Delete the old rollback segment and rollback table space.
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;
----Rebuild the new rollback 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, start the database with the new rollback segment
SVRMGRL >shutdown Abort
$ VI $ORACLE _home/dbs/init< SID >.ora
Rollback_segments= (R01,R02,R03,R04)
Remove the parameter _corrupted_rollback_segment
SVRMGRL >startup Normal
----Three, concluding remarks:
----The troubleshooting of this problem is that the database was implemented on an archived basis, and the author has successfully passed on HP-UX 10.20 and Solaris2.5 two system platforms.
.