RE: Re: Why I don't like RMAN repositories

From: Mark W. Farnham <>
Date: Wed, 11 Dec 2013 14:23:26 -0500
Message-ID: <023f01cef6a6$77fb8760$67f29620$>

Speaking of plus ones: +1 to  

"So, in the end, what I did was first make an image copy of everything in
case I screwed up, which is always the best first step of any recovery process."  

Also +1 to belts and suspenders (belts and braces) with regard to recovery possibilities.  

(Especially including the online redo logs, even if normally you do not back those up. That is my fractional first mini-step of the overall first step of a copy of everything.)  

Oh, and stop apologizing about long posts. Your signal to noise ratio is excellent!  


From: [] On Behalf Of Tim Gorman
Sent: Wednesday, December 11, 2013 1:07 PM To: ORACLE-L
Subject: Fwd: Re: Why I don't like RMAN repositories  

...oh yes, and I forgot to mention a big "+1" to Andy Klock for mentioning the analytic aspect of an RMAN recovery catalog.

One good practical example of that approach is the "estimate_mttr.sql" script that I have posted on my website at <>
"", which uses a single mongo-licious SQL
statement to use the time to backup the components needed for recovery in order to estimate the time-to-restore for a database. Of course, the biggest weakness of the script is the assumption that time-to-backup is the same as time-to-restore, but it was a fun to pull together and an eye-opening view into the ways that the data in the recovery catalog database could be turned into useful analytic information.

Just like the AWR repository, the recovery catalog repository contains lots of great information not revealed by the standard functionality of the product(s) that use it.

You can't improve that which you don't measure.

Thanks Andy!

  • Original Message --------


Re: Why I don't like RMAN repositories


Wed, 11 Dec 2013 10:59:56 -0700


Tim Gorman <> <>



Evergreen Database Technologies, Inc.


Please pardon the lengthy response...


Received on Wed Dec 11 2013 - 20:23:26 CET

Original text of this message