ORA-01548: active rollback segment XX found, terminate dropp

ORA-01548: active rollback segment XX found, terminate dropping tablespace execution statement: drop tablespace name error: "ORA-01548: active rollback segment '_ SYSSMU11_4270384673 $ 'found, terminate dropping tablespace error cause: to delete the segments in the undo tablespace, You need to reply to the solution: delete rollback segment information 1. Close the data file alter database datafile '/home/oracle/undofile for the corresponding undo tablespace. dbf 'offline drop2, query the segment status SQL> select segment_name, tablespace_name, status f Rom closed; SEGMENT_NAME TABLESPACE_NAME STATUS ready ---------------- _ blank $ UNDO_SMALL closed $ UNDO_SMALL NEEDS closed $ UNDO_TPFDA OFFLINE 3. Use the pfile parameter file to start the database and shut down the database: shutdown immediate: create pfile '/home/oracle/pfile. ora 'from spfile modify the pfile file and add the following parameter *. undo_manageme Nt = 'manual' _ corrupted_rollback_segments ('_ SYSSMU11_4270384673 $') Start the database: startup pfile = '/home/oracle/pfile. ora '4. Delete the segment drop rollback segment in the needs Recovery '_ SYSSMU11_4270384673 $' 5. Restart the database and delete the undo tablespace drop tablespace UNDO_SMALL Oracle to treat the data to be rolled back as submitted data, to avoid unpredictable problems, after removing the hidden parameters from the database, export the data, create a new database, and 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 _ javasupted_rollback_segments (upted undo segment list) hide the unique function of parameters: undo segments (undo segment/rollback segment) listed in the stage _ cancupted_rollback_segments when the instance starts startup and opens the database) all transactions pointing to these undo segments listed by _ uploupted_rollback_segments will not be accessed and will be considered as committed, this is similar to the undo segments that have been dropped. This will lead to serious logical errors. If there are active transactions in the data dictionary, it will be worse, logical rollback of the data dictionary causes database management problems if the bootstrap custom core object has active transactions, the error ORA-00704: bootstrap process failure error cannot be ignored, as a result, you cannot forcibly open the database. We sincerely recommend that you use the _ uploupted_rollback_segments parameter to open the database, export data, and recreate the database, the sequelae of using this parameter may be stubborn. Oracle has a tool called TXChecker which can check the instance behavior changes caused by transaction _ offline_rollback_segments and _ javasupted_rollback_segments: undo Segments listed in the preceding two parameters (Undo segment/rollback segment) online will not be used online. records that will not be shown as OFFLINE in the basic table of the UNDO $ data dictionary will not be allocated to new transactions in the life cycle of the instance. the active transaction 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)