RMAN Duplicate Failed - ORA - 38862: Flashback database logs are in use.

Problem Statement:

While doing a RMAN based duplication for database running on version 19.10 encountered a strange error "ORA - 38862: Flashback database logs are in use". Though at first instance one would think about why would the database  be using flashback logs as it's a RMAN based restore. 


Error Stack:

RMAN-05501: aborting duplication of target database

RMAN-03015: error occurred in stored script Memory Script

RMAN-03009: failure of sql command on clone_default channel at <timestamp>

RMAN-11003: failure during parse/execution of SQL statement: alter database flashback off

ORA - 38862: Flashback database logs are in use


Command:

run  {

                allocate auxiliary channel ch1 device type disk;

                allocate auxiliary channel ch1 device type disk;

                allocate auxiliary channel ch1 device type disk;

                allocate auxiliary channel ch1 device type disk;

                duplicate database <source db name> to <target db name>

                until scn <scn number> nofilenamecheck;

        }

It seems RMAN is trying to disable the flashback of the database while restoring and it thinks some of the flashback logs are still in use and causing refresh to fail. Similar RMAN duplication on the same type of version and configuration gives no error. As in luck found a document on Oracle Support that talks about the same error (Doc ID 2418803.1).

This problem arises when we have db_recovery_file_dest and db_flashback_retention_target parameter set which is not very uncommon. 


Solution: 

Disable the flashback retention target during the restore.

Step1: set log_archive_dest_1 to FRA location.

Step2: set db_flashback_retention_target=0

Step3: unset db_recovery_file_dest

    alter system set db_recovery_file_dest='' scope=both sid='*';


Even though we have a solution it makes me feel it's very common to have these parameters set and what could be the actual reason for RMAN thinking this way. I will continue my investigation to identify the actual reason if any, meanwhile this workaround works well.


References:

Oracle Support Document ID: 2418803.1

Comments

Post a Comment

Popular posts from this blog

How to Solve - "WAIT FOR EMON PROCESS NTFNS"

Event Monitor Process in short called as EMON is generally used by oracle to send notification. Often applications uses Database Change Notification process also called as DBCN to be aware of changes in the database, based on these notifications they take further actions. Often clients subscribe to the database and notifications are send as callback to them. In some cases you will notice database sessions are showing wait event "WAIT FOR EMON PROCESS NTFNS" and it can even make your database un-responsive. One observation can be these processes are taking more CPU (may not in be in all cases). As stated EMON process deals with database notification and it's spawn and gets down itself and Administrators have no control on theses processes. Anyone can go through oracle documents to read more EMON functioning process.  EMON uses oracle advanced queues and database queue notifications into them and EMON process these notifications to clients based on their subscriptions. In s
Read more

Query Regression - "OR" Transformation Oracle 19c

Recently while upgrading Oracle Database from version 12.1 to 19.10 found there were couple of queries which was running slow post upgrade. Usually these type of behavior is seen while upgrading to newer version and oracle provide various ways to fix them. The difference between good and bad plan was an introduction of  "MERGE JOIN CARTESIAN" (aka MJC) and that's in where regressed query in 19c taking most of the time. MJC sometimes works for queries but in this case it was clearly not helping.  We had following options here:     1. Copy the profile from 12c to 19c database and it worked, but the problem was not just to specific query but with many similar query. This means profile option is not very attractive in this case.     2. We also tried running query with OFE 12.1 to use the same optimizer features as previous version and query behaves well. Though this option can't be placed as we need to use 19c OFE and can be placed only for testing purpose.           alte
Read more

ORA - 12537: TNS: connection closed

Often when active clone to be done to create a new environment, we land up into couple of issues. I will discuss about one issues during this process. Action : Create a new database on different machine from a source. Error : ORA - 12537: TNS: connection closed In order to duplicate the environment was using below rman log /tmp/duplicate.log connect target sys/<password>@<source tns alias> connect auxiliary sys/<password>@<target tns alias> run{ allocate channel ch1 device type disk; allocate channel ch2 device type disk; allocate channel ch3 device type disk; allocate channel ch4 device type disk; allocate auxiliary channel ax1 device type disk; allocate auxiliary channel ax2 device type disk; allocate auxiliary channel ax3 device type disk; allocate auxiliary channel ax4 device type disk; DUPLICATE TARGET DATABASE TO <TARGET_DBNAME> FROM ACTIVE DATABASE NOFILENAMECHECK; } While making connection to Auxiliary database received mentioned error ORA - 12537:
Read more