1. Close the data file of the corresponding undo tablespace.
Alter database datafile '/home/Oracle/undofile. dbf' offline drop
2. query the segment status
SQL> select segment_name, tablespace_name, status from dba_rollback_segs; segment_name tablespace_name status =------------------------------ ---------------- _ blank $ undo_small =$ undo_small needs =$ undo_tpfda offline
3. Use the pfile parameter file to start the database
Shut down the database: shutdown immediate
Create a pfile: Create pfile '/home/Oracle/pfile. ora' from spfile
Modify the pfile file and add the following parameters:
*. Undo_management = 'manual'
_ Uploupted_rollback_segments ('_ syssmu11_4270384673 $ ')
Start Database: startup pfile = '/home/Oracle/pfile. ora'
4. Delete the segment in the needs recovery status.
Drop rollback segment '_ syssmu11_4270384673 $'
5. Restart the database and delete the Undo tablespace.
Drop tablespace undo_small
Oracle regards the data to be rolled back as submitted data. To avoid unpredictable problems, after removing hidden parameters from the database, export the data and create a new database, import the source data.
For databases that have not been started, you can use the Linux operating system command strings to obtain rollback segment information from the data files in the system tablespace. For oracle in Windows, you can copy the data file to the Linux system through FTP, and then execute the strings command: strings system01.dbf | grep _ syssmu
Definition: in order to better enable readers to understand the theme-related content, special reference http://www.askmaclean.com/archives/ora-00600-4000-ora-00704-bootstrap-process-failure.html
_ Offline_rollback_segments and _ segment upted_rollback_segments both cause instance behavior changes: