DB Consistency (DPC1)

Description

This probe performs a consistency check on a particular database table. Under the hood, the mysql 'check table' command is used.

Release notes

Version 1.1.0 - General deployment
  • Improvement: Probe will now not be executed on the server if it is not defined on the SMP (M6425)
  • Dependency:
    • SNMP Agent module v3.0.0 or higher

Version 1.0 - General deployment
  • Feature: Initial version
  • Dependency:
    • SNMP Agent module v2.0+

Resource configuration interface

GUI unavailable.

Resource parameters

  • Table name: name of the table which need to be be checked. Following tables can be checked:
    • directory_entry: this table contains information related to the Internal Directory
    • attribute_state: this table contains all sorts of transient data used by the SOP API

Performance graphs

This probe does not generate any performance graphs.

Alarms

This probe can report following alarm states:

  • CRITICAL: the database table is corrupt. More precisely, the status returned by the CHECK TABLE command was not OK.

Possible causes

* A sudden power failure such that the SOP didn't get the chance to shutdown cleanly

Possible consequences

A corrupted directory_entry table may have following consequences:
    • Basic telephony that uses STARTDYNAMICAPPLICATION may not function.

A corrupted attribute_state table may have following consequences:
    • netDesktop and netConsole may not function properly.

Possible actions

  • If Database Server 2.4.0 or higher is used, just reboot the SOP
  • Contact Escaux

Copyright © Escaux SA