RE: database resource usage

  • From: "Richard J. Goulet" <rgoulet@xxxxxxxxxx>
  • To: "ORACLE-L" <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 29 Sep 2006 09:27:52 -0400

Question & I'll admit to not having deeply read the previous posts on
this, but have you checked out the resource management capabilities of
the database?  It may not be feasible if the OLAP stuff is using the
same username as the OLTP user which I would submit is bad practice in
the first place.  And since resource profiles can be switched on the fly
that may alleviate end of month processing problems as well.

Dick Goulet, Senior Oracle DBA

45 Bartlett St  Marlborough, Ma 01752, USA
Tel.: 508.573.1978 |Fax:  508.229.2019 | Cell:508.742.5795 




From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Dennis Williams
Sent: Friday, September 29, 2006 9:21 AM
To: chris_stephens@xxxxxxxxxxxx
Subject: Re: database resource usage

I would argue that this is a people problem rather than a technical
problem. You are correct that this is not an ideal solution. I don't
think OLAP developers should be creating stuff that drives the system to
its knees. That is poor development practice. Some day they will release
one of these bad boys into production. Talk to them. Educate them. If
that doesn't work, you can put various quotas on them. Especially
emphasize that it is critical they don't do something dumb during the
month-end processing. Send out a monthly reminder. Back in the olden
mainframe days we all had to share one system, and etiquette prevailed. 
     I don't know of a tool, but would suspect you could put something
together using Unix tools such as ps, awk, perl, etc. Then you won't be
dependent on a vendor, but can perform your own upgrades.
     While you're at it, examine that month end load and see if any
tasks can be shifted in time to free up more resources.
Dennis Williams

GIF image

Other related posts: