ORA-38856: Cannot mark instance UNNAMED_INSTANCE_2 (redo thread 2) as enabled

最新推荐文章于 2022-03-08 17:20:01 发布

转载最新推荐文章于 2022-03-08 17:20:01 发布 · 621 阅读

文章标签：

#database #ORA-38856 #oracle #Oracle #UNNAMED_INSTANCE_2

ORACLE 专栏收录该内容

4 篇文章

订阅专栏

本文介绍了解决Oracle数据库中ORA-38856错误的方法。该错误通常发生在从RAC备份恢复到单实例数据库的过程中，与源数据库使用的线程数量有关。通过设置特定参数并调整数据库开启方式可以有效解决此问题。

ORA-38856: Cannot mark instance UNNAMED_INSTANCE_2 (redo thread 2) as enabled

Example:

In the example below the error Occurred while performing an open resetlogs on a 10.2.0.3 Oracle Single Instance Database
Server prior to restoring an RMAN backup of and Oracle Database. The RMAN backup was taken from a RAC Database Server
and restored to a Single Instance Box.

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

Details:

ORA-38856: cannot mark instance UNNAMED_INSTANCE_2 (redo thread 2) as enabled.

Oracle bug, 4355382 ORA-38856: FAILED TO OPEN DATABASE WITH RESETLOGS WHEN USING RAC BACKUP, exists in the
Oracle 10g release 2.0 that affects backups taken from a RAC database. The problem is related to the number of threads
used by the source database and an expectation that the cloned database must have an identical number of threads.

Solution:

1. Set the following parameter in the auxiliary init.ora file: _ no_recovery_through_resetlogs=TRUE.

2. Open the database in resetlogs mode.

3. Remove _ no_recovery_through_resetlogs=TRUE from init.ora.

4. Restart database.