Re: database resource usage

  • From: "Dennis Williams" <oracledba.williams@xxxxxxxxx>
  • To: chris_stephens@xxxxxxxxxxxx
  • Date: Fri, 29 Sep 2006 09:23:27 -0500

Chris,

Okay, you answered my question while I was typing it. I think your mission
is to tell management that if they are going to develop a proper data
warehouse, they should plan to purchase another server.
   I used to work for a tightfisted organization that resented spending
money for anything. They were planning to share an existing transaction
application server with their data warehouse. Once they realized how spikey
the load on a DW is, I never saw them open their pocketbook so fast. They
had that new server in there in a couple of days and were demanding that I
get Oracle installed and the database moved over there pronto.
   I don't think most monitoring tools will help you.  But you must
immediately read Tim Gorman's paper: Scaling to Infinity immediately. This
can be found at: http://www.evdbt.com/papers.htm
Make sure these guys design this DW right from the ground up.

Dennis Williams

On 9/29/06, Stephens, Chris <chris_stephens@xxxxxxxxxxxx> wrote: 

 The olap stuff is development.  I can't come down on them for trying
stuff out.  They need to be able to do that.  The problem is that our
development/test databases are on the same machine and there is no way that
i know of to limit percentages of server resources to specific databases on
Red Hat 4.  ...everyone (developers here) keeps saying that resource manager
can do this but that only works within databases.

I'm looking to gather ammunition for a change in our server architecture.

Chris

 ------------------------------
*From:* Dennis Williams [mailto:oracledba.williams@xxxxxxxxx]
*Sent:* Friday, September 29, 2006 8:21 AM
*To:* Stephens, Chris
*Cc:* ORACLE-L
*Subject:* Re: database resource usage


 Chris,

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

CONFIDENTIALITY NOTICE:
This message is intended for the use of the individual or entity to which
it is addressed and may contain information that is privileged,
confidential and exempt from disclosure under applicable law. If the
reader of this message is not the intended recipient or the employee or
agent responsible for delivering this message to the intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by email reply.

Other related posts:

  1. Home
  2. oracle-l
  3. Archive
  4. 09-2006