Possible Cause of ORA-00354 and ORA-00353 -OR- ARC0: Error 19510 closing archivelog file
(Doc ID 444685.1)
Last updated on FEBRUARY 02, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 8.1.7.4 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Following errors appear in the Alert Log:
ORA-00354: corrupt redo log block header
ORA-00353: log corruption near block %s change %s time %s
-- OR --
ARC0: Error 19510 closing archivelog file
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance %s - Archival Error
ARCH: Connecting to console port...
Backup script is deleting or moving files from LOG_ARCHIVE_DEST directory
LOG_ARCHIVE_DEST directory is not full
ORA-16014: log %n sequence# %n not archived, no available destinations
ARC0: Failed to archive log# %n seq# %n
ARC0: Archiving not possible: error count exceeded
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |