Re: Locks

Looks like full table scans going on on that major table or that jerk must have created more havoc.
Full table scans can be shown through v$sysstat or v$sesstat, join on of those tables with v$statname and you will know it. Question: Did you create a primary key constraint or did you create an index only.
This also could be a source of problems

Hth,

--
Sybrand Bakker, Oracle DBA
<amerar_at_ci.chi.il.us> wrote in message news:7v71s1$vbu$1_at_nnrp1.deja.com...
>
>
>
> Hello,
>
> Perhaps this post is worthless, but what is a good way to try and find
> out why a database starts running slowly. I take a look at the the
> locks view and see about 40 locks on a certain table. It is possible
> that many users are updating this table and creating a bottle neck. I
> also see tons of updates happening in the v$session view.
>
> My question is, how do I actually pin point the problem? Everything was
> running fine yesterday. Then, some jerk accidentally dropped a promary
> key index on a major table. It took 45 minutes to re-create this index,
> and everything has been going slow since.
>
> I am guessing that all users are on re-entering their work, but how can
> I be sure that this is what is causing the problems??
>
> Arthur
> amerar_at_ci.chi.il.us
>
> ps. Send a copy to e-mail please.
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Wed Oct 27 1999 - 12:38:36 CDT