Steps to reproduce:

1. In oracle create archivelog destination with alternate status (see https://docs.oracle.com/en/database/oracle/oracle-database/19/sbydb/using-ALTERNATE-attribute-to-configure-alternate-destinations.html#GUID-7055337B-A852-402F-8B2F-2E119CBE6437 )

Result:

Zabbix evaluates the destination as unavailable (or better doesn't evaluate it as available) and triggers Archivelog '{#DEST_NAME}': Log Archive is not valid trigger
Expected:
The destination is evaulated as valid and available.

The change seems to be quite simple in src/[go|https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/src/go?at=c9640dbb98063f509f87f9f1cbe3cc431bb84f94]/[plugins|https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/src/go/plugins?at=c9640dbb98063f509f87f9f1cbe3cc431bb84f94]/[oracle|https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/src/go/plugins/oracle?at=c9640dbb98063f509f87f9f1cbe3cc431bb84f94]/handler_archive.go from

    row, err := conn.QueryRow(ctx, `
        SELECT
            JSON_OBJECT('available' VALUE COUNT)
        FROM
            V$LOG    
        WHERE 
            STATUS IN ('INACTIVE', 'UNUSED')
    `)

to

    row, err := conn.QueryRow(ctx, `
        SELECT
            JSON_OBJECT('available' VALUE COUNT)
        FROM
            V$LOG    
        WHERE 
            STATUS IN ('INACTIVE', 'UNUSED', 'ALTERNATE')
    `)