My Oracle Support Banner

AWR Interval and Retention settings Changed After RMAN Duplicate (Doc ID 1620321.1)

Last updated on OCTOBER 13, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

After doing RMAN DUPLICATE, the clone database does not have the same AWR settings as the source database.

 

 select * from DBA_HIST_WR_CONTROL;


     DBID SNAP_INTERVAL        RETENTION            TOPNSQL
---------- -------------------- -------------------- ----------
2136725841 +00000 01:00:00.0    +00008 00:00:00.0    DEFAULT  <<<<=== Changed to default.
2121095894 +00000 02:00:00.0    +00014 00:00:00.0    DEFAULT

 

Changes

 RMAN Duplicate, creates a new DBID for the clone database.

Cause

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
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.