Alcatel-Lucent 5620 Troubleshooting Manual page 63

Alarm name, ID, type, and probable
cause(s)
Alarm name: DBFailOver
Alarm ID: 201
Type: configurationAlarm (11)
Probable cause: databasePrimaryDown
(155)
Alarm name: OldArchiveLogsDeleted
Alarm ID: 198
Type: databaseAlarm (29)
Probable cause: archivedLogsIssue (154)
Alarm name:
OracleHomeDiskSpaceBelowThreshold
Alarm ID: 399
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
Alarm name: PrimaryDatabaseWasDown
Alarm ID: 254
Type: databaseAlarm (29)
Probable cause: primaryDatabaseWasDown
(193)
Alarm name: ReinstantiateStandbyDatabase
Alarm ID: 252
Type: configurationAlarm (11)
Probable cause:
reinstantiateStandbyDatabase (191)
Alarm name:
ReinstantiateStandbyDatabaseFailed
Alarm ID: 253
Type: configurationAlarm (11)
Probable cause:
reinstantiateStandbyDatabaseFailed (192)
Alarm name:
RowThresholdConstraintViolated
Alarm ID: 286
Type: configurationAlarm (11)
Probable cause:
partialConstraintEnforcement (218)
Alarm name:
StagingDiskSpaceBelowThreshold
Alarm ID: 453
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
Alarm name:
StandbyDataFileDiskSpaceBelowThreshold
Alarm ID: 539
Type: databaseAlarm (29)
Probable cause: diskSpaceIssue (153)
(3 of 4)
Alcatel-Lucent 5620 Service Aware Manager, Release 6.1 R3
3HE 04244 AAAB Ed. 01
Alarm severity, object type,
domain, and self-clearing attribute
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: No
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: Yes
Severity: Warning
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: No
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: No
Severity: Major
Object Type (class):
SizeConstraintPolicy
Domain: db
Self-clearing alarm raised: Yes
Severity: Major
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: Yes
Severity: Critical
Object Type (class):
DatabaseManager
Domain: db
Self-clearing alarm raised: Yes
Troubleshooting Guide
3 — Troubleshooting network alarms
Additional information
—
—
—
—
—
—
The alarm is raised when the number
of records in a table exceeds the
number specified in a size constraint
policy. Size constraint policies
specify the amount of database
capacity that historical records
consume. See the 5620 SAM User
Guide for more information on size
constraint policies.
—
—
November 2008 3-25