RE: How to justify a Database Shutdown
- From: "Goulet, Richard" <Richard.Goulet@xxxxxxxxxxx>
- To: "oracle-l" <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 19 Jan 2009 11:14:12 -0500
This sounds like a hosted environment from the original message.
Consequently one might want to look back at the contract. Shutting a
database down, even if at the customer's request, could be seen as a
failure to maintain the SLA which could result in a penalty to the
hosting company. Now if that's the case, management can make the case
back to the customer that they need to clean up their application or
else require a change in the contract so that the shutdown does not
count against the SLA. Hate to say I've seen a client do that to a
hosting company just to save a buck, but I have.
Dick Goulet
Senior Oracle DBA
PAREXEL International
978.313.3426
information transmitted in this communication is intended only for the
person or entity to which it is addressed and may contain confidential
and/or privileged material. Any review, retransmission, dissemination or
other use of, or taking of any action in reliance upon, this information
by persons or entities other than the intended recipient is prohibited.
If you received this in error, please destroy any copies, contact the
sender and delete the material from any computer.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Michael Fontana
Sent: Monday, January 19, 2009 10:58 AM
To: 'oracle-l'
Subject: RE: How to justify a Database Shutdown
<<
Hmmmm, we have a few dozen a day on a table
with 2.7 *billion* rows and that instance stays up for
months...
More than likely that problem - if indeed there is one - can
be solved with a flush of the shared pool at a convenient idle point.
I can't think of an instance where anyone would need to
"recycle" - that is such an inappropriate term - an Oracle instance
in Unix that is not in memory or cpu shortage.>>
Original poster did not indicate it, but one thing I would check is to
assure this is a dedicated database server. We have seen DB servers
running client processes that do leak memory and will benefit from the
reboot. So, this may not be a database-specific problem in such a case.
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
