重建UNDO表空间遭遇ORA-01548
今天开发那边的一套数据库的undo表空间不知道被谁设置成了自动扩展,然后所谓的屋漏偏逢连夜雨的是,开发人员今天跑了一个很大的
今天开发那边的一套数据库的undo表空间不知道被谁设置成了自动扩展,然后所谓的屋漏偏逢连夜雨的是,开发人员今天跑了一个很大的事物,然后直接后果就是undo表空间不断被扩展,直到把文件系统写爆了。没办法得把undo表空间删了重建以回收空间啊。安装常规的操作:
先新建一个新的undo表空间:
create undo tablespace tmpundo datafile '/soft/Oracle/oradata/sitjf/tmpundo01.dbf'size 1g autoextend off;
把新建的undo表空间设置为默认undo表空间:
alter system set undo_tablespace=tmpundo;
接下来就是删除原有undo表空间undotbs1了,但是我发现我悲剧了,删除报错:
SQL> DROP TABLESPACE UNDOTBS1 INCLUDING CONTENTS AND DATAFILES;
CREATE UNDO TABLESPACE UNDOTBS1 DATAFILE '/soft/oracle/oradata/sitjf/undotbs01.dbf' SIZE 1G AUTOEXTEND OFF;
DROP TABLESPACE UNDOTBS1 INCLUDING CONTENTS AND DATAFILES
*
ERROR at line 1:
ORA-01548: active rollback segment '_SYSSMU1_2181731349$' found, terminate
dropping tablespace
尝试过重启数据库,依然无效,尝试删除数据文件后,依然是报错:
SQL> ALTER DATABASE DATAFILE '/soft/oracle/oradata/sitjf/undotbs01.dbf' OFFLINE DROP;
Database altered.
最后弄的没办法了,还是Google一下吧,于是参照Google上的解决方法顺利的处理了:
1、修改init$ORACLE_SID.ora参数文件,为:
undo_management=manual
undo_retention=10800
undo_tablespace=tmpundo
_CORRUPTED_ROLLBACK_SEGMENTS = (_SYSSMU1$,_SYSSMU2$,_SYSSMU3$,_SYSSMU3$,_SYSSMU4$,_SYSSMU5$,_SYSSMU6$,_SYSSMU7$,_SYSSMU8$,_SYSSMU9$,_SYSSMU10$,_SYSSMU1_2181731349$)
及,把undo修改为手动管理,并把默认undo表空间设置为新建的临时过渡undo表空间tmpundo。
最重要的是_CORRUPTED_ROLLBACK_SEGMENTS参数,改参数Oracle会假设事务已经回滚,而不会进行其他的检查。一般UNDO表空间丢失或损害的时候可以尝试使用这个隐含参数。
然后以init$ORACLE_SID.ora参数文件启动数据库
SQL> startup force pfile='?/dbs/initsitjf.ora'
ORACLE instance started.
Total System Global Area 3423965184 bytes
Fixed Size 2211584 bytes
Variable Size 1761607936 bytes
Database Buffers 1644167168 bytes
Redo Buffers 15978496 bytes
Database mounted.
Database opened.
现在就可以删除undotbs1表空间了
SQL> drop tablespace undotbs1 including contents and datafiles;
Tablespace dropped.
然后重建undotbs1表空间
SQL> create undo tablespace undotBS1 datafile '/soft/oracle/oradata/sitjf/undotbs01.dbf' size 100M ;
Tablespace created.
重新修改undo表空间为自动管理,并且设置默认undo表空间为undotbs1,通过init参数修改。
undo_management=auto
undo_retention=10800
undo_tablespace=undotbs1
重启数据库,现在就可以删除过渡undo表空间tmpundo了:
SQL> drop tablespace tmpundo including contents;
Tablespace dropped.
现在空间已经回收了,undo表空间也被收缩了。
注:
也可以使用drop rollback命令来删除回滚段_SYSSMU1_2181731349$,undo表空间必须为manual管理方式
DROP ROLLBACK SEGMENT "_SYSSMU1_2181731349$";
查看回滚段
SELECT SEGMENT_NAME, OWNER, TABLESPACE_NAME, STATUS FROM DBA_ROLLBACK_SEGS;

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics











The main role of MySQL in web applications is to store and manage data. 1.MySQL efficiently processes user information, product catalogs, transaction records and other data. 2. Through SQL query, developers can extract information from the database to generate dynamic content. 3.MySQL works based on the client-server model to ensure acceptable query speed.

InnoDB uses redologs and undologs to ensure data consistency and reliability. 1.redologs record data page modification to ensure crash recovery and transaction persistence. 2.undologs records the original data value and supports transaction rollback and MVCC.

MySQL is an open source relational database management system, mainly used to store and retrieve data quickly and reliably. Its working principle includes client requests, query resolution, execution of queries and return results. Examples of usage include creating tables, inserting and querying data, and advanced features such as JOIN operations. Common errors involve SQL syntax, data types, and permissions, and optimization suggestions include the use of indexes, optimized queries, and partitioning of tables.

MySQL's position in databases and programming is very important. It is an open source relational database management system that is widely used in various application scenarios. 1) MySQL provides efficient data storage, organization and retrieval functions, supporting Web, mobile and enterprise-level systems. 2) It uses a client-server architecture, supports multiple storage engines and index optimization. 3) Basic usages include creating tables and inserting data, and advanced usages involve multi-table JOINs and complex queries. 4) Frequently asked questions such as SQL syntax errors and performance issues can be debugged through the EXPLAIN command and slow query log. 5) Performance optimization methods include rational use of indexes, optimized query and use of caches. Best practices include using transactions and PreparedStatemen

MySQL is chosen for its performance, reliability, ease of use, and community support. 1.MySQL provides efficient data storage and retrieval functions, supporting multiple data types and advanced query operations. 2. Adopt client-server architecture and multiple storage engines to support transaction and query optimization. 3. Easy to use, supports a variety of operating systems and programming languages. 4. Have strong community support and provide rich resources and solutions.

Compared with other programming languages, MySQL is mainly used to store and manage data, while other languages such as Python, Java, and C are used for logical processing and application development. MySQL is known for its high performance, scalability and cross-platform support, suitable for data management needs, while other languages have advantages in their respective fields such as data analytics, enterprise applications, and system programming.

MySQL is suitable for small and large enterprises. 1) Small businesses can use MySQL for basic data management, such as storing customer information. 2) Large enterprises can use MySQL to process massive data and complex business logic to optimize query performance and transaction processing.

MySQL index cardinality has a significant impact on query performance: 1. High cardinality index can more effectively narrow the data range and improve query efficiency; 2. Low cardinality index may lead to full table scanning and reduce query performance; 3. In joint index, high cardinality sequences should be placed in front to optimize query.
