RMAN Restore Performance
(Doc ID 740911.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 16-July-2015***
Quite often when considering RMAN restore performance, the first thing that springs to mind is the speed of the tape device, the media manager configuration, the restore script and the no:channels being allocated. Yet the backup itself and how the backup was originally written can have a huge impact on restore performance and this is what this note is primarily concerned with.
This note is intended for use by Database Administrators and Support personnel investigating RMAN restore performance specifically from a tape backup. It specifically looks at issues related to the processing of RMAN metadata, retrieval of the data from tape and when a restore is performing badly, how to determine where the time is being spent : in Oracle or in the Media Manager Layer. Problems related to writing back to disk/storage devices are outside the scope of this document.
A basic understanding of RMAN and Oracle is assumed.
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