oracle+600+4511,ORA-600 [4511] "Row locked by inactive ITL" (文档 ID 39553.1)

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

PURPOSE:

This article discusses the internal error "ORA-600 [4511]", 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 [4511] [a] [b] [c] [d] [e]

VERSIONS:

Versions 6.0 and later

DESCRIPTION:

We receive this error when a row lock is being tested and the lock is

not active at the time.

This may also be caused by having more than 4095 rows in a single

data block. Only blocks of 32Kb can contain this many rows. The

workaround is to limit the number of rows in the block, by setting

pctfree to a higher value.

FUNCTIONALITY:

TRANSACTION BLOCK OPERATIONS

IMPACT:

PROCESS FAILURE

POSSIBLE BLOCK CORRUPTION.

SUGGESTIONS:

If you know the table(s) involved, use ANALYZE TABLE

VALIDATE STRUCTURE CASCADE; to check for possible problems.

Run DBVERIFY on any datafiles associated with the table(s)

This can be related to a Consistent Read (CR) problem, so shutdown and

restart the instance and see if the problem reproduces.

Submit all trace files and the alert.log to Oracle Support Services

for further review and analysis.

Known Issues:

Known Bugs

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

NB

Bug

Fixed

Description

+

11.2.0.1.BP08, 11.2.0.2.2, 11.2.0.2.BP02, 11.2.0.3, 12.1.0.1

Block Corruption with PDML UPDATE. ORA_600 [4511] OERI[kdblkcheckerror] by block check

9.2.0.7, 10.1.0.4, 10.2.0.1

Update of a row with more than 255 columns can cause block corruption

'*' indicates that an alert exists for that issue.

'+' indicates a particularly notable issue / bug.

'I' indicates an install issue / bug included for completeness.

'P' indicates a port specific bug.

"OERI:xxxx" may be used as shorthand for ORA-600 [xxxx].

REFERENCES:

Note: 28814.1 Handling Oracle Block Corruptions in Oracle7/8/8i