Just wondering, do you have access to the database? Following the possible corruption path. Try running at query against the filter_push table and see how many push actions are actually in the database.
select * from escalation where name = '<escalation name>' select * from filter_push where filterid = '<escalationId returned from the first query>' Maybe there are two db entries for a push but only one shows up in the admin tool/def file? Jason From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Pickering, Christopher Sent: Tuesday, October 02, 2007 12:41 PM To: [email protected] Subject: Re: Escalation creating dup tickets ** Thats the another odd part of it. Although the first firing indicates that the escl failed, then the next log entry is the firing of the same escl again, but if you wade through the push fields, you will see that each field is pushing twice, then actions 2 & 3 are duplicated. I've been waiting for BMC to call back with their diagnosis, but I can't wait that much longer. I have to get this back into production. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
