Informix Error -634: Object does not exist.

Reasons / Common Causes

-634, despite its generic-sounding text, is specifically about DROP TRIGGER — per the official guidance, it fires when attempting to drop a trigger that doesn't exist under the name given.

1. A misspelled trigger name in DROP TRIGGER, per the official guidance — the direct, common cause.
2. A trigger already dropped previously, with the DROP TRIGGER statement re-run without checking whether it had already succeeded.
3. A trigger that was never actually created, due to an earlier failed CREATE TRIGGER statement that the current attempt assumes had succeeded.

Solutions / Resolution

1. Check that the trigger name is spelled correctly, per the official guidance.
2. Query systriggers to review the names of triggers in the database, per the official guidance:

   SELECT trigname, owner FROM systriggers;
   

3. Confirm whether the trigger was already dropped or never successfully created, once the spelling is confirmed correct and the trigger genuinely isn't listed.

Examples

A misspelled trigger name

DROP TRIGGER trg_orders_updte;
-- -634: the actual trigger is named trg_orders_update

Listing triggers to find the correct name

SELECT trigname, owner FROM systriggers;

Diagnostic Checks

1. Run the systriggers query to confirm the trigger's exact name (and whether it exists at all) before retrying DROP TRIGGER.

Related Errors / Related Topics

No closely related error codes are cross-referenced for -634 in this set yet.

Despite the generic wording, this is specifically about DROP TRIGGER — query systriggers to confirm the exact name before retrying.