Database Tuning (MOSC)

MOSC Banner

ORA-00060: Deadlock detected

edited Jan 19, 2016 10:01AM in Database Tuning (MOSC) 26 commentsAnswered

Hi,

I found following deadlock errors  in the alert log file.

2016-01-11 13:38:52.006000 +01:00
ORA-16198: LGWR received timedout error from KSR
ORA-16198: LGWR received timedout error from KSR
2016-01-11 13:38:55.855000 +01:00
ORA-00060: Deadlock detected. More info in file /app/eorp044/01/admin/diag/rdbms/p044a/p044a/trace/p044a_j013_53003.trc.
2016-01-11 15:18:52.916000 +01:00
ORA-00060: Deadlock detected. More info in file /app/eorp044/01/admin/diag/rdbms/p044a/p044a/trace/p044a_ora_1885.trc.
2016-01-11 15:28:51.485000 +01:00
ORA-00060: Deadlock detected. More info in file /app/eorp044/01/admin/diag/rdbms/p044a/p044a/trace/p044a_ora_1885.trc

.

I found the following solution on Oracle metalink. Could you please comment on this?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center