My Oracle Support Banner

EM 13c: DB Archiver Hung Alert Wrongly Interpreting Archive Hung Errors ORA-16038 (Doc ID 2896704.1)

Last updated on OCTOBER 03, 2022

Applies to:

Enterprise Manager for Oracle Database - Version 13.5.1.0.0 and later
Information in this document applies to any platform.

Symptoms

In Enterprise Manager (EM) Cloud Control, DB Archiver Hung Alert Wrongly Interpreting Archive Hung Errors ORA-16038

Alert_<SID>.log

2021-02-24T03:00:44.753734-05:00
Errors in file
/app/oracle/diag/rdbms/<DB_Name>/<DB_Name>/trace/<DB_Name>_tt02_26548.trc:
ORA-16038: log 1 sequence# 40717 cannot be archived
2021-02-24T03:00:44.754006-05:00
Errors in file
/app/oracle/diag/rdbms/<DB_Name>/<DB_Name>/trace/<DB_NAME>_tt02_26548.trc:
ORA-16038: log 1 sequence# 40717 cannot be archived

Example:

Target type=Database Instance
Target name=<DB_Name>
Categories=Fault
Message=The archiver hung at time/line number: Wed Aug 25 19:30:54 2021/4146068.
Severity=Critical
Event reported time=Aug 25, 2021 7:30:54 PM EDT
Associated Incident Id=112236
Associated Incident Status=New
Associated Incident Owner=
Associated Incident Acknowledged By Owner=No
Associated Incident Priority=None
Associated Incident Escalation Level=0
Event Type=Metric Alert
Event name=db_alert_log:archiveHungErrStack
Total Occurrences=99
Occurrences in this event=1
First Occurred in this event=Aug 25, 2021 7:30:54 PM EDT
Last Occurred in this event=Aug 25, 2021 7:30:54 PM EDT
Metric Group=DB Alert Log
Metric=Archiver Hung Alert Log Error
Metric value=ORA-16038: log 4 sequence# 320672 cannot be archived~ORA-19502: write error on file "", block number (block size=)~ORA-00312: online log 4 thread

 

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
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.