Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Announcement Support for this product will end on December 22, 2025. To monitor Oracle databases, we recommend that you use PATROL for Oracle Enterprise Database.

Standby Alert Log (StandbyAlertLog)


The StandbyAlertLog monitors any text from the Oracle standby alert log file using the alreader executable utility.

For any text that you want to be notified about, you can define filters to include or exclude specific ORA-XXXX errors or user defined text. By default, there are no pre-defined filters settings, and the alert log does not report any errors if no filter is defined.

The parameter reports the following values:

Value

Description

0

The data in the Oracle standby alert log file was successfully read and contents do not match the user defined filters.

1

The Oracle standby alert log file is not accessible.

2

The alreader utility failed to start or failed to register the Oracle standby alert log file.

3

The data Oracle standby alert log file was successfully read and it contains matches to the user defined filters.

The annotation in the StandbyAlertLog parameter shows the results for values 1, 2, and 3.

The first time the alreader utility runs after discovery, it initializes the parameter value by setting it to zero. Also, the parameter does not report any value if the alert log file is empty or does not exist.

Note

The following SQL query is used to find the alert log file:

select * from v$diag_info where NAME in ('Diag Trace')

The StandbyAlertLog parameter returns a "StandBy alert log file not found" message if it does not find the alert log file. This means that the StandbyAlertLog parameter is offline.

BMC PATROL properties

Attribute

Default value

Application class

ORACLE_STANDBY_DG_INSTANCE

Command type

not applicable

Platform

All

Icon style

StopLight

Unit

None

Border range

0-3

Alarm1 range

1-2 warn

Alarm2 range

3-3 alarm

Scheduling(poll time)

10 min

Active at installation

Yes

Parameter type

Standard

Value set by

Parameter collects own value

Annotation

Complete text for all entries that contain ORA-XXXX errors or user defined text.

External File

Extract alert log file location based on the following SQL query:

select * from v$diag_info where NAME in ('Diag Trace')

BMC ProactiveNet Performance Management properties

Property

Default value

Monitor type

Oracle Database Standby DG  Instance

Key Performance Indicator

Yes

Monitor for abnormalities

Yes

Graph by default

Yes

Availability

No

Response time

No

Normal distribution

Yes

Statistical

Yes

alreader

The alreader (alreader.exe on Windows) is a utility for scanning Oracle Alert log files. Oracle alert log files are used by Oracle to record change events within the Oracle system. The KM uses these files as source of data for monitoring. This utility is a tool used for data collection. The utility can scan one or more alert log files according to your needs. Every change in the log file is recorded by the alreader utility and the new changes (data lines) are sent to the KM.

In remote monitoring, the alreader utility is deployed locally on the host where the Oracle database is installed. The utility sends the new changes (data lines) to the remote PATROL Agent located on a different host over SSH.

After the utility initializes the StandbyAlertLog parameter, the parameter scans 1 MB of data in the alert log every 600 seconds (10 minutes) for new entries

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*