RE: RMAN catalog operations taking 128 seconds per file - where is the bottleneck (and no guessing)
- From: <rajendra.pande@xxxxxxx>
- To: <sacrophyte@xxxxxxxxx>, <jkstill@xxxxxxxxx>
- Date: Wed, 13 Oct 2010 16:08:21 -0400
You could run it in debug mode and see where the trace leads you.
How big is the catalog size - as Jared said there could be a FTS
I have seen that RMAN is good at what it does but there are quite a few
gotcha's with the catalog.
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Charles Schultz
Sent: Wednesday, October 13, 2010 4:00 PM
To: Jared Still
Cc: ORACLE-L
Subject: Re: RMAN catalog operations taking 128 seconds per file - where
is the bottleneck (and no guessing)
Thanks, Jared, looks like it could quite possibly be unpublished bug
7444008
<https://supporthtml.oracle.com/ep/faces/secure/km/BugSearch.jspx?bugId=
7444008> . I hate bugs. Still, I am curious, what exactly is the root
problem?
On Wed, Oct 13, 2010 at 14:45, Jared Still <jkstill@xxxxxxxxx> wrote:
On Wed, Oct 13, 2010 at 12:05 PM, Charles Schultz <sacrophyte@xxxxxxxxx>
wrote:
Good day, list,
What would cause an RMAN catalog operation to last a relatively eternal
128 seconds?
There are a number of notes on MOS regarding RMAN performance, you
may want to check there.
IIRC there are some indexing issues, though I can't recall any version
#'s.
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Oracle Blog: http://jkstill.blogspot.com
Home Page: http://jaredstill.com
--
Charles Schultz
Please visit our website at
http://financialservicesinc.ubs.com/wealth/E-maildisclaimer.html
for important disclosures and information about our e-mail
policies. For your protection, please do not transmit orders
or instructions by e-mail or include account numbers, Social
Security numbers, credit card numbers, passwords, or other
personal information.
Other related posts:
