ORA-600 [2662] “Block SCN is ahead of Current SCN“

ORA-600 [2662] "Block SCN is ahead of Current SCN" (Doc ID 28929.1) ​编辑To Bottom

ORA-600 [2662] “Block SCN is ahead of Current SCN“_第1张图片





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

PURPOSE:            
  This article discusses the internal error "ORA-600 [2662]", 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 [2662] [a] [b] [c] [d] [e]
 
VERSIONS:
  versions 6.0 to 12.1
 
DESCRIPTION:

  A data block SCN is ahead of the current SCN.

  The ORA-600 [2662] occurs when an SCN is compared to the dependent SCN 
  stored in a UGA variable.

  If the SCN is less than the dependent SCN then we signal the ORA-600 [2662]
  internal error.

ARGUMENTS:
  Arg [a]  Current SCN WRAP
  Arg [b]  Current SCN BASE
  Arg [c]  dependent SCN WRAP
  Arg [d]  dependent SCN BASE 
  Arg [e]  Where present this is the DBA where the dependent SCN came from.
 
FUNCTIONALITY:      
  File and IO buffer management for redo logs
 
IMPACT:
  INSTANCE FAILURE
  POSSIBLE PHYSICAL CORRUPTION
 
SUGGESTIONS:        
     
  There are different situations where ORA-600 [2662] can be raised.

  It can be raised on startup or during database operation.

  If not using Parallel Server, check that 2 instances have not mounted
  the same database.

  Check for SMON traces and have the alert.log and trace files ready
  to send to support.

  Check the SCN difference [argument d]-[argument b].

  If the SCNs in the error are very close, then try to shutdown and startup
  the instance several times. 

  In some situations, the SCN increment during startup may permit the 
  database to open. Keep track of the number of times you attempted a 
  startup.

  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:
        

 
 
NB Prob Bug Fixed Description
III 14351566 11.2.0.3.8, 11.2.0.3.BP21, 11.2.0.4, 12.1.0.1 ORA-600 [kclchkblk_4] ORA-600 [2662] when doing flash back
- 34938584 AIM: ORA-603 / ORA-600 [2662] - kpdbcrefreshdrv
II 34624225 AIM:ORA-600 [2662] - kcsgcsn8
III 13087149 12.2.0.1 ORA-600 [2662] after convert to snapshot standby following a flashback db
- 4453449 10.2.0.2, 11.1.0.6 OERI:3020 / corruption errors from multiple FLASHBACK DATABASE
II 5889016 10.1.0.2 Corruption / OERI during recovery
- 2899477 9.2.0.5, 10.1.0.2 Minimise risk of a false OERI[2662]
- 2764106 9.2.0.5, 10.1.0.2 False OERI[2662] possible on SELECT which can crash the instance
I 2216823 10.1.0.2 OERI [2662] reusing a TEMPFILE with a restored database
- 2054025 9.0.1.3, 9.2.0.1 OERI:2662 possible on new TEMPORARY index block
P - 647927 8.0.4.2, 8.0.5.0 Digital Unix ONLY: OERI:2662 could occur under heavy load
- 851959 7.3.4.5 OERI:2662 possible from distributed OPS select
  • '*' 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:336196 - ORA-600 [2662], [0], [2346030], [64338], [42] UNDER HEAVY LOADING
BUG:851959 - ORA-600 [2662] OCCURRED DURING CREATE SNAPSHOT AT MASTER SITE
NOTE:1021243.6 - This document has been replaced with more recent information on this topic. Please refer to more recent documentation.

NOTE:2899477.8 - Bug 2899477 - Minimise risk of a false OERI[2662]

BUG:297197 - WHEN RUNNING IN PARALLEL MODE
NOTE:5889016.8 - Bug 5889016 - Corruption / OERI during recovery
NOTE:647927.8 - Bug 647927 - Digital Unix ONLY: OERI:2662 could occur under heavy load
NOTE:851959.8 - Bug 851959 - OERI:2662 possible from distributed OPS select


NOTE:4453449.8 - Bug 4453449 - OERI:3020 / corruption errors from multiple FLASHBACK DATABASE
NOTE:146580.1 - What is an ORA-600 Internal Error?
NOTE:2054025.8 - Bug 2054025 - OERI:2662 possible on new TEMPORARY index block
NOTE:2216823.8 - Bug 2216823 - OERI [2662] reusing a TEMPFILE with a restored database
NOTE:2764106.8 - Bug 2764106 - False OERI[2662] possible on SELECT which can crash the instance
BUG:195115 - GETS ORA 600 [2662][0][33702][0][33793][][][] ON STARTUP

你可能感兴趣的:(DBRecovery,数据库,oracle)