Working with Profile Jobs
This chapter is intended to help DBAs manipulate Profile Jobs so that they can manage target Altibase instances more efficiently.
Introduction
As stated in the Overview chapter, a Profile Job is a job unit for collecting data from a database or OS and storing them in a target MR periodically and automatically. DBAs can thus analyze the data collected in the MR using history monitors.
Profile Jobs are managed not by AdminCenter for DBA but by AMOND. AdminCenter for DBA doesn't even store any information about Profile Jobs. Strictly speaking, AdminCenter for DBA is a remote controller for Profile Jobs.
A Profile Job consists of following elements.
- Job Name: The unique name of the Profile Job.
- Activated: A flag to show whether it has been activated by a DBA or not.
- Status: The state of a profile job. Even if activated, it may not work due to external problems such as failure to connect to Altibase or an MR.
- Cycle Time: The profiling interval, in seconds.
- Remove Older Than: The amount of time that collected data will be kept in the MR, in days.
- Text
- DB Profile Job: a SELECT SQL statement ends with semicolon.
- OS Profile Job: a Profile Job's description.
Depending on the monitoring target, Profile Jobs can be categorized into DB Profile Job and OS Profile Job.
DB Profile Job: User-defined Profile Job
A DB Profile Job is a profile job for Altibase that is based on a SELECT SQL statement. Its purpose is to realize flexible database monitoring, so DBAs can create their own DB Profile Jobs.
When the "DB Profile Job" item in the "AMOND" folder is clicked, DBAs can view the list of DB Profile Jobs in tabular format.
Add
When the DBA opens a context menu by clicking the right mouse button in the DB Profile Job control screen, a menu group will show up.
After choosing the "Add Profile Job" item, a small dialog box will appear to add a DB Profile Job.
- Job Name: The unique name of the Profile Job.
- Activated: The flag to activate.
- Cycle Time: The profiling interval, in seconds.
- Remove Older Than: The duration that collected data will be kept in the MR, in days.
- Text: a SELECT SQL statement ends with a semicolon.
DBAs should keep in mind that column names must be explicitly given.
In other words, "*", which signifies all columns in select statements, is not allowed.
After filling out the above items and clicking "OK", execution will start.
Remove
After selecting one or more of the DB Profile Jobs to be removed, execute "Remove Profile Job(s)" in the context menu.
Edit
After selecting a DB Profile Job to be edited, execute "Edit Profile Job" in the context menu. Only "Cycle Time" and "Remove Older Than" are editable.
Start/Stop
After selecting one or more DB Profile Jobs to be started or stopped, execute "Start/Stop" in the context menu.
Import/Export Profile Jobs
For improved portability of Profile Jobs, AdminCenter for DBA allows Profile Jobs to be imported and exported in XML format.
This means that after a DBA has created his/her own DB Profile Jobs pertaining to an Altibase instance, he/she can use them with other Altibase instances.
Export Profile Job
After selecting one or more DB Profile Jobs for export, execute "Export Profile Job(s)" in the context menu.
A file dialog will appear for saving the selected DB Profile Jobs.
After entering the name of file, click the "Save" button.
Import Profile Job
After opening context menu, execute "Import Profile Job(s)".
A file dialog box will then appear for selecting the file to be imported.
After choosing the desired file, click the "OK" button. If any duplicates are found, the DBA will be asked whether to overwrite them.
OS Profile Job: Pre-defined Profile Job
The OS Profile Job is a profile job for the OS on which Altibase is running.
Technically, the OS Profile Job collects OS information using the OS vendor's API.
Therefore, OS Profile Jobs are fixed, and the DBA cannot create his/her own profile job set.
Add/Remove/Edit
"Add" and "Remove" are not available for OS Profile Jobs.
The DBA is allowed to edit only the "Cycle Time" and "Remove Older Than" fields.
These are edited in exactly the same manner as when editing DB Profile Jobs.
Start/Stop
Usage is exactly the same as when starting or stopping DB Profile Jobs.