数据库 
首页 > 数据库 > 浏览文章

Oracle创建新undo表空间最佳实践(包含段检查)

(编辑:jimmy 日期: 2025/2/25 浏览:3 次 )

在处理一则ORA-600 [4194]案例时,参考MOS文档:Step by step to resolve ORA-600 4194 4193 4197 on database crash (文档 ID 1428786.1)

1.对于ORA 600[4194]的解释

2.创建新undo表空间最佳实践(包含段检查)

1.对于ORA 600[4194]的解释:

The following error is occurring in the alert.log right before the database crashes.
ORA-00600: internal error code, arguments: [4194], [#], [#], [], [], [], [], []
This error indicates that a mismatch has been detected between redo records and rollback (undo) records.
ARGUMENTS:
Arg [a] - Maximum Undo record number in Undo block
Arg [b] - Undo record number from Redo block
Since we are adding a new undo record to our undo block, we would expect that the new record number is equal to the maximum record number in the undo block plus one. Before Oracle can add a new undo record to the undo block it validates that this is correct. If this validation fails, then an ORA-600 [4194] will be triggered.

可以看到,此错误是因为redo和undo的记录不匹配。常见于异常断电等场景。

2.创建新undo表空间最佳实践(包含段检查)

Best practice to create a new undo tablespace.
his method includes segment check.
 Create pfile from spfile to edit
SQL> Create pfile='/tmp/initsid.ora' from spfile;
 Shutdown the instance
 set the following parameters in the pfile /tmp/initsid.ora
 undo_management = manual
 event = '10513 trace name context forever, level 2'
 SQLstartup restrict pfile='/tmp/initsid.ora'
 SQL>select tablespace_name, status, segment_name from dba_rollback_segs where status != 'OFFLINE';
This is critical - we are looking for all undo segments to be offline - System will always be online.
If any are 'PARTLY AVAILABLE' or 'NEEDS RECOVERY' - Please open an issue with Oracle Support or update the current SR. There are many options from this moment and Oracle Support Analyst can offer different solutions for the bad undo segments.
If all offline then continue to the next step
 Create new undo tablespace - example
SQL>create undo tablespace <new undo tablespace> datafile <datafile> size 2000M;
 Drop old undo tablespace
SQL>drop tablespace <old undo tablespace> including contents and datafiles;
 SQL>shutdown immediate;
SQL>startup nomount; --> Using your Original spfile
. Modify the spfile with the new undo tablespace name
SQL> Alter system set undo_tablespace = '<new tablespace created in step 6>' scope=spfile;
. SQL>shutdown immediate;
. SQL>startup; --> Using spfile

总结

以上所述是小编给大家介绍的Oracle创建新undo表空间最佳实践(包含段检查),希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对网站的支持!
如果你觉得本文对你有帮助,欢迎转载,烦请注明出处,谢谢!

上一篇:Oracle备库宕机启动的完美解决方案
下一篇:Linux虚拟机下安装Oracle 11G教程图文解说
一句话新闻
一文看懂荣耀MagicBook Pro 16
荣耀猎人回归!七大亮点看懂不只是轻薄本,更是游戏本的MagicBook Pro 16.
人们对于笔记本电脑有一个固有印象:要么轻薄但性能一般,要么性能强劲但笨重臃肿。然而,今年荣耀新推出的MagicBook Pro 16刷新了人们的认知——发布会上,荣耀宣布猎人游戏本正式回归,称其继承了荣耀 HUNTER 基因,并自信地为其打出“轻薄本,更是游戏本”的口号。
众所周知,寻求轻薄本的用户普遍更看重便携性、外观造型、静谧性和打字办公等用机体验,而寻求游戏本的用户则普遍更看重硬件配置、性能释放等硬核指标。把两个看似难以相干的产品融合到一起,我们不禁对它产生了强烈的好奇:作为代表荣耀猎人游戏本的跨界新物种,它究竟做了哪些平衡以兼顾不同人群的各类需求呢?