Ora-38856:cannot Mark instance unnamed_instance_2 (Redo thread 2) as Enabled

During the recovery of yesterday's 11.2.0.2 for Linux database, the data files were copied from ASM to a single node machine, and the following ORA-38856 errors were reported in the resetlogs process
sql> ALTER DATABASE open Resetlogs;
ALTER DATABASE open resetlogs
*
ERROR at line 1:
Ora-38856:cannot Mark Instance unnamed_instance_2 (Redo Thread 2) as enabled
ORA-38856 is the expected error during open database Resetlogs when the set of enabled instances (Redo threads) in the Controlfile does is not match the set of enabled instances (Redo threads) in DataFile checkpoint. This is expected behavior in a normal RAC restore/recover/open resetlogs situation.

When the database is Resetlogs, it discovers that the redo threads in the control file and the redo threads of the data file rollup are inconsistent, and the problem occurs.
All and thread 2 related parameters were disabled in this recovery, and the database is still reporting an error because the database needs to read the redo information for node 2 during the exception recovery process, and it cannot be read at this time. But using _allow_resetlogs_corruption After that, it's weird to report the mistake. By querying MoS, you find a similar unpublished Bug 4355382 ora-38856:failed to OPEN DATABASE with Resetlogs when USING RAC BACKUP. Although the bug is fixed in 10.2.0.3, but in the process of abnormal recovery, in the case of risk-controllable, bold attempt to continue to use _no_recovery_through_resetlogs, the database normal resetlogs success.
can refer to: RMAN Duplicate from RAC backup fails ORA-38856 (DOC ID 334899.1)

Contact: Mobile Phone (13429648788) QQ (107644445)
Link:http://www.xifenfei.com/5521.html
Author: Xi-fei © Copyright [Article allows reprint, but must be linked to the source address, or to investigate legal liability.]