Tables created for triggering
See 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 Launchers that are accessing this database. The Launchers must have unique machine name and TCP/IP address combinations. (In other words, triggering is only supported for one Launcher 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/Launcher environments.
- Trigger_Registry
- Used during processing, this table registers every "watched" table for each Launcher. The "watches" on each card are placed here. In this registry is every map on every 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 Oracle 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.