ORA-00600: internal error code, arguments: [4194]

lhrbest發表於2017-09-11



4193:表示undo和redo不一致(Arg [a] Undo record seq number,Arg [b] Redo record seq number );
4194:表示也是undo和redo不一致(Arg [a] Maximum Undo record number in Undo block,Arg [b] Undo record number from Redo block)

故障解決:


1、修改引數
undo_management= MANUAL
undo_tablespace= SYSTEM
2、OPEN資料庫,刪除當前undo空間,重建新的undo空間
3、修改引數
undo_management= AUTO
undo_tablespace= UNDOTBS1
4、重新啟動資料庫





ORA-00600: internal error code, arguments: [4194]

2016-11-21 14:51 by 瀟湘隱者, 555 閱讀, 0 評論, 收藏編輯

使用PlateSpin複製出來的一資料庫伺服器(Oracle 10g)在啟動資料庫例項時遇到“ORA-00600: internal error code, arguments: [4194].....”錯誤,例項在啟動後,會自然Down掉。具體情況如下所示:

Successfully onlined Undo Tablespace 54.
Mon Nov 21 11:34:03 2016
SMON: enabling tx recovery
Mon Nov 21 11:34:03 2016
Errors in file /u01/app/oracle/admin/epps/bdump/epps_smon_7522.trc:
ORA-00600: internal error code, arguments: [4097], [], [], [], [], [], [], []
Mon Nov 21 11:34:03 2016
Database Characterset is UTF8
Mon Nov 21 11:34:03 2016
Errors in file /u01/app/oracle/admin/epps/udump/epps_ora_7548.trc:
ORA-00600: internal error code, arguments: [4194], [59], [40], [], [], [], [], []
Mon Nov 21 11:34:04 2016
Non-fatal internal error happenned while SMON was doing temporary segment drop.
SMON encountered 1 out of maximum 100 non-fatal internal errors.
Mon Nov 21 11:34:04 2016
Errors in file /u01/app/oracle/admin/epps/bdump/epps_smon_7522.trc:
ORA-00600: internal error code, arguments: [4097], [], [], [], [], [], [], []
 
................................................................................
................................................................................
 
ORA-00600: internal error code, arguments: [4194], [52], [29], [], [], [], [], []
ORA-00600: internal error code, arguments: [4194]Non-fatal internal error happenned while SMON was doing temporary segment drop.
Mon Nov 21 11:35:04 2016
Flush retried for xcb 0x4419143b0, pmd 0x4401e3c90
Mon Nov 21 11:35:04 2016
SMON encountered 6 out of maximum 100 non-fatal internal errors.
Mon Nov 21 11:35:04 2016
Doing block recovery for file 2 block 1007
No block recovery was needed
Mon Nov 21 11:35:05 2016
Errors in file /u01/app/oracle/admin/epps/bdump/epps_pmon_7510.trc:
ORA-00600: internal error code, arguments: [4194], [52], [29], [], [], [], [], []
Mon Nov 21 11:35:05 2016
Errors in file /u01/app/oracle/admin/epps/bdump/epps_pmon_7510.trc:
ORA-00600: internal error code, arguments: [4194], [52], [29], [], [], [], [], []
PMON: terminating instance due to error 472
Instance terminated by PMON, pid = 7510

clip_image001

 

這個錯誤,官方文件Step by step to resolve ORA-600 4194 4193 4197 on database crash (文件 ID 1428786.1)有提供詳細的介紹。建議處理前,建議先查閱次文件,錯誤出現的主要場景:

This issue generally occurs when there is a power outage or hardware failure that initially crashes the database. On startup, the database does the normal roll forward (redo) and then rollback (undo), this is where the error is generated on the rollback.

 

具體操作如下所示

 

Step 1: 透過spfile建立生成pfile

 

SQL> create pfile from spfile;

File created.

 

Step 2: 關閉資料庫例項

 

Step 3:修改pfile中undo_management為MANUAL

[oracle@DB-Server dbs]$ grep undo initepps.ora
 
*.undo_management='AUTO'
 
*.undo_tablespace='UNDOTBS'
 
[oracle@DB-Server dbs]$ vi initepps.ora

 

Step 4: 使用PFILE啟動資料庫

[oracle@DB-Server dbs]$ sqlplus / as sysdba
 
SQL*Plus: Release 10.2.0.4.0 - Production on Mon Nov 21 11:51:59 2016
 
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
 
Connected to an idle instance.
 
SQL> startup restrict pfile='initepps.ora'
 
ORACLE instance started.
 
Total System Global Area 1.0737E+10 bytes
 
Fixed Size 2101808 bytes
 
Variable Size 6476008912 bytes
 
Database Buffers 4244635648 bytes
 
Redo Buffers 14671872 bytes
 
Database mounted.
 
Database opened.

 

Step 5: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

 
SQL> select tablespace_name, status, segment_name from dba_rollback_segs where status != 'OFFLINE';
 
TABLESPACE_NAME                STATUS           SEGMENT_NAME
------------------------------ ---------------- ------------------------------
SYSTEM                         ONLINE           SYSTEM

 

Step 6: 新建一個UNDO表空間

SQL> create undo tablespace UNDOTBS1
  2  datafile '/u04/epps/oradata/undotbs_01.dbf'
  3  size 4G;
 
Tablespace created.

 

Step 7: 刪除舊的UNDO表空間

 

SQL> drop tablespace UNDOTBS including contents and datafiles;
 
Tablespace dropped.

 

Step 8:關閉資料庫例項


SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle Database 10g Release 10.2.0.4.0 - 64bit Production

 

Step 9:啟動資料庫例項到NOMOUNT狀態

 

SQL> startup nomount;
ORACLE instance started.
 
Total System Global Area 1.6777E+10 bytes
Fixed Size                  2113368 bytes
Variable Size            9982443688 bytes
Database Buffers         6777995264 bytes
Redo Buffers               14663680 bytes


 

Step 10:修改spfile中的undo_tablespace引數

SQL> alter system set undo_tablespace='UNDOTBS1' scope=spfile;
 
System altered.

 

Setp 11:關閉資料庫例項。

 

Step 12:啟動資料庫例項(使用spfile)

SQL> startup;
ORACLE instance started.
 
Total System Global Area 1.6777E+10 bytes
Fixed Size                  2113368 bytes
Variable Size            9982443688 bytes
Database Buffers         6777995264 bytes
Redo Buffers               14663680 bytes
Database mounted.
Database opened.






Step by step to resolve ORA-600 4194 4193 4197 on database crash (文件 ID 1428786.1)


In this Document

Symptoms
Changes
Cause
Solution


APPLIES TO:

Oracle Database - Enterprise Edition - Version 9.2.0.1 to 11.2.0.3 [Release 9.2 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 04-Dec-2013***

SYMPTOMS

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.

CHANGES

This issue generally occurs when there is a power outage or hardware failure that initially crashes the database. On startup, the database does the normal roll forward (redo) and then rollback (undo), this is where the error is generated on the rollback.

CAUSE

This also can be cause by the following defect

Bug 8240762 Abstract: Undo corruptions with ORA-600 [4193]/ORA-600 [4194] or ORA-600 [4137] after SHRINK

Details: 
Undo corruption may be caused after a shrink and the same undo block may be used 
for two different transactions causing several internal errors like:
ORA-600 [4193] / ORA-600 [4194] for new transactions
ORA-600 [4137] for a transaction rollback

SOLUTION

Best practice to create a new undo tablespace.
This method includes segment check.

Create pfile from spfile to edit
>create pfile from spfile;

1. Shutdown the instance

2. set the following parameters in the pfile
    undo_management = manual
    event = '10513 trace name context forever, level 2'

3. >startup restrict pfile=

4. >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

5. Create new undo tablespace - example
>create undo tablespace datafile size 2000M;

6. Drop old undo tablespace
>drop tablespace including contents and datafiles;

7. >shutdown immediate;

8 >startup nomount;  --> Using your Original spfile

9 modify the spfile with the new undo tablespace name

  Alter system set undo_tablespace = '' scope=spfile;

10. >shutdown immediate;

11. >startup;  --> Using spfile
 
The reason we create a new undo tablespace first is to use new undo segment numbers that are higher then the current segments being used.  This way when a transaction goes to do block clean-out the reference to that undo segment does not exist and continues with the block clean-out.


Step by step to resolve ORA-600 4194 4193 4197 on database crash (文件 ID 1428786.1)





About Me

.............................................................................................................................................

● 本文作者:小麥苗,部分內容整理自網路,若有侵權請聯絡小麥苗刪除

● 本文在itpub(http://blog.itpub.net/26736162/abstract/1/)、部落格園(http://www.cnblogs.com/lhrbest)和個人微信公眾號(xiaomaimiaolhr)上有同步更新

● 本文itpub地址:http://blog.itpub.net/26736162/abstract/1/

● 本文部落格園地址:http://www.cnblogs.com/lhrbest

● 本文pdf版、個人簡介及小麥苗雲盤地址:http://blog.itpub.net/26736162/viewspace-1624453/

● 資料庫筆試面試題庫及解答:http://blog.itpub.net/26736162/viewspace-2134706/

● DBA寶典今日頭條號地址:

.............................................................................................................................................

● QQ群號:230161599(滿)、618766405

● 微信群:可加我微信,我拉大家進群,非誠勿擾

● 聯絡我請加QQ好友646634621,註明新增緣由

● 於 2017-09-01 09:00 ~ 2017-09-30 22:00 在魔都完成

● 文章內容來源於小麥苗的學習筆記,部分整理自網路,若有侵權或不當之處還請諒解

● 版權所有,歡迎分享本文,轉載請保留出處

.............................................................................................................................................

小麥苗的微店

小麥苗出版的資料庫類叢書http://blog.itpub.net/26736162/viewspace-2142121/

.............................................................................................................................................

使用微信客戶端掃描下面的二維碼來關注小麥苗的微信公眾號(xiaomaimiaolhr)及QQ群(DBA寶典),學習最實用的資料庫技術。

   小麥苗的微信公眾號      小麥苗的DBA寶典QQ群1     小麥苗的DBA寶典QQ群2        小麥苗的微店

.............................................................................................................................................

ORA-00600: internal error code, arguments: [4194]
DBA筆試面試講解群1
DBA筆試面試講解群2
歡迎與我聯絡



來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26736162/viewspace-2144770/,如需轉載,請註明出處,否則將追究法律責任。

相關文章