Overview

Introduction

AdminCenter for DBA is a graphical tool that helps DBAs manage Altibase more easily and quickly. AdminCenter version 2.1.0.0 focuses on database monitoring functionality. Additional features will be provided incrementally.

The major benefits of this tool are:

  1. DBAs can investigate the current or historical state of a target database or operating system that is being monitored.
  2. DBAs can manage so-called "Profile Jobs", which collect state information from databases or operating systems and store the collected data periodically and automatically.

For a better understanding of this tool, please read the following 'Terminology' and 'How the Monitoring System Works' sections.

Terminologies

Monitor

An AdminCenter for DBA monitor is a graphical interface that depicts the state of a database or OS. The monitor is very simple to use: once connected to a database, just click any monitor menu in the left tree menu, and then the information about the selected monitor will show up in the right panel.

AdminCenter for DBA provides two types of monitors: a snapshot monitor and a history monitor. The snapshot monitor enables observation of the current state of a database or OS. In contrast, the history monitor is for inquiring about the state of a database or OS in the past.

Profile Job

A Profile Job is a job unit that captures monitoring data and stores them in consistent storage, called MR ("Managed Repository"), periodically and automatically. Using profile jobs enables DBAs to trace past problems and analyze database usage patterns based on the collected data.

The Altibase monitoring system provides two types of profile jobs: DB Profile Jobs and OS Profile Jobs. DB Profile Jobs are user-defined Altibase profile jobs. DBAs can add new DB Profile Jobs based on their own SQL statements. Additionally, DBAs can manage working DB Profile Jobs, for example, they can issue commands to edit/remove/start/pause them. Conversely, OS Profile Jobs are predefined profile job pertaining to the OS. So, DBAs can only edit/start/pause them.

How monitoring system works

Four components are required for monitoring.

  1. An Altibase instance (aka AI) to be monitored.
  2. AdminCenter for DBA as a monitor viewer and controller.
  3. Altibase Monitoring Daemon (aka AMOND) as a monitoring agent.
  4. Managed Repository (aka MR) as storage for historical data.

Let's take a look at the following simple scenario to see how it works.

At first, the DBA starts the AI and MR. Then, AMOND starts to collect data about the AI and OS, and stores them in the MR. On the client side, the DBA executes AdminCenter to observe the state of the AI and OS. In the case of a snapshot monitor, it sends the requested current data to the database or AMOND, and then describes the state based on the received data. In the case of a history monitor, it sends the requested historical data to MR. Then it prints out the received data from MR in tabular or chart format for ease of analysis.