Hi!

I know that this version is not supported by ElevateSoft, but...

A corporation have 3,7 GB sized database. They have two server services in one machine.
This needed because commonly the server out of allocatable memory space.

The sysadmin reported to me a daily problem that CPU usage is 70-30% by dbsrvr processes,
and this is periodically changed (70-30, 30-70).
When all of the users leaved the office, two of the connections are remained, and srvadmin
have been crashed two times, when he tried to kill these connections.
Only one way he have to solve the problem: the restart.

I want to ask that:
a.)
Have the dbsrvr some option to limit queries (timeout, like in php, or mysql) to not eat
up the resources?
Can I define in this in the client or in the server.

b.)
Have the dbsrvr and extra SQL monitor tool that can show me the last running queries?

Thanks for your help:
  dd

<< A corporation have 3,7 GB sized database. They have two server services
in one machine. This needed because commonly the server out of allocatable
memory space.

The sysadmin reported to me a daily problem that CPU usage is 70-30% by
dbsrvr processes, and this is periodically changed (70-30, 30-70). When all
of the users leaved the office, two of the connections are remained, and
srvadmin
have been crashed two times, when he tried to kill these connections.  Only
one way he have to solve the problem: the restart. >>

Did the Server Administration Utility actually crash ?  What was the error
message ?  Was the database server still responsive ?

<< Have the dbsrvr some option to limit queries (timeout, like in php, or
mysql) to not eat up the resources? >>

Your problem is not caused by queries eating up resources.  Most likely the
problem is caused by sessions that have been disconnected and haven't been
removed yet by the database server.  You can see this information in the
Server Administration Utility in the list of sessions present on the
database server.

Sorry I can't be more specific, but you're speaking in very general terms
about an issue that I have no information about.  It's almost impossible to
diagnose such problems with little information.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" wrote:

>The sysadmin reported to me a daily problem that CPU usage is 70-30% by
>dbsrvr processes, and this is periodically changed (70-30, 30-70). When all
of the users leaved the office, two of the connections are remained, and
>srvadmin have been crashed two times, when he tried to kill these connections.  
>Only one way he have to solve the problem: the restart. >>

>Did the Server Administration Utility actually crash ?

Yes. It crashed.

> What was the error
> message ?  
> Was the database server still responsive ?

I will ask it from the system administrator. Only what I know that srvadmin crashed two times, when the sysadmin tried to kill the two
remaining session (he reported me that users leaved the office, but the connections are remained).

>Your problem is not caused by queries eating up resources.  
>Most likely the
>problem is caused by sessions that have been disconnected and haven't been
>removed yet by the database server.  You can see this information in the
>Server Administration Utility in the list of sessions present on the
>database server.

And this can cause high CPU usage?

>Sorry I can't be more specific, but you're speaking in very general terms
>about an issue that I have no information about.  It's almost impossible to
>diagnose such problems with little information.

Ok, I undestand it. The sysadmin said only this, and that: when he restarted the services, the problem vanished in this server...
Hmmmmmmmm...

I will ask it from more info (log, crash report), and I will write to you again.

Thanks for your help:
  dd

<< And this can cause high CPU usage? >>

No, but it can cause the memory usage to be much higher than it needs to be,
and that can cause spurious issues with crashes, etc. due to unexpected "out
of memory" errors in areas of the code that may not handle them very
gracefully.  "Out of memory" errors are particularly bad because they can
prevent orderly shut down of the engine.  Even something as simple as
allocating a new string for an error message can fail, thus causing extreme
random behaviors in the engine.

--
Tim Young
Elevate Software
www.elevatesoft.com