Re: Oracle Locking Up

Daniel Morgan <damorgan_at_exxesolutions.com> wrote in message news:<3EAF63E5.CE227221_at_exxesolutions.com>...
> Mark D Powell wrote:
>
> > Daniel Morgan <damorgan_at_exxesolutions.com> wrote in message news:<3EAEC8D1.95FCED50_at_exxesolutions.com>...
> > > Oracle 9.2.0.1.0 on a single CPU 1.7GHz Pentium IV
> > >
> > > One user doing SELECTS from various tables none with more than 10K rows
> > > and here's what I get:
> > >
> > > SQL> select event, seconds_in_wait
> > > 2 from v_$session_wait;
> > >
> > > EVENT SECONDS_IN_WAIT
> > > ------------------------------------------------------ ---------------
> > > null event 0
> > > pmon timer 3
> > > rdbms ipc message 0
> > > rdbms ipc message 0
> > > rdbms ipc message 154
> > > rdbms ipc message 3
> > > rdbms ipc message 3
> > > smon timer 208
> > > library cache pin 0
> > > library cache lock 3
> > > SQL*Net message from client 306
> > > SQL*Net message from client 926
> > > SQL*Net message from client 256
> > >
> > > The lock up and these waits are outrageous. Any ideas will be
> > > appreciated.
> > >
> > > It is a student's machine and I would like to try to fix the problem by
> > > email or phone rather than driving to their house.
> > >
> > > Thanks.
> >
> > Daniel, is the problem repeatable after booting the machine?
> > Do queries against the rdbms dictionary run OK?
> >
> > HTH -- Mark D Powell --
>
> The problem is sporadic. When it locks up Oracle can be shut down with another SQL*Plus session / as sysdba
> and shutdown immediate. Then it may happen again hours later. Same goes for rebooting the machine. It will
> happen again but hours later.
>
> And what is strange is that it never seems to interfere with a SQL statement that is executing. The statement
> will finish, commit but never return to the SQL> prompt.

Ok, what is the OS? How much memory does it have? And how much virual memory is configured? Since the session has to be idle for a couple of hours for the problem to show up then in the meantime is the user firing up any games or other pieces of software? That is I am looking at the possibility of a specific conflict due to memory or possibly video.

Being that this is a student, and that the session has to sit idle a while, then as a work around could the student just stop the database when they are not going to be using it and start it up when they need it (at least uptil someone hits upon something useful)?

HTH -- Mark D Powell -- Received on Wed Apr 30 2003 - 08:49:04 CDT