Oracle中出现ORA-00600内部错误代码怎么办

类型:
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
II
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)

转到底部

类型:
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)

转到底部

类型:
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.
NB
Prob
Bug
Fixed
Description
II
21977392
ORA-600 [4193] ORA-600 [ktbair1] ORA-600 [1234]
   ORA-600 [6856] block type 'ktu undo block' on recovery of encrypt datafile
II
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

 
Bug 21977392  ORA-600
 [4193] ORA-600 [ktbair1] ORA-600 [1234] ORA-600 [6856] block type 'ktu undo
 block' on recovery of encrypt datafile
 This
 note gives a brief overview of bug 21977392.  The content was last updated on: 18-APR-2016 Click here for details of each of the
 sections below.
Affects:
Product (Component)
Oracle Server (Rdbms)
Range of versions believed to be affected
Versions BELOW 12.2
Versions confirmed as being affected
12.1.0.2
        (Server Patch Set)
12.1.0.1
        (Base Release)
11.2.0.4
Platforms affected
Generic (all / most platforms affected)
Fixed:
The fix for 21977392 is first
   included in
12.1.0.2.160419
        (Apr 2016) Database Proactive Bundle Patch
Interim patches may be available for earlier versions – click here to
 check.
Symptoms:
Related To:
Internal
        Error May Occur (ORA-600)
ORA-600
        [4193]
ORA-600
        [ktbair1]
ORA-600
        [6856]
ORA-600
        [1234]
Stack is likely to include
        kcbr_media_apply
Recovery
Physical
        Standby Database / Dataguard
Transparent
        Data Encryption
Description
This bug is only relevant
 when using Transparent Data Encryption
Media recovery crashes in a redo callback routine with some ORA600. The errors are usually ORA-600 [4193] and/or ORA-600 [ktbair1] or   ORA-600 [1234] ORA-600 [6856].Rediscovery Notes- Media recovery crashes in a redo callback routine with some ORA600.- The errors are usually ORA-00600:[4193] and/or ORA-00600:[ktbair1].- The ORA-600 [4193] has these characteristics:     – ORA-10560: block type 'KTU UNDO BLOCK'     – ORA-600 [4193] in parallel recovery slave     – call stack:        -> ksvrdp -> krp_slave_main -> krp_slave_apply ->          -> kcbr_media_apply -> kcbr_apply_change ->           -> kcoapl -> kturdb -> ORA-00600:[4193]     – the ORA-600 incident tracefile shows a dump of the ktudb       from the redo change vector, and all the contents look       like garbage, eg the "flg" field has bits set other than       these bits: 0x1FFF for example:       —-       *** ktuc_diag_dmp: dump of current change vector       ktudb redo: siz: 45736 spc: 47634 flg: 0x2740 seq: 0x6253 rec: 0x7f                  xid:  0xd29a.4e93.24dbeb07       Unexpected kcocv element following ktudb structure:       —-       this is also the case for ORA-600 [1234].     – the ORA600 incident tracefile also shows the details of the       block involved:       *** ktuc_diag_dmp: dump of buffer cache for rdba 0x010a63c2       and there will be a redo dump started but it may not be       complete, eg:         DUMP REDO          Opcodes *.*          DBAs (file#, block#):          (4, 680898) .     – if the redo dumps shows the problematic change vector header,       then it will be encrypted (ENC:1).- The ORA-00600:[ktbair1] has these characteristics:     – ORA-00600:[ktbair1] in parallel recovery slave     – call stack:        -> ksvrdp -> krp_slave_main -> krp_slave_apply ->          -> kcbr_media_apply -> kcbr_apply_change ->           -> kcoapl -> kdxlup -> ktbair2 -> ORA600:[ktbair1]     – the ORA600 tracefile shows the dump of the problematic change       vector header, and it is encrypted (ENC:1), eg:        Error 600 in redo application callback:          Dump of change vector:          CON_ID:0 TYP:0 CLS:1 AFN:7 DBA:0x034cd2b9 OBJ:166589            SCN:0x0000.17a2e5a8 SEQ:1 OP:10.18 ENC:1 RBL:0 FLG:0x0000          index redo (kdxlup): update keydata, count=2          KTB Redo          op: 0x0e  ver: 0x00          compat bit: 0 (pre-11) padding: 0          op: [ktbdir] invalid op: 0x0e       and there will be a redo dump started but it may not be       complete, eg:         DUMP REDO          Opcodes *.*          DBAs (file#, block#):          (7, 55366329) .        this is also the case for ORA-600 [6856]- the database is using encryption- dump the redo manually for the specific block involved:    – see the incident tracefile DUMP REDO, DBAs to find the file#      and block# to dump    – see the alert log to find which log was being applied at the      time of the OR6000 – this is the logfile to dump   syntax:   alter session set "_sga_clear_dump"=TRUE;   alter system dump logfile ''    dba min   dba max  ;   the redo dump should confirm the problematic change vector is   encrypted (ENC:1), and   the redo dump should confirm the problematic change vector is   very near to the start of the log – this is a very important   characteristic of this bug, if the problematic change vector   is NOT near to the start of the log, then it's unlikely that   this bug is involved.  note: this redo dump needs to be done on the customer system         because the encryption wallet (and its password) is        needed to decrypt the encrypted change vector data.Workaround If problem is encountered in a physical standby database, refresh the affected files from the primary database  Note: Any patch/fix for this bug will *not* "repair" already badly encrypted redo.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:21977392 (This link
 will only work for PUBLISHED bugs)Note:245840.1 Information on the sections in this article