ORA-01548: Active rollback segment XX found, terminate dropping tablespace

Note: [Oracle problem set] refers to the problems and solutions encountered by bloggers during database operations.

Statement execution: indicates the database operation process. Error: Indicates An error occurred while operating the database. Error cause: indicates the cause of the error. Solution: indicates the solution to the error. Related Knowledge: indicates the knowledge related to this topic. ========================================================== ==================================Execution statement: an error is reported when the tablespace name is dropped. The following error occurs:

"ORA-01548: Active rollback segment '_ syssmu11_4270384673 $' found, terminate dropping tablespace"

Error cause: to delete the segments in the Undo tablespace, you must reply to the solution: delete rollback segment information.

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
Content. Thanks to Maclean! _ Extends upted_rollback_segments (extends upted undo segment List) to hide functions unique to parameters:

• When the instance starts startup and opens the database, the Undo segments listed by _ cancupted_rollback_segments (UNDO segment/rollback segment) will not be accessed and read.
• All transactions that point to the Undo segments listed by _ javasupted_rollback_segments are considered to have committed commit, which is similar to the Undo segments that have been dropped.
  • This will cause serious logical errors.
  • If there are active transactions in the data dictionary, it will be even worse. The logical misoperation of the data dictionary will cause database management problems.
  • If the bootstrap Bootstrap core object has active transactions, the error ORA-00704: bootstrap process failure error cannot be ignored, resulting in the failure to forcibly open the database
• We strongly recommend that you use the _ javasupted_rollback_segments parameter to open the database, export data, and recreate the database. This parameter may be stubborn.
• Oracle has a tool called txchecker to check for problematic transactions.

_ Offline_rollback_segments and _ segment upted_rollback_segments both cause instance behavior changes:

• Undo segments (UNDO segment/rollback segment) listed in the preceding two parameters will not be used online
• The undo $ data dictionary base table contains offline records.
• New transactions will not be allocated and used in the life cycle of the instance.
• The active transaction on the Undo segments list listed by the parameter will be neither rolled back nor marked as dead so that SMON can be rolled back (understand the SMON function you do not know (5): recover dead transaction)