Error:741: Trigger for the same event already exists.
R Smith got error -741 (trigger for the same event already exists) creating an insert trigger, but drop trigger gave 634 and 111 (no record found). Deleting rows from systriggers and systrigbody did not help, and no other insert trigger existed on the table. Michael Krzepkowski suggested an ownership issue; R Smith said he owned it. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hmmm... well, this one is keeping me up late tonight.
Today, I have been working on new/old procedures and triggers and
as I was updating the database, I ran into the -741 error.
This happens to be a trigger that I did not modify, so it's more
mystifying than usual.
I simply added a 'drop trigger' statement before the 'create' and
now I am being told that the trigger already exists.
When I execute the 'drop trigger' statement, I get the following
error:
634: Object does not exist.
111: ISAM error: no record found.
... so what's the deal? It's not there on the drop and it exists
on the create??
Then, I got fancy, and may have dug myself a bigger hole. There
were references to the original trigger in systriggers and systrigbody,
so I deleted them. Guess what? No difference!!
I'm not sure where to go from here if I can neither delete or
create it.
Any help would certainly be appreciated.
drop trigger "exedor".rej_insert;
create trigger "mediator".rej_insert insert on "exedor".reject_info
referencing new as pre
for each row
(
execute procedure "exedor".insertrejaudit(pre.reject_id,
pre.wf_id ,pre.case_id ,pre.case_solution_id,
pre.switch_id ,pre.so, re.tn ,pre.rj_dt_tm ,pre.last_update,
pre.retry_counter ,pre.output_msg, ,pre.action_seq ),
execute procedure reject_received (CURRENT),
execute procedure insert_wf_link (pre.wf_id, pre.reject_id, "R")
);
-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 80,000 Newsgroups - 16 Different Servers! =-----
I omitted this, which may be important to any respondents. I did confirm that there are no other triggers for the insert event on that table. -----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- http://www.newsfeeds.com - The #1 Newsgroup Service in the World! -----== Over 80,000 Newsgroups - 16 Different Servers! =-----
Hi! Just a shot in the dark: maybe it is ownership issue. If you look through catalogs there should be owner of the trigger. HTH Michael R Smith wrote: > I omitted this, which may be important to any respondents. > > I did confirm that there are no other triggers for the insert > event on that table. > > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- > http://www.newsfeeds.com - The #1 Newsgroup Service in the World! > -----== Over 80,000 Newsgroups - 16 Different Servers! =-----
Michael, Thanks for the reply, but ownership is not the issue, but good try. I'm the owner. michaelk@sqlcanada.com (Michael Krzepkowski) wrote in <38DAEE44.32B5568F@sqlcanada.com>: >Hi! > >Just a shot in the dark: maybe it is ownership issue. If you look >through >catalogs there should be owner of the trigger. > >HTH > >Michael > > >R Smith wrote: > >> I omitted this, which may be important to any respondents. >> >> I did confirm that there are no other triggers for the insert >> event on that table. >> >> -----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- >> http://www.newsfeeds.com - The #1 Newsgroup Service in the World! >> -----== Over 80,000 Newsgroups - 16 Different Servers! =----- > -----= Posted via Newsfeeds.Com, Uncensored Usenet News =----- http://www.newsfeeds.com - The #1 Newsgroup Service in the World! -----== Over 80,000 Newsgroups - 16 Different Servers! =-----