Alcatel-Lucent 5620 Troubleshooting Manual page 62

3 — Troubleshooting network alarms
Alarm name, ID, type, and probable
cause(s)
Alarm name:
DatabaseArchivedLogNotApplied
Alarm ID: 205
Type: configurationAlarm (11)
Probable cause:
databaseArchivedLogNotApplied (159)
Alarm name: DatabaseBackupFailed
Alarm ID: 136
Type: configurationAlarm (11)
Probable cause: databaseBackupFailure
(109)
Alarm name: DatabaseRedundancyFailure
Alarm ID: 246
Type: configurationAlarm (11)
Probable cause:
DatabaseRedundancyFailure (184)
Alarm name:
DatabaseRedundancyOutOfSync
Alarm ID: 302
Type: configurationAlarm (11)
Probable cause:
DatabaseRedundancyOutOfSync (233)
Alarm name:
DatabaseRedundancyRealTimeApplyFailure
Alarm ID: 296
Type: configurationAlarm (11)
Probable cause:
DatabaseRedundancyRealTimeApplyFailure
(227)
Alarm name:
DataFileDiskSpaceBelowThreshold
Alarm ID: 196
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
(2 of 4)
3-24
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: No
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: No
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: No
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: Yes
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: No
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: Yes
November 2008 Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
Additional information
—
The backup file could not be created
because of, for example, a lack of
disk space or insufficient
permissions.
The alarm is raised when a problem
is detected with the standby
database. Possible problem states
include:
•
down
•
out of synchronization
•
old primary due to a failover
•
not in managed recovery mode
When the standby database is online
and the former primary becomes the
standby, you can manually clear the
alarm.
The alarm is raised in a redundant
5620 SAM deployment each time the
primary 5620 SAM server polls the
primary and standby databases and
detects a difference in the primary
and standby database archive log
sequence numbers that is greater
than one. The alarm may indicate
that the primary database is not
sending archive logs to the standby
quickly enough, or that the standby
database is not able to keep up with
the rate at which the primary is
sending the archive logs.
The alarm is not raised in a
standalone 5620 SAM deployment.
The alarm is raised when database
redundancy falls out of real-time
apply transfer mode, which means
that primary database transactions
are not immediately replicated to
the standby database. The alarm is
cleared when the database is again
operating in real-time apply mode.
One or more 5620 SAM database file
system thresholds specified in the
nms-server.xml file have been
reached.
Troubleshooting Guide 3HE 04244 AAAB Ed. 01