Data Transformation Engine Database Interface Designer Reference Guide

Chapter 9 - Database Triggers Database Triggers Overview
Database Interface Designer Reference Guide
132
Tables Created for Triggering
Refer to the following table for information about the four tables that are created
by executing the SQL script:
Table Description
Trigger_Server Used at startup, this table tracks the Event Servers that are
accessing this database. The Event Servers must have unique
machine name and TCP/IP address combinations. (In other
words, triggering is only supported for one Event Server per
machine.)
Trigger_Catalog Used at startup, this table tracks all triggers for all tables that
have been defined on this database. This functionality allows
table "watches" to be reused across multi-user/Event Server
environments.
Trigger_Registry Used during processing, this table registers every "watched"
table for each Event Server. The “watches” on each card are
p
laced here. In this re
g
istr
y
is ever
y
ma
p
on ever
y
machine that
is being "watched".
Trigger_Events Used during processing, this table records all events that have
occurred as a result of the table "watches" defined in the
Trigger_Registry table.
Note For Oracle8 only. If an Oracle table is truncated or
dropped while having unprocessed row-based table
entries, there may be map execution problems. To avoid
these problems, you may have to perform some
maintenance on this table. For information about how to
do this, refer to Handling Truncated Tables.