[email]psafasysinct.com[/email] (Pouya) wrote in message news:<ef4a87ef.0307091017.163584a2posting.google. com>...Not much help, but have you verified that the triggers are in place?> OK,
> I'm having a problem getting triggers to kick off on an AIX box. I
> have implemented this same database/triggers on an NT box and the
> triggers are working properly. Can triggers be turned off on DB2? I'm
> trying to figure out what could hinder triggers from working... could
> it be an AIX thing?
> *** I did not install/configuration DB2 on AIX so I'm taking another
> engineers word for it, but did do the install/configuration on NT
> *** An example of a trigger in question is:
> CREATE TRIGGER GENERATE_PART_ID NO CASCADE BEFORE INSERT ON Episode
> REFERENCING NEW AS n FOR EACH ROW MODE DB2SQL SET ( n . pid ) = case
> when ( select max ( isnewpid ) from gainIDSetting ) = 1 then ( select
> max ( pidStartID ) from gainIDSetting ) else ( select max ( PID ) + 1
> from episode ) END
If yo have access to the database, yo can try something like:
select * from syscat.triggers where trigname = 'GENERATE_PART_ID'"
if the trigger exists, you should see at least one row returned.
As far as I can tell there is no way that you can "turn off" a trigger
by mistake. In fact, I have seen a few posts where people are
wondering how on earth they are going to disable a trigger