Optim™ Database
Administrator 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 to change management script
- The process of integrating change commands or changes into a change
management script.
- 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.
C
- change commands
- An ordered collection of operations such as DDL, DML, DCL, running
utilities, bind, and rebind.
- change management script
- The set of changes that you want to make to your database. The
change management script binds the change 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 can
use the change management script to deploy changes to your DB2® databases.
- 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 the target database to determine the differences between
the databases.
- copy and paste
- The process of copying an object in the Object List and pasting
the object into the same database or a different database. The Change
Management Script Editor can be used to move the objects, data, and
dependencies.
- copying
- Moving an object or objects where the entire internal
structure is copied from the source (database connection, physical
data model, or a DDL script file) 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 Partitioning Feature (DPF)
- A feature in DB2 for Linux, UNIX, and Windows that
can be used to improve the management of a large database by dividing
it into multiple database partitions that are physically placed on
one or more servers.
- deploy
- The process of issuing change commands against DB2 objects. For example, tables, table spaces,
and triggers. See also run.
- 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, running the
change commands that were generated during the change specification
phase against the database, and managing the undo process.
- DPF
- See Database Partitioning Feature.
G
- generate
- The process of creating change commands .
H
- HADR
- See high availability disaster recovery.
- high availability disaster recovery
- A disaster recovery solution in DB2 for Linux, UNIX, and Windows that
uses log shipping and provides data to a standby system if a partial
or complete site failure occurs on a primary system.
I
- ignore
- The process of having objects ignored when migrating objects with
the Change Management Script Editor. An ignore
causes the object type to be excluded from being in the comparison
of the source objects and target objects in the Compare
Editor.
- 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 re-created to be used.
M
- mask
- The process of having names translated when migrating objects
with the Change Management Script Editor. A mask
causes the names in the source objects to map to the names in the
target objects in the Compare Editor. For example, the schema name
for DEV can be mapped to TEST.
- 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). See also source model and target model.
- model analysis
- The process of analyzing a model to verify that it is compliant
with the defined constraints.
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.
- reload method
- The reload method determines which type of reload commands will
be generated for external data preservation. The method to be used
can be specified by clicking Data Options in
the Commands section of the Change
Management Script Editor, which starts the Customize
Data Preservation wizard.
- resources
- The models and scripts that make up a change. The resources for
a change reside in folders in the project for the change.
- restart
- The process of restarting the commands in a change management
script if an error occurs when the change management script is run
from the Change Management Script Editor.
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.
- task assistant
- An editor that helps guide you through the process of performing
various database administration activities, such as backing up a database,
loading a table, or rebinding a package.
- 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.
- undo
- The process of reversing (or undoing) the commands that were successfully
deployed or partially deployed from the change management script in
the Change Management Script Editor.
- unload method
- The unload method determines which type of unload commands are
generated for data preservation and whether data preservation is performed
externally in data files or internally in the database. The method
to be used can be specified The method to be used can be specified
by clicking Data Options in the Commands section
of the Change Management Script Editor, which
starts the Customize Data Preservation wizard.