Re: strange select issue

From these enqueue waits, it is clear that your session is waiting on a lock. You'll have to query V$LOCK to see who is holding that lock which you seek. Until this lock is released, your session will wait forever.

HTH,
Brian

Tom wrote:
>
> > WAIT #1: nam='enqueue' ela= 0 p1=1397948422 p2=2 p3=1
> > WAIT #1: nam='enqueue' ela= 0 p1=1397948422 p2=2 p3=1
> > WAIT #1: nam='enqueue' ela= 0 p1=1397948422 p2=2 p3=1
> > WAIT #1: nam='enqueue' ela= 0 p1=1397948422 p2=2 p3=1
> > WAIT #1: nam='enqueue' ela= 0 p1=1397948422 p2=2 p3=1
> > WAIT #1: nam='enqueue' ela= 0 p1=1397948422 p2=2 p3=1
> > WAIT #1: nam='enqueue' ela= 0 p1=1397948422 p2=2 p3=1
>
> looking for info on this i see that these could be related to locks however the docs say...
>
> enqueue - The process is waiting on an enqueue (a lock you can see in v$lock). This commonly occurs when one user is trying to
> update a row in a table that is currently being updated by another user
>
> however this is occuring when i'm trying to import the data into an empty user also? am i missing something as i don't really see
> where the issue is.
>
> thanks for the inout so far.
>
> Tom

-- 
===================================================================

Brian Peasland
dba_at_remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.


"I can give it to you cheap, quick, and good. Now pick two out of
 the three"