RE: database resource usage
- From: "Stephens, Chris" <chris_stephens@xxxxxxxxxxxx>
- To: "Dennis Williams" <oracledba.williams@xxxxxxxxx>
- Date: Fri, 29 Sep 2006 09:11:59 -0500
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:
