Tuesday, July 24, 2018

ORA-16014: log 1 sequence# 1221 not archived, no available destinations

Today in my Primary database I was dong some log switching. It took a bit long to complete the log switch and so I decided to look into the alert log. I could able to see some issue been recorded in the alert log. Below is the issue.

Issue:





Alert log:
ARC1: Error 19504 Creating archive log file to '+DATA/vis/datafile/archive/1_1221_970193294.dbf'
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance VIS - Archival Error
ORA-16038: log 1 sequence# 1221 cannot be archived
ORA-19504: failed to create file ""
ORA-00312: online log 1 thread 1: '+DATA/vis/logfile/log01b.dbf'
ORA-00312: online log 1 thread 1: '+DATA/vis/logfile/log01a.dbf'
Archiver process freed from errors. No longer stopped
Tue Jul 24 19:17:42 2018
ARC3: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance VIS - Archival Error
ORA-16014: log 1 sequence# 1221 not archived, no available destinations
ORA-00312: online log 1 thread 1: '+DATA/vis/logfile/log01b.dbf'
ORA-00312: online log 1 thread 1: '+DATA/vis/logfile/log01a.dbf'
Tue Jul 24 19:23:06 2018
ARC3: Error 19504 Creating archive log file to '+DATA/vis/datafile/archive/1_1221_970193294.dbf'
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance VIS - Archival Error
ORA-16038: log 1 sequence# 1221 cannot be archived
ORA-19504: failed to create file ""
ORA-00312: online log 1 thread 1: '+DATA/vis/logfile/log01b.dbf'
ORA-00312: online log 1 thread 1: '+DATA/vis/logfile/log01a.dbf'
Tue Jul 24 19:23:06 2018
ARC0: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance VIS - Archival Error
ORA-16014: log 1 sequence# 1221 not archived, no available destinations
ORA-00312: online log 1 thread 1: '+DATA/vis/logfile/log01b.dbf'
ORA-00312: online log 1 thread 1: '+DATA/vis/logfile/log01a.dbf'
Tue Jul 24 19:27:14 2018
Incremental checkpoint up to RBA [0x4c6.50f.0], current log tail at RBA [0x4c6.56f.0]
Tue Jul 24 19:28:06 2018
ARC1: Error 19504 Creating archive log file to '+DATA/vis/datafile/archive/1_1221_970193294.dbf'
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance VIS - Archival Error
ORA-16038: log 1 sequence# 1221 cannot be archived
ORA-19504: failed to create file ""
ORA-00312: online log 1 thread 1: '+DATA/vis/logfile/log01b.dbf'
ORA-00312: online log 1 thread 1: '+DATA/vis/logfile/log01a.dbf'
Tue Jul 24 19:28:07 2018
ARC3: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARCH: Archival stopped, error occurred. Will continue retrying

Here in my case log sequence 1221 cannot be archived and the same belongs to the archive group 1.

Reason :
One of the online redo is corrupted and so archiver cannot archive that to the disk. Now to bring back the database to normal state, need to clear the corrupted redo log.

Solution:
Clear the corrupted redo log



Now the database will start normally, but we can not use those old logs. Now need to take a full backup in-order to have proper and valid backup.

NOTE : Since I faced this issue a few times, I tried different options. The above is not the only solution to overcome this issue. For me one time I faced this issue and simply I checked the archive mount point usage and found only 32 MB is available as free space. My log size 150 MB. So this was the reason for the issue. Archiver is trying to write the archived log in the archive destination and due to in-adequate amount of space it waits and registered the above issue in alert log file. After clearing up the unwanted old log files I could able to make some free space and the archival process is completed normally. So always try to find the root cause for the issue and take the action/workaround accordingly.
****************************நன்றி****************************

No comments:

Post a Comment

IAS Cache initialization failed

 Today I faced an Issue in R12.2 instance. The solution I followed to overcome the issue is very simple, but they are more than one solution...