Re: finding solution 4 this Special DeadLock

From: Mladen Gogala <>
Date: Sun, 10 Feb 2008 12:47:11 +0100 (CET)
Message-ID: <fomo7v$1fr$>

On Sun, 10 Feb 2008 02:04:02 -0800, meysam.khayatan wrote:

> Dear friends

This is an annoying start. I am very selective about my friends and I cannot recollect ever becoming your friend.

> i have a problem in DeadLock
> in udump alert log file i have a deadlock that in trace file described
> as below:
> =============================================================== ***
> 2008-02-06 09:00:06.223
> *** SESSION ID:(32.18099) 2008-02-06 09:00:06.219 DEADLOCK DETECTED
> Current SQL statement for this session: LOCK TABLE PER_ANALYSIS_CRITERIA
> IN EXCLUSIVE MODE The following deadlock is not an ORACLE error. It is a

It is an application error. Fix the @#$%! application. Using exclusive table locks in an application that uses Oracle RDBMS is about the most idiotic thing one can make. Piece on Earth!

Received on Sun Feb 10 2008 - 05:47:11 CST

Original text of this message