Glossary
A
- auditing
- The process of keeping track of database changes to provide a record of
the evolution of the database. Auditing provides a mechanism to track who
performed what actions and helps prevent unknown or unanticipated access to
the data.
- apply
- The process of integrating change commands or changes into a model.
- archive
- The process of capturing data, definitions, and environment information
from the archive source (expressed in SQL) and storing this information in
an archive target; as well as deleting some or all of the source data. This
process can be performed by running an unload task.
B
- base model
- A model that is a representation of a database before changes are applied
and upon which the DB2® Change Management Expert deployment
script is based. See also model, model version, and target
model.
C
- change commands
- An ordered collection of operations such as DDL, DML, DCL, running utilities,
bind, and rebind.
- change specification
- The process of defining a set of changes that you want to apply to a database.
The process involves making changes to models of the database and analyzing
the impact of those changes. After the changes are defined, they can be deployed
to the actual database
- comparison
- The process of analyzing the differences between two models. Often, a
model of a database that contains the proposed changes is compared to an earlier
model of the database to understand the effects of the changes. Or, when the
schema of one database is being changed to match another database, the model
of the source database can be compared to a model of target database to determine
the differences between the databases.
- copying
- Moving an object or objects where the entire internal structure is copied
from the source database to the target database.
D
- data design project
- A container for storing the resources that are needed to plan, analyze,
and make changes to a database. Projects map to directories in the file system.
- data preservation
- The process of specifying how to control data in the target database when
there are changes to database structure or metadata.
- database timeline
- The state of a database at various points of time. Models of the database
timeline can be compared by using the Compare With selection.
- deploy
- The process of issuing change commands against DB2 objects. For example,
tables, table spaces, and triggers. Deploy is a step in the deployment process.
- deployment
- The process of changing the database to reflect the conditions that were
specified in the change specification phase. Deployment encompasses the process
of naming the target database, declaring the change commands that will be
deployed against that database, and the steps to implement the change, deploy
the change, and manage the undo process.
- deployment script
- The set of changes that you want to make to your database. The deployment
script binds the change management resources together and organizes those
resources into a coherent form. It describes the specification resources and
metadata about how the change will be issued. You use the deployment script
to deploy the changes to your DB2 databases.
G
- generate
- The process of creating change commands .
I
- impact analysis
- The process of finding the dependencies that exist for an object. As changes
are made to an object, a list of the related objects that might be impacted
by the changes can be generated.
- inoperative object
- A DB2 object that is valid, but must be recreated to be used.
L
load providers
A data load provider generates a particular type of load command during
data preservation. The 'IMPORT' provider generates the DB2 Import command
and the 'LOAD' provider generates the DB2 Load command. You can specify the
default Data Load provider in your preferences. You can override the default
setting for any particular data load operation by choosing the load provider
in the Generate Change Commands wizard. 
M
- migration
- Moving an object or objects where only part of the internal structure
is copied from source to target. The process of changing the catalog schema
of one database to match another database. Migration can be initiated from
several different starting points. For example, source and target objects
are compared and DDL generated to bring the target in line with the source.
Database objects, attributes, or dependencies can be migrated within the same
database or between database tiers.
- migration analysis
- Comparing and moving the differences between the model of one database
to the model of another database when changing the catalog schema of one database
to match another database.
- model
- A representation of the database catalog (referring to database schema
objects). A model can be stored in memory or stored on the local file system.
See also base model, model version, source model, and target
model.
- model analysis
- The process of analyzing a model to verify that it is compliant with the
defined constraints.
- model version
- A type of model that provides a representation of the database catalog
at a particular point in time. As a snapshot of the database at a particular
point in time, a model version provides important auditing information.
- multiple provisioning
- The process of deploying changes to multiple databases at once.
P
- project
- See data design project.
R
- refresh
- The process of ensuring that the base model matches the most current version
of the DB2 database catalog. It is possible that changes occurred to the database
between the time the change commands were created and the time the change
commands are to be deployed. Refreshing the base model provides the opportunity
to discover any changes and, if necessary, re-create the change commands.
- resources
- The models and scripts that make up a change. The resources for a change
reside in folders in the project for the change.
S
- source model
- A model that serves as the basis, or source, of change for another model.
T
- target model
- A model that is a representation of a database after changes are applied
and upon which the DB2 Change Management Expert deployment
script is based. See also model and base model.
- tier
- Describes the database's purpose in the IT infrastructure. For example,
the development rack, the test rack, or the production rack are all different
database tiers.
U
- undefined object
- A DB2 object that is valid and operative, but is undefined at runtime.
unload providers
An unload provider generates a particular type of unload command during
data preservation. The 'EXPORT_DEL' unload provider generates EXPORT commands
with the DEL data file format. The 'EXPORT_IXF' unload provider generates
EXPORT commands with IXF data file format. The HPU provider generates the
High Performance Unload command. For the HPU commands to be deployed successfully,
DB2 High Performance Unload for Multiplatforms product must be installed.
You can specify the default Data Unload Provider to be used when you generate
your Data preservation commands. You can override the default for any data
preservation entry in the Generate Change Commands wizard. 