Dave, It may or may not be the case with you but, We faced the same error when we were using the qualification "TR.Status != DB.Status" instead of Status != "DB.Status".
We got rid of this error when i corrected the qualification. This was during the upgrade from ARS 6.0 to ARS 7.1 On Tue, Sep 15, 2009 at 8:34 AM, Shellman, David < [email protected]> wrote: > ** We upgraded to 7.1 Patch 7 (Windows/Oracle) from 7.0.1 over the > weekend. Since then we are seeing issues a large number of "Too many > filters processed during this operation (ARERR 298)" errors. Most are > associated with escalations but we are also seeing it in when individuals > are updating records in our home grown system. Very seldom did we see this > issue when on 7.0.1. > > Yesterday I updated the Maximum Filters for an Operation to 20000. I just > bumped it to 40000. > > Any ideas of what parameters to change to or reasonable values is greatly > appreciated. > > Dave > > Dave Shellman > > Phone: (717) 810-3687 > Fax: (717) 810-2124 > email: [email protected] > > *Tyco **Electronics* > MS 161-043 > PO Box 3608 > Harrisburg, PA 17105-3607 > > > > _Platinum Sponsor: [email protected] ARSlist: "Where the Answers > Are"_ -- Regards, Kiran Kodali Ph: 940-231-8524 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"
