Email: service@parnassusdata.com 7 x 24 online support!

Oracle ORA-600 [4511] "Row locked by inactive ITL"

Oracle ORA-600 [4511] "Row locked by inactive ITL"

ORA-600 [4511] "Row locked by inactive ITL"

 

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 <table_name>

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.

 

NB Bug Fixed Description

+ 9724970 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

4000840 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

 

ORA-600 [4511] [a] [b] [c] [d] [e]

Versions: 6.0.37 - 7.3.2 Source: ktb.c

===========================================================================

Meaning: Row lock points to inactive ITL entry. (ktbgtl)

 

Argument Description:

---------------------------------------------------------------------------

Diagnosis:

Watch out for migrated DB from earlier version where bugs below

may appear.

Isolate the trace file and get the bad block id.

ANALYZE TABLE <table_name> VALIDATE STRUCTURE on the bad table.

Bounce DB and see if reproduces as can be related to CR.