While Solving ORA-00600 [4194]/[4193] Errors [ID 281429.1]
In this Document
Applies to:
Oracle Server - Enterprise Edition - Version 7.0.16.0 and laterInformation in this document applies to any platform.
***Checked for relevance on 03-Oct-2011***
Oracle Server Enterprise Edition
Goal
This note will give an Brief overview of the steps to resolve ORA-600 [4194]/[4193]:-
Fix
Short Description of ORA-00600[4194]
---------------------------------------
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
Refer to Note:39283.1 for more details on the description of this error.
Basic Steps that Need to be Followed to Solve an ORA-00600[4194] Error
There are two Options to resolve this issue.
Options along with their solutions are given below.
Option 1:- Support Method(Drop the undo tablespace).
Option 1 :- Supported Method
======================
Drop the undo tablespace.
Single instance
This error normally happens for a new transaction. The trace file actually shows an active transaction for the undo segment because this is the transaction created by the same process.If the undo segment happens to have an active transaction , then Oracle
may recover it later with no problems .
Normally if the header is dumped after the error, the active transactin is gone.
So a Simpler option to resolve this issue is.
Step 1
--------
SQL> Startup nomount ; --> using spfile
SQL> Create pfile='/tmp/corrupt.ora' from spfile ;
SQL> Shutdown immediate;
Step 2
-------
Modify the corrupt.ora and set Undo_managment=Manual
SQL> Startup mount pfile='/tmp/corrupt.ora'
SQL> Show parameter undo
it should show manual
SQL> Alter database open ;
If it comes up
SQL> Create rollback segment r01 ;
SQL> Alter rollback segment r01 online ;
Create a new undo tablespace
SQL> Create undo tablespace undotbs_new datafile '<>' size <> M ;
Please note :- You can delay the drop of the Old undo tablespace this is just to allow the block cleanout to happen for dead transaction.
So the below step can be issued after database has been up and running with new undo tablespace for couple of hours.
Also note if your database has been forced open(datafiles are not in sync and archivelogs missing ) using any unsupported method then please donot drop the Old undo.
Drop the Old undo tablespace
SQL> Drop tablespace
Step 3
-------
SQL> Shutdown immediate;
SQL> Startup nomount ; ---> Using spfile
SQL>Alter system set undo_tablespace=
SQL> Shutdown immediate ;
SQL> Startup
Check if error is reported
For Rac Instance(If one instance is down and other is up and running)
------------------------
If one node is up and running and other node is failing with ORA-00600[4194]/[4193] then
From the instance which is up and running create a new undo tablespace and make it the default one for the other instance which is down with the error.Startup the failing instance with
the new undo tablespace.
From Instance which is up and running
Create undo tablespace undo_new datafile '
Alter system set undo_tablespace=
Now Startup the Instance which is down
SQL>Startup mount
SQL>Show parameter undo
Should show the new undo tablespace created above
SQL>Alter database open ;
SQL>Drop tablespace
If all the Instance is down in the Rac due to this error then following the instruction given for Single instance and create new undo tablespace.
For 8i database and Below
SQL>Startup restrict
Drop the Manual rollback segments and recreate it
Please note :-
Option 1 would fail if the undo segment involved is System undo .
Please open a Service request with Oracle to diagnose the issue further
if option 1 fails.
References
NOTE:39283.1 - ORA-600 [4194] "Undo Record Number Mismatch While Adding Undo Record"@NOTE:452620.1 - ORA-600 [4193] ORA-600 [4194] IN SYSTEM ROLLBACK SEGMENT. HOW TO PATCH
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/17252115/viewspace-751747/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-00600 [4194]/[4193] Errors Without Using Unsupported parameter-281429.1Error
- Step by step to resolve ORA-600 4194 4193 4197 on database crash [ID 1428786.1]Database
- ORA-00600 [4194], [55]處理
- Oracle recover current redo ORA-00600:[4193] (oracle 故障恢復current redo日誌ORA-00600:[4193]報錯)Oracle
- ORA-00600: internal error code, arguments: [4194]Error
- 【UNDO】Step by step to resolve ORA-600 4194 4193 4197 on database crashDatabase
- ora-00600:internal error code,arguments:[4194],[7],[2],[],[]Error
- oracle斷電重啟之ORA-00600[4194]Oracle
- ORA-00600: internal error code, arguments: [4194], [4], [31]Error
- ORA-00600: internal error code, arguments: [4194], [30], [30], [],Error
- Understanding and Diagnosing ORA-00600 [13011] Errors [ID 1392778.1]Error
- Understanding and Diagnosing ORA-00600 [12333] Errors [ID 389713.1]Error
- UNDO表空間損壞,爆滿,ORA-600[4194]/[4193]錯誤解決
- ORA-00600: internal error code, arguments: [4194] 錯誤處理Error
- 遭遇 ORA-00600: internal error code, arguments: [4194] ORA-1552Error
- ORA-00600 "deadlock detected while waiting for resource"WhileAI
- 簡單記錄一次ORA-00600: internal error code, arguments: [4194]Error
- ORA-27090,ORA-00600: internal error code, arguments: [4194],的解決方法Error
- ORA-00937 Errors While Executing A Query Using Microsoft OLEDB DriversErrorWhileROS
- 記一次無歸檔恢復ORA-00600: internal error code, arguments: [4194]Error
- ORA-27090及ORA-00600: internal error code, arguments: [4194], [18], [4]的解決方法Error
- Linux Load Average: Solving the MysteryLinux
- Solving ODI "Initializing Search Engine" issue
- ASM REACTING TO PARTITION ERRORS [ID 1062954.1]ASMReactError
- Metric Collection ErrorsError
- oracle之errorsOracleError
- oracle 之errorsOracleError
- Understanding and Diagnosing ORA-00600 [12333] / ORA-3137 [12333] ErrorsError
- Java 迴圈 - for, while 及 do…whileJavaWhile
- Database Capture and Replay: Common Errors and Reasons (文件 ID 463263.1)DatabaseAPTError
- Connected to an idle instance – while database is runningWhileDatabase
- while迴圈以及do while迴圈While
- ORA-00600 : internal error code, arguments: [qertbFetchByRowID]Error
- Go Errors 詳解GoError
- slave-skip-errorsError
- HIbernate errors...Error
- How to Create a BNE Log For Web Adi Issues and Errors? [ID 817023.1]WebError
- DIAGNOSING ORA-3113 ERRORS [ID 1020463.6]Error