RE: Tuning RMAN backup and recovery

From: Taylor, Chris David <Chris.Taylor_at_ingrambarge.com>
Date: Mon, 11 Feb 2008 17:09:37 -0600
Message-ID: <17E4CDE8F84DC44A992E8C00767402E0860FAC@spobmexc02.adprod.directory>


You mean you weren't using dbms_stats.gather_fixed_objects_stats()??

I thought EVERYONE was using that by now...

KIDDING!! Only kidding!

Chris Taylor
Sr. Oracle DBA
Ingram Barge Company
Nashville, TN 37205
Office: 615-517-3355
Cell: 615-354-4799
Email: chris.taylor_at_ingrambarge.com

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Don Seiler
Sent: Monday, February 11, 2008 3:55 PM
To: oracle-l
Subject: Re: Tuning RMAN backup and recovery

Just wanted to follow-up here as well. I finally decided to file an SR, and Oracle came back pretty quickly with Note 462879.1 [0], fixed in 10.2.0.4 and 11g. It seems that, in this bug, queries against v$rman_status table can take an extremely long time, and that table is queried for every datafile switch during RMAN DUPLICATEs

Workarounds are to either set sesiion-level optimization to RULE based, or to gather fixed object statistics via dbms_stats.gather_fixed_objects_stats();.

I've done the latter, but haven't had an opportunity to perform another restore as our development instances are needed until the next release in two weeks. I'll report back with results when I do.

[0]

https://metalink.oracle.com/metalink/plsql/f?p=130:14:698790149932005062 0::::p14_database_id,p14_docid,p14_show_header,p14_show_help,p14_black_f rame,p14_font:NOT,462879.1,1,1,1,helvetica

-- 
Don Seiler
http://seilerwerks.wordpress.com
ultimate: http://www.mufc.us
--
http://www.freelists.org/webpage/oracle-l




--
http://www.freelists.org/webpage/oracle-l
Received on Mon Feb 11 2008 - 17:09:37 CST

Original text of this message