Actually..... I think if the ARS server knows what "Filter 'X' is bad" then there likely is a row in the filter table for that filter. ( But the ARS server just does not like what it sees for that filter, so it complains and "ignores" the filter. So the admin tool would never show the object in it's lists/UI.)
BTW: This kind of problem falls into that mystical "That should never happen" group of problems. So how you fix it... also falls into that set of "you should never have to do this kind of thing" space too. Mucking around in the "meta tables" of ARS is way beyond "not supported". Doing these things may qualify for BMC to actually laugh at you as they hang up on the support call. ( So be warned.. you are likely on your own here.) My two cents on what I think you could try to do to fix this: 1) Do a DB backup. 1.1) Put the backup somewhere safe. 1.2) Test the DB backup without breaking/changine the currently "broken" env. 1.3) If the test fails... go back to step 1 or risk loosing your whole ARS server. (your choice) 2) Find the filterId value based on the name that the AR Server kicks out at start up. 3) Then delete all the related records for that filterId in the other filter* tables for that filterId. 4) Stop and Start the ARS server. If all went well... then you should not have any remaining trace for that filter on the system and the AR Server will stop "ignoring" it because it no longer exists. 5) Rebuild ( I would suggest you NOT restore from def/xml file backup) the filter with the Admin Tool. This gives the Admin tool a shot at getting it right this time. ( Note this may require some very detailed knowledge of how to read a backup def file, or you may have to "reinvent the wheel". But it is much safer, IMO, to redo the build with no possible way to "drag a bug" along with you too.) HTH. Good luck. -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On Feb 8, 2008 11:04 AM, Robert Molenda <[EMAIL PROTECTED]> wrote: > ** > Whoops MY BAD (not enough cafe yesterday I guess)... > > The queries for the Filter Actions, need to also have the following added to > the end of each sql statement... > > and filterId not in (select escalationId from escalation) > so for example: > select * from filter_notify where filterId not in (select filterId from > filter) and filterId not in (select escalationId from escalation) > > This is because Escalations use 'filter actions'... > > sorry about any confusion... > > However Cleanup, yes, if you backup your database, then you can delete > these rows, etc. > > On Documentation, Yes, have a look at the "Database-Ref-xxx.pdf" file... > > However since you know the filter name, you could do the forensics backwards > (down) so to say. > > BTW - what version / patch are you on? <snip> > > Robert Molenda wrote: > > ** > > Generally this happens because "something got corrupted" in the ARSystem > Meta Data... > > > > When you tried to import the filter again, did you remember to check the > 'overwrite' checkbox? > > > > You can try the following SQL to 'try' to determine where the issue could > be: > > > > All statements should return Zero rows... > > > > /* Form deleted but filters still reference it */ > > select * from filter_mapping where schemaId not in ( select schemaId from > arschema ) > > > > /* Filter exists but is not mapped to any form */ > > select * from filter where filterId not in ( select filterId from > filter_mapping) > > /* Filter Mapping exists, but filter does not */ > > select * from filter_mapping where filterId not in ( select filterId from > filter) > > > > /* Fragments left in Filter action definitions, but filter does not exist > */ > > select * from filter_notify where filterId not in (select filterId from > filter) > > select * from filter_notify_ids where filterId not in (select filterId > from filter) > > select * from filter_message where filterId not in (select filterId from > filter) > > select * from filter_log where filterId not in (select filterId from > filter) > > select * from filter_set where filterId not in (select filterId from > filter) > > select * from filter_process where filterId not in (select filterId from > filter) > > select * from filter_push where filterId not in (select filterId from > filter) > > select * from filter_sql where filterId not in (select filterId from > filter) > > select * from filter_gotoaction where filterId not in (select filterId > from filter) > > > > /* Never actually got around to this one but... thought about trying some > left-outer of left-outer, but... maybe someone else can struggle with that > :( */ > > select distinct filterId from (above list of action tables) into excel > > crunch up excel to find a filter without any definition in the action > tables > > > > HTH > > > > Robert Molenda <snip> > > > > > > On 2/7/08, Remedy Maniac <[EMAIL PROTECTED]> wrote: > > > > dear listers, > > > > > > > > following my issues with export (see previous post), I noticed that > > > > whenever I start the ARSystem, I see messages about "error in > definition > > > > for a filter". > > > > When I look in the Admin tool I don't see the filter. But it exists in > > > > the database in table Filter. > > > > So first thing is what to do? > > > > Second though is my database is somehow corrupted. Is there a way to > > > > correctly rebuild the database? > > > > We already tried to rebuild the indexes, all, including the primary > > > > keys. That didn't help. > > > > Maybe there is some internal mechanism via Remedy itself. > > > > Any help on this? > > > > Thank you. > > > > S. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
