No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight V300R010C00 Maintenance Guide 08

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
ALM-505001101 Database Usage Is High

ALM-505001101 Database Usage Is High

Description

If the maintenance tool detects that the database tablespace usage is greater than the alarm generation threshold (95%), the alarm is generated. The detection period is 5 minutes. If the database tablespace usage is less than the alarm clear threshold (85%), the alarm is automatically cleared.

Attribute

Alarm ID

Alarm Severity

Alarm Type

505001101

Major

Quality of service alarm

Parameters

Name

Meaning

Server name

Name of the server for which the alarm is generated.

Server IP address

Internet Protocol (IP) address of the server for which the alarm is generated.

TablespaceName

Name of the database tablespace for which the alarm is generated.

Threshold

Threshold for generating an alarm.

Clearance threshold

Threshold for clearing an alarm.

Usage

Database tablespace usage.

Impact on the System

The operations associated with the eSight database tablespace may fail, for example, alarm information may fail to be saved to the database. This alarm may cause exceptions or eSight failures if it is not cleared in a timely manner.

Possible Causes

  • The alarm generation threshold for the database tablespace usage of the eSight server is set improperly.
  • The eSight receives a large number of alarms or events within a short period of time.
  • The eSight records a large number of logs within a short period of time.
  • The database tablespace is not released in a timely manner after the data in the Oracle database is exported or dumped.

Procedure

  1. Check whether the alarm generation threshold for the database tablespace usage of the eSight server is set improperly.

    1. Contact the administrator to check whether the alarm generation threshold for the database tablespace usage of the server is set improperly.
      • If yes, ask the administrator to handle it. After the administrator processes it, go to Step 1.2. If you cannot wait for the administrator to process it, go to Step 5.
      • If no, go to Step 2.
    2. Wait five minutes. In the current alarm list, check whether the alarm is cleared.
      • If yes, the alarm handling process is complete.
      • If no, go to Step 2.

  2. Check whether a large number of alarms or events are reported within a short period of time.

    1. Check whether TablespaceName in the alarm information is the alarm database fmdb.
    2. Check whether a large number of alarms are reported within a short period of time.
      1. Choose Fault > Current Alarms from the main menu.
      2. On Current Alarms page, check whether a large number of events (more than 300 events per second) are reported within a short period of time.
    3. Handle these alarms.
      • Set alarm masking rules to mask these alarms, see Set alarm masking rules. Choose Fault > Alarm Settings from the main menu. In the navigation tree on the left, choose Masking Rule.
      • Choose System > System Settings > Common Parameters from the main menu.
      • In the navigation tree in the left pane, choose Alarm Database Dump. On the Alarm Database Dump page, perform scheduled tasks for alarm overflow dump, and find the cause for device alarm generation.
    4. Wait five minutes. In the current alarm list, check whether the alarm is cleared.
      • If yes, the alarm handling process is complete.
      • If no, go to Step 3.

  3. Check whether a large number of logs are reported within a short period of time.

    1. Check whether TablespaceName in the alarm information is the alarm database omssm.
    2. Generally, only a large number of system logs are reported within a short period of time. check whether a large number of system logs are reported.
      1. Choose System > System Management > Log Management from the main menu.
      2. In the navigation tree in the left pane, choose System Logs. On the System Logs page, check whether a large number of system logs are reported (more than 300 logs are reported per second.)
    3. Handle these logs.
      1. Choose System > System Settings > Common Parameters from the main menu.
      2. In the navigation tree in the left pane, choose Log Database Dump. On the Log Database Dump page, perform scheduled tasks for system log dump, and find the cause for system log generation.
    4. Wait five minutes. In the current alarm list, check whether the alarm is cleared.
    • If yes, the alarm handling process is complete.
    • If no, go to Step 4.

  4. Check whether it is the Oracle database that does not release the database tablespace after data is exported or dumped from the database.

    1. Check whether it is the Oracle database based on the TablespaceName field in the alarm location information.
      • If yes, connect to the database as the administrator and run the following command to release the database tablespace:

        # alter table <table_name> enable row movement

        # alter table <table_name> shrink space

      NOTE:

      In the command, replace <table_name> with the actual database tablespace name.

      After the database tablespace is released, go to Step 4.2.

    2. Wait five minutes. In the current alarm list, check whether the alarm is cleared.
      • If yes, the alarm handling process is complete.
      • If no, go to Step 5.

  5. Collect the information about alarm handling, and contact the technical support personnel.

Clearing

When the fault is eliminated, the system will auto-clear the alarm. Manual clearing is not required.

The following situations cause failures in automatically clearing alarms. Instead, they need to be cleared manually.

  • The name and IP address of the host for which this alarm is generated are changed.
  • The server that generates the alarm is not monitored.
  • Active/standby switchover occurs in a high-availability system.

Related Information

None.

Translation
Download
Updated: 2019-08-03

Document ID: EDOC1100044373

Views: 27011

Downloads: 90

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next