RE: Inheriting a "interesting" recovery process
- From: "Jesse, Rich" <Rich.Jesse@xxxxxx>
- To: <davidsharples@xxxxxxxxx>, <AGUERRA@xxxxxxxxx>
- Date: Fri, 4 Aug 2006 12:42:14 -0500
It also prevents rolling forward if a recovery is needed, i.e. PIT.
Rich
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of David Sharples
Sent: Friday, August 04, 2006 9:43 AM
To: AGUERRA@xxxxxxxxx
Cc: Jared Still; stvsmth@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx
Subject: Re: Inheriting a "interesting" recovery process
very poor reasons
all a shutdown does is clear out your buffer cache and shared pool
making the database have to work hard when you restart it.
What does keeping the archive logs have to do with anything. Don't you
keep all of them anyway?
On 04/08/06, Guerra, Abraham J <AGUERRA@xxxxxxxxx> wrote:
Well, the only reason I would do colds is that the database is
shut nicely and do not have to keep the archivelogs produced during the
backup... also, shutting down the database once in a while avoids having
problems with the fragmentation of the shared pool and stuff like
that...
Other related posts:
