restore to shared bookmark fails ORA-00308: cannot open archived log (KBA6065)
KBA
KBA# 6065
Issue
When restoring/refreshing a self-service container from a shared bookmark the recovery can fail with:
Example:
try_manual_recovery=false
ALTER DATABASE RECOVER LOGFILE '/oracle/oradata/OGDMD003/source-archive/OGDMD004_1_176_1042539374.arc';
SQL*Plus: Release 12.1.0.2.0 Production on Tue Jun 9 08:41:45 2020
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning option
SQL> SQL> alter database recover automatic database until change 39835881078 using backup controlfile
*
ERROR at line 1:
ORA-00279: change 39835881040 generated at 06/08/2020 15:40:33 needed for
thread 1
ORA-00289: suggestion :
/oracle/oradata/OGDMD003/source-archive/OGDMD003_1_176_1042539374.arc
ORA-00280: change 39835881040 for thread 1 is in sequence #176
ORA-00278: log file
'/oracle/oradata/OGDMD003/source-archive/OGDMD003_1_176_1042539374.arc' no
longer needed for this recovery
ORA-00308: cannot open archived log
'/oracle/oradata/OGDMD003/source-archive/OGDMD003_1_176_1042539374.arc'
ORA-27037: unable to obtain file status
Linux-x86_64 Error: 2: No such file or directory
Additional information: 3
This shows that the naming conversion for the required archive logs does not match as we are running the command:
ALTER DATABASE RECOVER LOGFILE '/oracle/oradata/OGDMD003/source-archive/OGDMD004_1_176_1042539374.arc';
However we then see the file required as
/oracle/oradata/OGDMD003/source-archive/OGDMD003_1_176_1042539374.arc
Prerequisites
This issue is only seen when using self-service shared bookmarks and if the Oracle database parameter log_archive_format has been altered from the default to include SID specific details like this:
log_archive_format = "${ORACLE_SID}_%t_%s_%r.arc"
Applicable Delphix Versions
- Click here to view the versions of the Delphix engine to which this article applies
-
Major Release All Sub Releases 6.0 6.0.0.0, 6.0.1.0, 6.0.1.1, 6.0.2.0 5.3
5.3.0.0, 5.3.0.1, 5.3.0.2, 5.3.0.3, 5.3.1.0, 5.3.1.1, 5.3.1.2, 5.3.2.0, 5.3.3.0, 5.3.3.1, 5.3.4.0, 5.3.5.0 5.3.6.0, 5.3.7.0, 5.3.7.1, 5.3.8.0, 5.3.8.1, 5.3.9.0 5.2
5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1
5.1
5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0
5.0
5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1 ,5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4
4.3
4.3.1.0, 4.3.2.0, 4.3.2.1, 4.3.3.0, 4.3.4.0, 4.3.4.1, 4.3.5.0
4.2
4.2.0.0, 4.2.0.3, 4.2.1.0, 4.2.1.1, 4.2.2.0, 4.2.2.1, 4.2.3.0, 4.2.4.0 , 4.2.5.0, 4.2.5.1
4.1
4.1.0.0, 4.1.2.0, 4.1.3.0, 4.1.3.1, 4.1.3.2, 4.1.4.0, 4.1.5.0, 4.1.6.0
Resolution
Please check the Oracle parameter log_archive_format and ensure that it does not include the ORACLE_SID as part of the naming convention.
Troubleshooting
<text>
Related Articles
The following articles may provide more information or related information to this article:
- link
- link
- link