I hear ya!!
We have presently 8.1.7.4 on Solaris 7.
In short, I'll tell you we ask our customers in the field to bounce the DB
monthly.
( Personnally, I think the SA's liked that fact so they could feel better
about booting the OS as well)
In the past I've had to fight the "Unable to allocate shared memory pool
size <bytes>'.
It looked like it was one or all of the following:
(1) Oracle - neededing 8.1.7.4 vice 8.1.7.0 to address memory leaks.
(2) Replication Threads (memory leaks ??? unable to prove)
(3) Our own code as a result of some patch not being tested long enough.
(4) Who knows what else, could never pin point the problem even looking at
"$" tables and "hidden" oracle parameters?
About a year ago we told them to start bouncing the DB when a window of
opportunity came and I have not had any reported problems from them or at
our own development sites.
Any way, for what its worth, these are my thoughts.
Jeff
-----Original Message-----
From: oracledba-return-122728-JEFFERY.L.SCHRENK=saic.[Email address protected]
[mailto:oracledba-return-122728-JEFFERY.L.SCHRENK=saic.[Email address protected]
n Behalf Of Anthony Molinaro
Sent: Wednesday, January 04, 2006 9:03 AM
To: LazyDBA Discussion
Subject: bouncing the db?
hello dba's,
I have a question that I am hoping you can help with.
We have different rdbms at my company and as expected
each one is treated differently.
from our experience (well, from the suggestion of sql server
consultants)
its good to bounce the sql server databases every so often.
now, I've never done this with oracle but I am wondering
if any of you have.
I am ofcourse aware of the various drawbacks to bouncing
the db (such as flushing the caches making all new sql hard parsed)
but it would be done at our maintenance window (so, no worries
about users and their sql).
over the last 6 months we've hit some bugs with oracle that neither
I nor oracle support have been able to really fix (we're talking
severity 1 tar here, so, very senior support analysts working with
me to resolve various problems as we got nowhere).
in some cases (magically) bouncing the db
(at the suggestion of support) has helped.
I'm not crazy about doing this all the time but if it saves me
from all-nighters and rebuilding production from standby via
failover (which is a total pain as our db's are ~1tb) then I'll do
it.
this would be a monthly thing or every other month.
so, we're talking 6 - 12 bounces a year.
any feedback (good or bad) would be appreciated.
thanks guys/gals,
Anthony
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html
Oracle LazyDBA home page