Note: For additional ORA-600 related information please read Note:146580.1
PURPOSE:
This article discusses the internal error "ORA-600 [504]", 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 [504] [a] [b] [c] [d] [e] [f] [g]
VERSIONS:
versions 6.0 to 9.2
DESCRIPTION:
This ORA-600 triggers when a latch request violates the ordering
rules for obtaining latches and granting the latch would potentially
result in a deadlock.
These ordering rules are enforced by assigning each latch a "level#",
and checking requested-level vs owned-levels on each latch request.
ARGUMENTS:
Arg [a] the requested latch address
Arg [b] bit array of latches owned
Arg [c] the level of the requested latch
Arg [d] the name of the requested latch
Arg [e] the child latch number of the requested latch
Arg [f] if non zero, allows 2 wait gets of children
Arg [g] address of latch owned at this level
FUNCTIONALITY:
KERNEL SERVICE LAYER - LATCHING
IMPACT:
PROCESS FAILURE
NON CORRUPTIVE - No underlying data corruption.
SUGGESTIONS:
Look for trace files generated at the time of the error.
Contact Oracle Support Services and provide the alert.log and
associated trace files for further diagnosis.
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:
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.