Re: RMAN or Hot Backup
From: Michael Austin <maustin_at_firstdbasource.com>
Date: Fri, 10 Apr 2009 08:52:55 -0500
Message-ID: <7bIDl.4501$im1.2177_at_nlpi061.nbdc.sbc.com>
Mladen Gogala wrote:
> Na Thu, 09 Apr 2009 19:07:06 -0500, Bob Jones napisao:
>
>
> He probably means something like "ALTER SYSTEM SUSPEND", frequently
> employed with snapshot technology or with BCV splitting. I am by no
> means a mind reader, but those are the first things that come to mind
> when someone starts talking about suspending the system.
>
Date: Fri, 10 Apr 2009 08:52:55 -0500
Message-ID: <7bIDl.4501$im1.2177_at_nlpi061.nbdc.sbc.com>
Mladen Gogala wrote:
> Na Thu, 09 Apr 2009 19:07:06 -0500, Bob Jones napisao:
>
>> I am not sure what you meant by avoiding redo problems and suspending >> the system. I see neither being a problem with non-RMAN backups.
>
> He probably means something like "ALTER SYSTEM SUSPEND", frequently
> employed with snapshot technology or with BCV splitting. I am by no
> means a mind reader, but those are the first things that come to mind
> when someone starts talking about suspending the system.
>
I have seen this tried on an extremely busy database. It took almost 1.5hrs to get the database to a point where it would "suspend" blocking ALL processing while it goes into suspend mode. Once the BCV was "split", it was set to resume. If yours is an online/web backend - this could be a MAJOR problem.
<snip> Received on Fri Apr 10 2009 - 08:52:55 CDT