ORA-600 [4512] "Lock count mismatch"

ORA-600 [4512] "Lock count mismatch"  To BottomTo Bottom




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

PURPOSE:
  This article discusses the internal error "ORA-600 [4512]", 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 [4512]
VERSIONS:
  versions 6.0 and above

DESCRIPTION:

  Oracle is checking the status of transaction locks within a block.

  If the lock number is greater than the number of lock entries, 
  ORA-600 [4512] is reported followed by a stack trace, process state 
  and block dump.

  This error possibly indicates a block corruption.

FUNCTIONALITY:
  TRANSACTION BLOCK CODE

IMPACT:
  PROCESS FAILURE
  POSSIBLE PHYSICAL BLOCK CORRUPTION

SUGGESTIONS:

  Treat it as block corruption.

  E.g if in archivelog mode, restore and rollforward.

  See Note:28814.1 for block corruption diagnostics and resolution options.

  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.4.
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
IIII 18940497 11.2.0.4.BP13, 12.1.0.2.3, 12.1.0.2.DBBP04, 12.2.0.1 ORA-600 [6856] ORA-600 [4512] ORA-600 [kafspa:columnBuffer1] ORA-600 [kdblkcheckerror] [6126] Wrong Results after UPDATE on Table with Chained rows
  • '*' indicates that an alert exists for that issue.
  • '+' indicates a particularly notable issue / bug.
  • See Note:1944526.1 for details of other symbols used

你可能感兴趣的:(troubleshooting)