Alcatel-Lucent 5620 - Page 71

3 — Troubleshooting using network alarms
Alcatel-Lucent 5620 Service Aware Manager, Release 3-29
3HE 05723 TQZZA Edition 01 Troubleshooting Guide
Name:
DatabaseRedundancyRealTimeApplyFailure
Type: configurationAlarm (11)
Probable cause:
DatabaseRedundancyRealTimeApplyFailure
(227)
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
The alarm is raised when database
redundancy falls out of real-time
apply transfer mode, which means
that the primary database
transactions are not immediately
replicated to the standby database.
The alarm clears when the database
is operating in real-time apply mode.
Name: DataFileDiskSpaceBelowThreshold
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
The alarm is raised when the primary
or standalone database data file disk
space threshold specified in the
nms-server.xml file is reached.
Name: DatafileSizeAboveThreshold
Type: databaseAlarm (29)
Probable cause: HighNumberOfRecords
(526)
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
The alarm is raised when a
tablespace data file size exceeds 85
percent of 32 Gbytes. This may
indicate that the number of stored
NE backups is too high.
Name: DBFailOver
Type: configurationAlarm (11)
Probable cause: databasePrimaryDown
(155)
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
The alarm is raised when a database
failover occurs. A standby database
reinstantiation is required. The
alarm clears when the standby
database is online.
Name:
InstallDirectoryDiskSpaceBelowThreshold
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
The alarm is raised when the primary
or standalone database installation
disk space threshold specified in the
nms-server.xml file is reached.
Name: OldArchiveLogsDeleted
Type: databaseAlarm (29)
Probable cause: archivedLogsIssue (154)
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): No
The alarm is raised when the
5620 SAM deletes the applied archive
logs because database disk space is
low. In a standalone deployment, the
5620 SAM deletes all archive logs. In
a redundant deployment, the
5620 SAM deletes the applied archive
logs, and can raise the alarm against
the primary or standby database.
Name:
OracleHomeDiskSpaceBelowThreshold
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
The alarm is raised when the primary
or standalone database Oracle disk
space threshold specified in the
nms-server.xml file is reached.
Name: PrimaryDatabaseDown
Type: databaseAlarm (29)
Probable cause: primaryDatabaseDown
(527)
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Implicitly cleared (self-clearing): Yes
The alarm is raised when the primary
5620 SAM database is down for at
least one poll. The alarm is not
persisted in the database or stored in
the alarm history; when the database
returns to service, the
PrimaryDatabaseWasDown alarm is
raised.
Alarm Attributes Additional information
(3 of 5)
Aug 2010
AAAD
8.0 R4