PreviousNextIndex

Glossary


This Glossary contains definitions of terms used throughout the HACMP for AIX (HACMPTM) Smart Assist for DB2, Version 5.4 documentation set. General familiarity with AIX 5L and networking terms and commands is assumed.

For general terms used in HACMP and for HACMP usage of some specific AIX terms and commands, see Master Glossary for HACMP, Version 5.4.

For additional information on the DB2 terminology, see About This Guide

database

A collection of raw data managed by DB2 or other database software.

DB2 failover

A function of the DB2 software that is the same as the term fallover used in HACMP. This guide and the SMIT interface for HACMP Smart Assist for DB2 uses the term fallover.

See also Fallover.

database instance

A collection of database software necessary to manage the database and a database name, volumes, files in the /run directory, and a collection of metadata including configuration files, database parameters, and paths to volumes.

To start a database instance, the kernel of the database system software is started by specifying the instance name.

In DB2, a database table name is unique within the confines of an instance. And, conversely, different database tables with the same name can exist in multiple DB2 instances.

See also db2nodes.cfg.

db2nodes.cfg

The ASCII-based configuration file for a given DB2 instance that is instance-specific. Exists under the /sqllib directory of the instance home directory. This file maps the location of the logical DB2 UDB partitions to physical nodes.

F

fallover

The process of an active node acquiring resources, such as a service IP label and a DB2 instance previously owned by another node, in order to maintain availability of those resources. You can specify a fallover policy for a resource group.

See also DB2 failover.

H

hostname

A name of node/host on which to run the partition. The TCP/IP host name of the database partition server. This entry is required.

P

primary node

A cluster node on which the application runs unless a condition forces a fallover to another cluster node. It is also a home node for the resource group hosting the DB2 instance.

See also standby node.

S

standby node

A cluster node on which the application runs after a fallover from the primary node.

See also primary node.


PreviousNextIndex