RE: Tool recommendation
- From: "Goulet, Richard" <Richard.Goulet@xxxxxxxxxxx>
- To: <nupendra@xxxxxxxxxxx>, <cary.millsap@xxxxxxxxxxxx>
- Date: Wed, 18 Aug 2010 08:40:53 -0400
One VERY useful profile parameter in these cases is the CPU_PER_CALL.
I've had this limited down to something like 5 minutes in the past for a
user who could not control their SQL. If left to unlimited their sql
would run for days. IDLE_TIME is another good one for those folks who
don't know how to properly shutdown their PC's.
Dick Goulet
Senior Oracle DBA/NA Team Lead
PAREXEL International
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Upendra N
Sent: Wednesday, August 18, 2010 1:07 AM
To: cary.millsap@xxxxxxxxxxxx
Cc: freek.dhooge@xxxxxxxxx; mark.powell2@xxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: RE: Tool recommendation
Cary,
That is very true. Though most of their data comes from individual
tables, occasionally they may join..
I will also put some additional restrictions on their profile.
Thanks for catching it!
-Upendra
________________________________
From: cary.millsap@xxxxxxxxxxxx
Date: Tue, 17 Aug 2010 14:54:11 -0500
Subject: Re: Tool recommendation
To: nupendra@xxxxxxxxxxx
CC: freek.dhooge@xxxxxxxxx; mark.powell2@xxxxxx; oracle-l@xxxxxxxxxxxxx
All these thoughts of people who don't know SQL writing SQL, returning
results sets with six-figure cardinalities, ...quite arousing.
Sounds like the opening chapter of an interesting story. :-)
Giddy-up!
Cary Millsap
Method R Corporation
http://method-r.com
http://carymillsap.blogspot.com
On Tue, Aug 17, 2010 at 2:40 PM, Upendra N <nupendra@xxxxxxxxxxx> wrote:
Thanks for everyone who responded.
I'll enable sqlnet.expire_time, that should handle the dead
connections.
I checked out SQL Developer, it is a nice query tool but not
intuitive enough for some one who doesn't know SQL.
Right now in MS Access the business users drag/drop columns to
build a query, anything similar in nature would be easier for me to
sell.
Am I just being paranoid or Access is capable of handling large
queries (upto ~200K records)?
-Upendra
> From: Freek.DHooge@xxxxxxxxx
> To: mark.powell2@xxxxxx; oracle-l@xxxxxxxxxxxxx
> Date: Tue, 17 Aug 2010 16:40:48 +0200
> Subject: RE: Tool recommendation
>
> Hi,
>
> Another solution (depending if the session is really dead)
could be to enable dcd (dead client detection, sqlnet.expire_time) in de
sqlnet.ora file on de server.
>
>
http://download.oracle.com/docs/cd/B19306_01/network.102/b14213/sqlnet.h
tm#sthref475
>
>
>
> regards,
>
> Freek D'Hooge
> Uptime
> Oracle Database Administrator
> email: freek.dhooge@xxxxxxxxx
> tel +32(0)3 451 23 82
> http://www.uptime.be
> disclaimer: www.uptime.be/disclaimer
> --
> From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Powell, Mark
> Sent: dinsdag 17 augustus 2010 16:09
> To: oracle-l@xxxxxxxxxxxxx
> Subject: RE: Tool recommendation
>
> Why not write a dead session detection script that looks for
and clears these sessions out and schedule it to run every X minutes?
>
> Or maybe create an on-demand script that is launched via a web
application or by the operators.
> --
> //www.freelists.org/webpage/oracle-l
>
>
Other related posts:
