Helmut,
This thing with app servers and everyone ending up on the DB as a single
user (like PeopleSoft likes it) is one BIG pain in the &^%. Basically your
stuck with not being to limit anything. Reason is that you cannot predict what
jobs/sessions should have the longer vs. shorter limits. Setting any one of
these will cause the offending session to abort. OH, BTW: there's a bug in
8.1.7.0.0 (BUG # 2085332) where you set the CPU_PER_CALL and your user gets an
ORA-2394 vs. an ORA-2393 when they exceed the per call CPU utilization. It's
supposedly fixed in 9.2.
OH, don't forget for any profile limits to work you need to set
RESOURCE_LIMIT=TRUE in init.ora.
Dick Goulet
____________________Reply Separator____________________
Author: "Daiminger; Helmut" <[EMAIL PROTECTED]>
Date: 4/15/2002 6:08 AM
Hi!
We are experiencing performance problems on one of our production boxes,
because some sessions are using up all the resources. All the users connect
to the db through an application server using the same database user (approx
30 simultaneous connections).
I was thinking about using profiles to limit the amount of resources a
session can use. But I am pretty unsure to what values I should set the
single criterias. The db is running on a Sun server, 4 CPUs, 4 GB of RAM and
a Raid 0+1 disk array.
What would be reasonable ballpark numbers to set for
cpu_per_session
cpu_per_call
logical_reads_per_session
logical_reads_per_call
What would happen if cpu_per_session is set to 500 (i.e. 5 seconds) and the
session used up all that CPU time? Would the session error out then?
This is 8.1.7 on Sun Solaris.
Thanks,
Helmut
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>How to use profiles??</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Hi!</FONT>
</P>
<P><FONT SIZE=2>We are experiencing performance problems on one of our
production boxes, because some sessions are using up all the resources. All the
users connect to the db through an application server using the same database
user (approx 30 simultaneous connections).</FONT></P>
<P><FONT SIZE=2>I was thinking about using profiles to limit the amount of
resources a session can use. But I am pretty unsure to what values I should set
the single criterias. The db is running on a Sun server, 4 CPUs, 4 GB of RAM and
a Raid 0+1 disk array.</FONT></P>
<P><FONT SIZE=2>What would be reasonable ballpark numbers to set for</FONT>
</P>
<P><FONT SIZE=2>cpu_per_session</FONT>
<BR><FONT SIZE=2>cpu_per_call</FONT>
<BR><FONT SIZE=2>logical_reads_per_session</FONT>
<BR><FONT SIZE=2>logical_reads_per_call</FONT>
</P>
<P><FONT SIZE=2>What would happen if cpu_per_session is set to 500 (i.e. 5
seconds) and the session used up all that CPU time? Would the session error out
then?</FONT></P>
<P><FONT SIZE=2>This is 8.1.7 on Sun Solaris.</FONT>
</P>
<P><FONT SIZE=2>Thanks,</FONT>
<BR><FONT SIZE=2>Helmut</FONT>
</P>
</BODY>
</HTML>
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
