Alcatel-Lucent 5620 Troubleshooting Manual page 70

3 — Troubleshooting using network alarms
Alarm
Name: DatabaseBackupFailed
Type: configurationAlarm (11)
Probable cause: databaseBackupFailure
(109)
Name: DatabaseBackupInvalidConfig
Type: configurationAlarm (11)
Probable cause: InvalidbBackupConfigration
(829)
Name: DatabaseBackupRsyncFailed
Type: databaseAlarm (29)
Probable cause:
databaseBackupFileRsyncFailed (525)
Name: DatabaseRedundancyArchiveGap
Type: configurationAlarm (11)
Probable cause:
DatabaseRedundancyArchiveGap (454)
Name: DatabaseRedundancyFailure
Type: configurationAlarm (11)
Probable cause:
DatabaseRedundancyFailure (184)
Name: DatabaseRedundancyOutOfSync
Type: configurationAlarm (11)
Probable cause:
DatabaseRedundancyOutOfSync (233)
(2 of 5)
3-28
Attributes
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
Alcatel-Lucent 5620 Service Aware Manager, Release
Aug 2010
Troubleshooting Guide
Additional information
The alarm is raised when the
database backup files cannot be
created because of, for example, a
lack of disk space or insufficient file
permissions.
The alarm is raised when the
scheduled backup destination is
empty.
The alarm is raised when one or more
database backup files cannot be
copied to the standby database
station.
The alarm is raised when the primary
5620 SAM main server detects an
archive log gap. An archive log gap
occurs when a number of archive logs
cannot be applied to the standby
database. The alarm may indicate
that the primary database is out of
archive log disk space, the standby
database has been down for too long,
or the standby database is not able
to process the archive logs at the
rate that the primary database sends
them. The alarm clears after a
standby database reinstantiation,
which corrects the archive log
gap.The alarm is raised only in a
redundant 5620 SAM system.
The alarm is raised when the
5620 SAM detects a standby database
problem, for example, the database
is down or not in managed recovery
mode. The alarm clears when the
standby database is functional.The
alarm is raised only in a redundant
5620 SAM system.
The alarm is raised when 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 process the
archive logs at the rate that the
primary sends them.The alarm is
raised only in a redundant 5620 SAM
system.
3HE 05723 AAAD TQZZA Edition 01
8.0 R4