## -8052: Trigger dropped during migration; check view migrationerrorprotocol

### Explanation:

When the database catalog was migrated to UNICODE, some triggers could not be recreated. The database system created replacements for these triggers.

### User Action:

In the MIGRATIONERRORPROTOCOL system table, check the CREATE statements for the triggers that could not be recreated.

The CREATE statement for a trigger can be incorrect for the following reasons (for example):

· The trigger is referencing a table or view that was renamed or does not exist any more.

· The syntax within the trigger has changed.

You can delete the replacement trigger once you have fixed the original one.

See also:

System tables documentation