Data Transformation Engine Database Interface Designer Reference Guide

Chapter 9 - Database Triggers Database Triggers Overview
Database Interface Designer Reference Guide
134
Otherwise, the database triggers will continually remain in operation, taking up
processing and space resources on the target DBMS.
If the triggering installation script cannot be run, a temporary solution would be to
run the following SQL statements on the target DBMS:
1 DELETE FROM Trigger_Events;
2 DELETE FROM Trigger_Registry;
3 COMMIT;
Handling Truncated Tables
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 the Trigger_Events table as shown in
the following procedure.
Note Make sure you only delete those rows in the Trigger_Events table associated with
the truncated table. Also, you can perform this procedure after dropping and
re-creating a table.
To delete table-specific truncated rows
1 Enter the following SQL statement:
DELETE from Trigger_Events WHERE ID IN (
SELECT ID FROM Trigger_Registry WHERE TriggerName IN (
SELECT TriggerName FROM Trigger_Catalog
WHERE UPPER(SourceSchema) = UPPER('
schema_name ') AND
UPPER(SourceTable) = UPPER('
table_name ')))
where
schema_name is the name of your schema and table_name is the name
of the truncated table.
2 Commit the transaction (for example, COMMIT;).