David,

we noticed the same problem after upgrading to 7.1(from 6.3). I did some 
investigations and found out that before 7.1 only filters were counted if the 
at least one action of the filter was executed. In 7.1 every filter is counted 
regardless if an action is executed or not. We multiplied the "Maximum filters 
for an Operation" by 10 and everything is fine now.

HTH

Kind Regards Conny

-----Ursprüngliche Nachricht-----
Von: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] Im Auftrag von Shellman, David
Gesendet: Dienstag, 15. September 2009 16:36
An: arslist@ARSLIST.ORG
Betreff: Re: ARERR 298 "Too Many Filter" since upgrade to 7.1

Peter,

Thanks.  Support just got back to me an noted that the default is 10,000 but 
that most applications need 200,000 to 660,000.  From the Configuring 
documentation "Defines the number of filters that can be performed in an 
operation. The default and recommended number is 10000. Increase this number at 
your own risk only if you reach a limit in your system and you have verified 
that your workflow is valid."

They also noted trying to increase the Filter Stack Size to a minimum of 
200,000.  If the they are referring to Maximum Stack of Filters, then 200,000 
is not a valid number.  100,000 is the maximum.  Also the Configuration 
documentation gives a similar warning as Maximum Filters for an Operation.

Dave

-----Original Message-----
From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Peter Romain
Sent: Tuesday, September 15, 2009 9:03 AM
To: arslist@ARSLIST.ORG
Subject: Re: ARERR 298 "Too Many Filter" since upgrade to 7.1

My ITSM 7.5 installation automatically set this to 500,000 so you've a way to 
go before you match that!

Cheers

Peter


> 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 < 
> dave.shell...@tycoelectronics.com> 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:  dave.shell...@tycoelectronics.com
>>
>> *Tyco **Electronics*
>> MS 161-043
>> PO Box 3608
>> Harrisburg, PA 17105-3607
>>
>>
>>
>>  _Platinum Sponsor: rmisoluti...@verizon.net ARSlist: "Where the 
>> Answers Are"_
>
>
>
>
> --
> Regards,
> Kiran Kodali
> Ph: 940-231-8524
>
> ______________________________________________________________________
> _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 
> Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum 
Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum 
Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"

Reply via email to