Re: Sql Trace to detect concurrency issues

On 22 Jan 2006 12:52:09 -0800, "Sudhir" <sudhir.jorwekar_at_gmail.com> wrote:

>Hi,
>
>I have just started using oracle and currently working on the
>concurrency issues in it.
>
>For this I want to take the sql trace of various queries that are
>encountered by server along with transaction id (or session id) and
>time at which the query is executed. (The time and transaction id will
>help finding conflicts between transactions.)
>
>I tried to do it with the standard Sql_trace option, but the trace
>files generated are quite difficult to parse for above info.
>
>Instead what I would like is a trigger that dumps the sql text in a
>file/ database table along with session id and current time .
>
>I want to know
>1) if this is a feasible approach (if yes, the the event that occurs
>for each query so that I can write a trigger on it.)
>2) is there any other simpler approach to this problem :)
>
>thanks & regards,
>Sudhir.

1 Oracle doesn't have concurrency issues. 2 Triggers on select statements are not possible 3 to your question 2) stop wasting your time. Try to learn Oracle, by reading the documentation, do not try to make Oracle behave like sqlserver.

--
Sybrand Bakker, Senior Oracle DBA