RMAN-06059: expected archived log not found

By -
Issue:

RMAN-03002: failure of backup command at 06/22/2017 20:01:47
RMAN-06059: expected archived log not found, loss of archived log compromises recoverability
ORA-19625: error identifying file +SID_ARCH/sid/archivelog/2017_06_17/thread_2_seq_316.11811.946933225
ORA-17503: ksfdopn:2 Failed to open file +SID_ARCH/sid/archivelog/2017_06_17/thread_2_seq_316.11811.946933225
ORA-15012: ASM file '+SID_ARCH/sid/archivelog/2017_06_17/thread_2_seq_316.11811.946933225' does not exist

Cause:

Here during backup of archive logs via RMAN, RMAN try to backup the archive log with sequence 316 thread 2, but actually RMAN can not backup it as this log file does not exist physically there.

So whenever RMAN tries to back it up, it fails hence backup of archive log via RMAN stucks.

Solution:

Go to RMAN:

rman target /

crosscheck archivelog all;

This will mark physically not present file as expired in control file .
Now try to backup the archive log, it will run smoothly.

Best Wishes,
Nikhil Kumar.

Comments

Post a Comment

Popular posts from this blog

TNS-12541 TNS-12560 TNS-00511 TNS:protocol adapter error No listener

By -
Oracle Listener does not start with errors:  TNS-12541: TNS:no listener TNS-12560, TNS-00511, Linux Error: 2: No such file or directory, The listener supports no services euls25002.sgp.st.com:oraSID 51> ps -ef | grep -i tns root       330     2  0 Jul19 ?        00:00:00 [netns] oraSID   17512     1  0 Jul20 ?        00:01:25 /oracleSID/SID/121/bin/tnslsnr LISTENER_SID -inherit oraSID   56223 56131  0 08:02 pts/1    00:00:00 grep --color=auto -i tns euls25002.sgp.st.com:oraSID 52> lsnrctl status LISTENER_SID LSNRCTL for Linux: Version 12.1.0.2.0 - Production on 25-SEP-2017 08:02:19 Copyright (c) 1991, 2014, Oracle.  All rights reserved. Connecting to (ADDRESS=(PROTOCOL=IPC)(KEY=SID.WORLD)) TNS-12541: TNS:no listener  TNS-12560: TNS:protocol adapter error   TNS-00511: No listener    Linux Error: 2: No such file or directory ...
Read more

How to set the root password after creating instance on oracle cloud

By -
How to set the root password after creating instance on oracle cloud? since you have created instance on oracle cloud, it requires you private .ppk key file to login from putty you can login on your instance by directly providing that private key. and on Linux/Unix defult user is "opc". since during creation of instance it  will not ask you for  root password. You dont need any password to connect to root. to connect to root type below command as opc user. [opc@sts ~]$ sudo su [root@sts opc]# by this you will login as root. Now change your password [root@sts opc]# passwd Changing password for user root. New password: Retype new password: passwd: all authentication tokens updated successfully. [root@sts opc]# All done. Thanks & Regards Nikhil Kumar.
Read more
By -
How to kill IMPDP/EXPDP job: nohup impdp \"/ as sysdba\" directory=PUMP dumpfile=FULL_EXPORT.dmp logfile=FULL_IMPORT.log & check import process from database: sqlplus / as sysdba SQL*Plus: Release 12.1.0.2.0 Production on Thu Mar 21 10:01:05 2019 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, OLAP, Advanced Analytics and Real Application Testing options SQL> select JOB_NAME,state from dba_datapump_jobs; JOB_NAME STATE ------------------------------ ------------------------------ SYS_IMPORT_FULL_02 EXECUTING SYS_IMPORT_SCHEMA_02 NOT RUNNING SYS_IMPORT_SCHEMA_01 NOT RUNNING SYS_IMPORT_FULL_01 NOT RUNNING SYS_IMPORT_SCHEMA_03 NOT RUNNING exit You can see that IMPORT process is run with SYS_IMPORT_FULL_02 EXECUTING name like above. We can attach or connect to this process like following: impdp \"/ as sysdba\" attach=SYS_IMPORT_FULL_02 check st...
Read more