ORA-16038: log N sequence# M cannot be archived
OracleWhat does it mean?
Oracle cannot archive an online redo log file and therefore cannot reuse that log group. When archiving is stuck in ARCHIVELOG mode, the database may stop accepting new transactions and hang.
Why does it happen?
Usually the archive log destination or the Fast Recovery Area (FRA) is full; disk space has run out; the archive destination is unreachable; or there is a permission/mount problem. Often seen together with ORA-19809 (limit exceeded for recovery files) or ORA-00312.
How to fix it
Free space in the archive destination/FRA: back up old archived logs with RMAN to a destination outside the FRA and delete them (DELETE ARCHIVELOG ALL COMPLETED BEFORE ...; with Data Guard, do not delete archived logs not yet shipped/applied on the standby), or increase db_recovery_file_dest_size. Check destination status: ARCHIVE LOG LIST; and SELECT dest_name, status, error FROM v$archive_dest WHERE status != 'INACTIVE'; Once the problem is fixed, archiving resumes where it left off.
More from this engine
- ORA-02449unique/primary keys in table referenced by foreign keys
- ORA-01950no privileges on tablespace 'name'
- ORA-01110data file N: 'path'
- ORA-19809limit exceeded for recovery files
- ORA-00376file N cannot be read at this time
- ORA-12520TNS:listener could not find available handler for requested type of server
- ORA-28001the password has expired