The alarm which you have mentioned below is being raised based on the 'status' column return from the SQL.
Please execute one of the attached SQL based on the Oracle version customer is having (see pending below), on the monitored instance and send us the results.
if the monitored instance version < 10.2.0.0 than execute DBO_Archive_Logs_Storage_9_2_0_1.sql
if the monitored instance version >= 10.2.0.0 than execute DBO_Archive_Logs_Storage_10_2_0_0.sqlThe attachment is a zip file, which contains the 2 scripts.
In this customer example we found the database was in noarchive mode.
From the information provided, the status of the archive is ERROR, so the alarm is as expected. The alarm checks if the status is either FULL,DISABLED or ERROR and if it is the alarm raises.
The suggestion is to fix this archive destination (Archives are not being created there, the only reason the database does not hang is because the archive destination is marked optional, so I assume he has another archive marked mandatory).
If the alarm still raises when the status becomes VALID, please let us know. We will need to review this further internally with
The workaround for this customer was to set all Log_archive_dest_x to '' in the instance then it fixes the issue