How to extract RMAN logs (Run through OEM or Rman prompt) from the Recovery Catalog
(Doc ID 1432185.1)
Last updated on OCTOBER 27, 2016
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.4 to 220.127.116.11 [Release 10.2 to 11.2]
Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [Release 11.2]
Information in this document applies to any platform.
When RMAN is run all rman output is logged to v$rman_output - this view is an in-memory view holding up to 32768 rows and the content is lost if the target is restarted. If a catalog is used, the contents of v$rman_output are stored in the catalog ROUT table during the resync process.
ROUT is typically used by OEM Grid and Database Control to view logs from the RMAN jobs but there is no easy way to print the logs via the GUI interface. This note explains how to extract the rman logs from the catalog which is useful particularly where logs need to be supplied to Support for problem analysis.
It is also useful in any situation where rman logs have been lost or deleted and are then needed later on.
Be aware though that by default only 7 days of logs are kept in ROUT.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|