My Oracle Support Banner

Not able to open Snapshot Standby Database - Errors: ORA-00322 ORA-00313 ORA-17503 (Doc ID 2197072.1)

Last updated on OCTOBER 23, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.2 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data
from the Oracle sample schema(s), Public Documentation delivered with an Oracle database product or other training material.
Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.





1. Taken the backup when the database was in physical standby.

2. Later, physical standby database was converted to snapshot standby and it was in read/write mode.

3. Using the standby database backup, rman duplicate was tried to clone another db on the same server where snapshot standby was in read/write mode.

4. Duplicate went successful, however it overwritten the ORL of snapshot standby which was in read/write mode at that time.

5. Because of this, snapshot standby went down and while opening the snapshot standby database thrown the below error:

SQL> alter database open;
alter database open
ERROR at line 1:
ORA-00322: log 31 of thread 2 is not current copy
ORA-00312: online log 31 thread 2: '+DATA/orcldr/onlinelog/group_31.846.924526077'


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

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