Oracle中出现ORA

共计 8467 个字符，预计需要花费 22 分钟才能阅读完成。

这篇文章将为大家详细讲解有关 Oracle 中出现 ORA-00600 内部错误代码怎么办，丸趣 TV 小编觉得挺实用的，因此分享给大家做个参考，希望大家阅读完这篇文章后可以有所收获。

ORA-00600: 内部错误代码, 参数: [4194] 或 [4193]


数据库版本：Oracle
11.2.0.1.0

数据库服务器操作系统：Windows
server 2008

问题现象：alter
database open resetlogs; 时报错如下

ORA-1092 signalled during: ALTER DATABASE OPEN…

Doing block recovery for file 3 block 261754

No block recovery was needed

Errors in file e:\app\administrator\diag\rdbms\klnew\klnew\trace\klnew_ora_2072.trc 
(incident=92624):

ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [],
[], [], [], [], [], [], []

ORA-01092: ORACLE 实例终止。强制断开连接

ORA-00600: 内部错误代码, 参数: [4194], [], [], [], [], [], [], [], [], [],
[], []

Incident details in:
e:\app\administrator\diag\rdbms\klnew\klnew\incident\incdir_92624\klnew_ora_2072_i92624.trc

Doing block recovery for file 3 block 261754

No block recovery was needed

No Resource Manager plan active

Errors in file
e:\app\administrator\diag\rdbms\klnew\klnew\trace\klnew_smon_3776.trc  (incident=87732):

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

Incident details in: e:\app\administrator\diag\rdbms\klnew\klnew\incident\incdir_87732\klnew_smon_3776_i87732.trc

Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x66288933]
[PC:0x9237D88, kgegpa()+38]

Dump file e:\app\administrator\diag\rdbms\klnew\klnew\trace\alert_klnew.log

解决方案：

1. 数据库开启的情况下，重建 undotbs，然后重新指定到新 undotbs 上。
2. 未打开情况下，修改 undo_management  参数为 manual 或者（也有说并且的）提供新的回滚段。

其中:

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）


其中 MOS 中查询有关 ORA-00600[4194] 问题相关信息；

 

转到底部

修改时间:
2015-11-20
类型:
REFERENCE




Note: For additional ORA-600 related
 information please read Note:146580.1

 

PURPOSE: 

 
 This article discusses the internal error ORA-600 [4194] ,
 what

 
 it means and possible actions. The information here is only applicable

 
 to the versions listed and is provided only for guidance.

 

ERROR: 

 

 Format: ORA-600 [4194] [a]
 [b]

 

VERSIONS: 

 
 versions 6.0 to 12.1

 

DESCRIPTION:

 

  A
 mismatch has been detected between Redo records and rollback (Undo)

 
 records.

 

  We
 are validating the Undo record number relating to the change being

 
 applied against the maximum undo record number recorded in the undo
 block.

 

 
 This error is reported when the validation fails.

 

ARGUMENTS:

  Arg
 [a] Maximum Undo record number in Undo block

  Arg
 [b] Undo record number from Redo block

 

FUNCTIONALITY: 

 
 Kernel Transaction Undo called from Cache layer

 

IMPACT: 

 
 PROCESS FAILURE

 
 POSSIBLE ROLLBACK SEGMENT CORRUPTION

 

SUGGESTIONS:

 

 
 This error may indicate a rollback segment corruption.

 

 
 This may require a recovery from a database backup depending on

  the
 situation.

 

  If
 the Known Issues section below does not help in terms of identifying

  a
 solution, please submit the trace files and alert.log to Oracle

 
 Support Services for further analysis.

 

 

 

 
 Known Issues:

 

 

You can restrict the list below to issues likely to affect one of the
 following versions by clicking the relevant button: 
 

The list below is restricted to show
 only bugs believed to affect version 11.2.0.1.
Other bugs may affect this version but have not been confirmed as being
 relevant yet.

There is 1 bug listed.

NB
Prob
Bug
Fixed
Description
12821418
11.2.0.3.8, 11.2.0.3.BP18, 11.2.0.4, 12.1.0.1
Direct NFS appears to be sending zero length
   windows to storage device. It may also cause Lost Writes

·  *  indicates
 that an alert exists for that issue.

·  +  indicates
 a particularly notable issue / bug.

·  See Note:1944526.1 for details of other symbols used

 

 

 

 

REFERENCES

BUG:792610 – ROLLBACK SEGMENT CORRUPTION, WHEN RETRY
 MULTI-ROW INSERT AFTER AN INTERNAL ERROR
NOTE:146580.1 –
 What is an ORA-600 Internal Error?
NOTE:281429.1 –
 Basic Steps to be Followed While Solving ORA-00600 [4194]/[4193] Errors
 Without Using Unsupported parameter
NOTE:3210520.8 –
 Bug 3210520 – OERI[kjccqmg:esm] / OERI[4194] / corruption possible in RAC

NOTE:69863.1 –
 ALERT: Apparent data corruptions involving Solaris 2.6, ISM DR on
 Starfire
NOTE:792610.8 –
 Bug 792610 – Rollback segment corruption OERI:4194 can occur if block
 checking detects a corrupt block
NOTE:8240762.8 –
 Bug 8240762 – Undo corruptions with ORA-600 [4193]/ORA-600 [4194] or ORA-600
 [4137] / SMON may spin to recover transaction



未找到您要查找的产品? 在社区中提问 …

 

相关内容

Bug 12821418 – Direct NFS appears to be sending zero length
 windows to storage device. It may also cause Lost Writes (文档 ID
 12821418.8)

转到底部

修改时间:
2015-11-6
类型:
PATCH

 

Bug 12821418 Direct
 NFS appears to be sending zero length windows to storage device. It may also
 cause Lost Writes

 This
 note gives a brief overview of bug 12821418. 
 The content was last updated on: 28-OCT-2015
 Click here for details of each of the
 sections below.
 There are additional notes on this bug in Note:1589411.1

Affects:
Product (Component)
Oracle Server (Rdbms)
Range of versions believed to be affected
Versions BELOW 12.1
Versions confirmed as being affected
11.2.0.3
11.2.0.2
11.1.0.7
Platforms affected
Generic (all / most platforms affected) Fixed:
The fix for 12821418 is first
   included in
12.1.0.1
        (Base Release)
11.2.0.4
        (Server Patch Set)
11.2.0.3.8
        Database Patch Set Update
11.2.0.3
        Bundle Patch 18 for Exadata Database
11.2.0.3
        Patch 25 on Windows Platforms


Interim patches may be available for earlier versions – click here to
 check.

Symptoms:
Related To:
Corruption
        (Logical)
Hang
        (Involving Shared Resource)
Internal
        Error May Occur (ORA-600)
Wrong
        Results
Error
        May Occur
ORA-8102 / ORA-8103 / ORA-1410 / ORA-752
ORA-600
        [3020]
ORA-600
        [kdsgrp1]
ORA-600
        [25027]
ORA-600
        [qertbFetchByRowID]
ORA-600
        [kcbz_check_objd_typ_3]
ORA-600
        [kclchkblk_3]
ORA-600
        [4137]
ORA-600
        [4193]
ORA-600
        [4194]
ORA-600 [6102]
Direct
        NFS (dNFS) Description

This bug is only
 relevant when using Direct NFS (dNFS)

Direct NFS: channel id 1 path *** to filer *** PING timeout

errors in the database alert log and database hangs.

This may also cause Lost Writes as described in Note:1589411.1

with the following symptoms:

 Wrong results

 ORA-1499 by analyze validate structure cascade

 ORA-8102

 ORA-600 [kdsgrp1]

 ORA-600 [qertbFetchByRowID]

 ORA-600 [25027]

 ORA-600 [kcbz_check_objd_typ_3]

 ORA-8103

 ORA-1410

 ORA-600 [kclchkblk_3]

 ORA-600 [4137]

 ORA-600 [4193]

 ORA-600 [4194]

and during recovery:

 ORA-600 [3020] with or without message KCOX_FUTURE: CHANGE IN FUTURE OF BLOCK

 ORA-00752 (when DB_LOST_WRITE_PROTECT is enabled - 11g)

 ORA-600 [6102]

Rediscovery Notes

 Direct NFS: channel id 1 path *** to filer *** PING timeout

 errors in the database alert log and database hangs.

Workaround

 Disable Direct NFS

Further details on this issue can be found in Note:1589411.1

Please note: The above is a summary description only. Actual symptoms can
   vary. Matching to any symptoms here does not confirm that you are
   encountering this problem. For questions about this bug please consult
   Oracle Support.

References

Bug:12821418 (This link
 will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article

 

ORA-600 [4193] seq# mismatch while
 adding undo record (文档 ID 39282.1)

转到底部

修改时间:
2016-3-29
类型:
REFERENCE

Note: For additional ORA-600 related
 information please read Note:146580.1
 
PURPOSE:   
 
 This article discusses the internal error ORA-600 [4193] ,
 what  
 
 it means and possible actions. The information here is only applicable  
 
 to the versions listed and is provided only for guidance.
 
ERROR:   
 
 Format: ORA-600 [4193] [a]
 [b]
 
VERSIONS:   
 
 versions 6.0 to 12.1
 
DESCRIPTION:   
 
  A
 mismatch has been detected between Redo records and Rollback (Undo)  
 
 records.
 
  We
 are validating the Undo block sequence number in the undo block against  
  the
 Redo block sequence number relating to the change being applied.
 
 
 This error is reported when this validation fails.
 
ARGUMENTS:
  Arg
 [a] Undo record seq number
  Arg
 [b] Redo record seq number
 
FUNCTIONALITY:
 
 KERNEL TRANSACTION UNDO
 
IMPACT:
 
 PROCESS FAILURE
 
 POSSIBLE ROLLBACK SEGMENT CORRUPTION
 
SUGGESTIONS:   
 
 
 This error may indicate a rollback segment corruption.
 
 
 This may require a recovery from a database backup depending on  
  the
 situation.
 
  For
 further analysis, please submit the trace files and alert.log to  
 
 Oracle Support Services.
 
 
 Known Issues:
 
You can restrict the list below to issues likely to affect one of the
 following versions by clicking the relevant button: 
The list below is restricted to show
 only bugs believed to affect version 11.2.0.1.Other bugs may affect this version but have not been confirmed as being
 relevant yet.
 
There are 2 bugs listed.
Prob
Bug
Fixed
Description
21977392
ORA-600 [4193] ORA-600 [ktbair1] ORA-600 [1234]
   ORA-600 [6856] block type ktu undo block on recovery of encrypt datafile
12821418
11.2.0.3.8, 11.2.0.3.BP18, 11.2.0.4, 12.1.0.1
Direct NFS appears to be sending zero length
   windows to storage device. It may also cause Lost Writes
·  *  indicates
 that an alert exists for that issue.
·  +  indicates
 a particularly notable issue / bug.
·  See Note:1944526.1 for details of other symbols used
 
 
 
 
REFERENCES
NOTE:146580.1 –
 What is an ORA-600 Internal Error?NOTE:8240762.8 –
 Bug 8240762 – Undo corruptions with ORA-600 [4193]/ORA-600 [4194] or ORA-600
 [4137] / SMON may spin to recover transaction

未找到您要查找的产品? 在社区中提问 …

Bug 21977392 – ORA-600 [4193] ORA-600 [ktbair1] ORA-600 [1234]
 ORA-600 [6856] block type ktu undo block on recovery of encrypt datafile (文档 ID
 21977392.8)
转到底部
修改时间:
2016-5-27
类型:
PATCH