Re: RMAN or Hot Backup

From: Michael Austin <>
Date: Mon, 30 Mar 2009 13:31:26 -0500
Message-ID: <3f8Al.11087$>

John Schaeffer wrote:
> On Mar 30, 12:26 pm, Michael Austin <>
> wrote:
>> Mladen Gogala wrote:
>>> On Fri, 27 Mar 2009 14:43:43 -0500, Michael Austin wrote:
>>>> Yes it does/did... Again using the methodology is essentially initiating
>>>> a controlled crash. - but, as I have experienced, depending on where the
>>>> Database writer and logwriters are at the exact moment of the break, you
>>>> can get corrupted UNDO segments and then you are hosed - and now you try
>>>> again - maybe next time you will get lucky and it will work.
>>> You can get that even with "alter system suspend" immediately before
>>> the split?
>> shhh... don't them that... they would try to use it with things other
>> than what it was intended...  And most places do not like using it
>> because EVERYTHING stops during that time period - so they pays their
>> money and takes their chances...

> Yeah, this is a bunch of info that everyone has provided. So, here
> comes the document and there goes away the idea of the hot backup
> solution. I've used RMAN and it really removes a bunch of the tasks.
> This one DBA who sits next to me claims that a hot backup can do
> EVERYTHING RMAN can, such as compression, including archive logs in
> the backup, validating the backup, reporting, etc......which we all
> know is flat out wrong........

Yeah - he needs to work in a real environment where RMAN is the ONLY option (too large and too complicated for his antiquated shell HB scripts.) Received on Mon Mar 30 2009 - 13:31:26 CDT

Original text of this message