RE: RMAN Reporting?

I don't think you can do it. I have resorted to tracking this through a separate database schema and the invoking scripts for the backup. At the beginning of the backup a timestamp and backup identification is inserted into a "backup tracking" table and then at the end another timestamp is inserted with a return code. If the backup causes the script to fail for some reason then the end time will be null. A reporting script can then be run against the table to identify "hung" backups and to do trend analysis against backups in general.

At 01:09 AM 12/12/2002 -0800, you wrote:

> From: "Walter K" <ORA1034_at_sbcglobal.net>
> Date: Wed, 11 Dec 2002 15:01:02 -0500
> Subject: RE: RMAN Reporting?
>
>I agree. I can get what I want by looking at time
>stamps on log files, grepping, etc. but that can be a
>lot of work to put together. I have a need to do some
>trending analysis and was expecting that I could get
>this info out of the RMAN tables but it's looking like
>that's just wishful thinking.
>
>-w

Andy Rivenes
arivenes_at_llnl.gov

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Andy Rivenes
  INET: arivenes_at_llnl.gov

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).