Hello,

I have Oracle 10g (10.1.0.3.0) running on RHE box. When I perform a
pretty simple select, even like select * from dual, I see that Oracle
stops for 2-3 s. and not responding, then it's OK. This happens every
4-5 correct selects.

Any idea what is going on ?

Regards,

--
Piotr Kujawka

Piotr Kujawka wrote:
> Hello,
>
> I have Oracle 10g (10.1.0.3.0) running on RHE box. When I perform a
> pretty simple select, even like select * from dual, I see that Oracle
> stops for 2-3 s. and not responding, then it's OK. This happens every
> 4-5 correct selects.
>
> Any idea what is going on ?
>
> Regards,
>
> --
> Piotr Kujawka

No. You need to use normal diagnostic tools to check the CPU load.
Also you need to check (assuming you can still get in) what Oracle is
waiting for.

You might have just insufficient memory, and the box is swapping and
paging like hell when this happens. Which you could easily check with
vmstat and similar programs.
Does your box satisfies Oracle's mimimum requirements?

--
Sybrand Bakker
Senior Oracle DBA

sybrandb wrote:

> No. You need to use normal diagnostic tools to check the CPU load.
Load is low, less then 1, the box is boring. There os no harddisks
problem too, because they do noting.

> Also you need to check (assuming you can still get in) what Oracle is
> waiting for.
How can i check that ?

> You might have just insufficient memory, and the box is swapping and
> paging like hell when this happens. Which you could easily check with
> vmstat and similar programs.
No, like I wrote below, the machine is very low load and has ~3 GB free
memory.


> Does your box satisfies Oracle's mimimum requirements?

Yes, of course,

Thank You for help.

Regards,


--
Piotr Kujawka

Piotr Kujawka wrote:
> sybrandb wrote:
>
> > No. You need to use normal diagnostic tools to check the CPU load.
> Load is low, less then 1, the box is boring. There os no harddisks
> problem too, because they do noting.
>
> > Also you need to check (assuming you can still get in) what Oracle is
> > waiting for.
> How can i check that ?
>
> > You might have just insufficient memory, and the box is swapping and
> > paging like hell when this happens. Which you could easily check with
> > vmstat and similar programs.
> No, like I wrote below, the machine is very low load and has ~3 GB free
> memory.
>
>
> > Does your box satisfies Oracle's mimimum requirements?
>
> Yes, of course,
>
> Thank You for help.
>
> Regards,
>
>
> --
> Piotr Kujawka

Piotr, you can check what your database/session is waiting on via
several tools that Oracle provides.

If you can reproduce the problem you can run a trace on a session with
wait events and look that the trace.

You can run a statspack report to get an overview of the database.

You can query the v$system_event and v$session_events views.

You can find information on the v$ views in the Reference manual while
the Performance and Tuning manul is probably the best place to look how
to trace a session.

The manuals are availabe online from the main Oracle site (which will
route you to the technet copy of the manuals, sign-in not required)
and the newsgroup archives have many posts on some of these features.

HTH -- Mark D Powell --

Mark D Powell wrote:

> The manuals are availabe online from the main Oracle site (which will
> route you to the technet copy of the manuals, sign-in not required)
> and the newsgroup archives have many posts on some of these features.

What I see, when I connect as normal user (not sys) the problem still
occur. But when I connect as sys there are no breaks and the database
response correctly.

Regards,

--
Piotr Kujawka

On Fri, 29 Sep 2006 16:07:45 +0200, Piotr Kujawka
<piotr@toskasujnoping.org> wrote:

>What I see, when I connect as normal user (not sys) the problem still
>occur. But when I connect as sys there are no breaks and the database
>response correctly.

There is no difference between SYS and any other users.
I would recommend following up the steps outlined by Mark Powell.

--
Sybrand Bakker, Senior Oracle DBA