After 12.1.0.2, when duplicate target database for standby from active database, hang will always die in restore controlfile. This error is caused by a Bug of 19664695. (Both Bug22468652 and Bug 20721271 can be attributed to Bug 19664695 .)
The solution is to set DISABLE_OOB = on in the sqlnet. ora file of ORACLE_HOME and GRID_HOME. For more information, see RMAN active duplicate hanging on restore control file (Doc ID 2073604.1)
*** RMAN active duplicate hanging on restore control file (Doc ID 2073604.1 )***
#################
#
# Applies:
#
#################
Oracle Database-Enterprise Edition-Version 12.1.0.2 and later
Information in this document applies to any platform.
SYMPTOMS
Duplicate command gets hung while restoring the control file
RMAN-08016: channel ORA_AUX_DISK_1: starting datafile backup set restore
RMAN-08169: channel ORA_AUX_DISK_1: using network backup set from service SNP
RMAN-08021: channel ORA_AUX_DISK_1: restoring control file
Source database has an inactive session in there waiting on "SQL * Net break/reset to client"
#################
#
# CAUSE
#
#################
BUG 20721271 DUPLICATE FOR STANDBY FROM ACTIVE DATABASE HANGS WHILE RESTORING CONTROL FILE
This bug is has been marked as a duplicate of bug 19664695.
BUG 19664695 12C rman wallet ORA-01031: INSUFFICIENT PRIVILEGES
#################
#
# SOLUTION
#
#################
At the time of this writing, bug 19664695 is open and being worked on by development.
The workaround, until a permanent fix is available, is:
1. On the specified uard (auxiliary) side, add the folowing line to the sqlnet. ora
DISABLE_OOB = on
2. Re-execute the duplicate command again
NOTE: Turning this parameter on disables the ability to send and receive "break" messages using urgent data provided by the underlying protocol. This wocould apply to all protocols used by the client.
For additional information, see:
What is DISABLE_OOB (Out Of Band Break )? (Note 373475.1)