Re: RMAN impact

From: Kevin Lidh <kevin.lidh_at_gmail.com>
Date: Thu, 9 Mar 2006 09:53:13 -0700
Message-ID: <cb4807f0603090853s4671a8a3wfc694c23fdef5ed3@mail.gmail.com>

On our largest database, approx 5 TB, we do our hot backup in the early hours. What you might see is:
Top 5 Timed Events

~~~~~~~~~~~~~~~~~~                                                     %
Total
Event                                               Waits    Time (s) Ela

Time

-------------------------------------------- ------------ -----------
--------
db file sequential read                       183,907,653   1,251,537
69.33
CPU time                                                      248,748
13.78
sbtwrite2                                       7,288,661     201,689
11.17
sbtbackup                                              46      31,919
1.77
buffer busy waits                               5,505,360      23,707

1.31

So there is an impact. To me, the alternative is worse.

On 3/9/06, David Sharples <davidsharples_at_gmail.com> wrote:
>
> yes the user can use it, rman is just a normal process. If you are
> struggling for resources then you will be struggling for resources.
>
> Use things like resource manager / profiles if you want to restrict its
> usage
>
>
> On 3/9/06, Li Li <litanli_at_gmail.com> wrote:
> >
> > I just started to look into RMAN backup and recovery and have a
> > question: for example, it takes 2 hours for RMAN to backup the database, how
> > much impact will RMAN have on the database during this 2 hours? Will user be
> > able to access the database during this 2 hours?
> >
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Thu Mar 09 2006 - 10:53:13 CST