Try using the status value just before Closed and using <= (unless you also need to run the escalation on records with a status value higher than Closed).
i.e. If the status just before Closed is Pending try: ( 'Trouble Ticket Status' <= "Pending") AND (($TIMESTAMP$ - 60) > 'Modified-date') On most databases using != forces a table scan to look at the entire table. Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mahan, Janet L[EQ] Sent: Thursday, April 02, 2009 10:20 AM To: [email protected] Subject: Re: Memory issue on sybase ARS 6.0.1 Memory size: 16384 Megabytes Memory grows to about 3932M or so and ARS dies The table has about 373k rows and approximately 350 tickets open The escalation will Run If: ( 'Trouble Ticket Status' != "Closed") AND (($TIMESTAMP$ - 60) > 'Modified-date') Janet Mahan Network Systems Administrator II EMBARQ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Darrell Reading Sent: Thursday, April 02, 2009 10:42 AM To: [email protected] Subject: Re: Memory issue on sybase ARS 6.0.1 How much memory does your system have, and how large does the arsystem executable grow to? On the table that you are hitting, how many rows are in that table, and how many open tickets are in this table? Lastly, what query is your escalation using to find the open tickets? Darrell Reading Systems Engineer Phone 479.204.5739 [email protected] Wal-Mart Stores, Inc. 805 Moberly Lane, MS-0560-68 Bentonville, AR 72716 Save Money. Live Better -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mahan, Janet L[EQ] Sent: Thursday, April 02, 2009 09:23 To: [email protected] Subject: Re: Memory issue on sybase ARS 6.0.1 Ok, let me ask something else related to my issue. Does anyone have a recommendation of the best way to update all open tickets every 5 minutes other than an escalation? The escalation seems to fill the memory up and kill the server and my interval does not work correctly. Thanks Janet Mahan Network Systems Administrator II EMBARQ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Grooms, Frederick W Sent: Wednesday, April 01, 2009 2:00 PM To: [email protected] Subject: Re: Memory issue on sybase ARS 6.0.1 Looking below it looks like you are on a Sun V240. What OS Version "uname -a" and what is your "ulimit -a" values. Also check your disk space "df -k" Fred -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mahan, Janet L[EQ] Sent: Wednesday, April 01, 2009 11:27 AM To: [email protected] Subject: Re: Memory issue on sybase ARS 6.0.1 Any ideas? Janet Mahan -----Original Message----- From: Mahan, Janet L[EQ] Sent: Tuesday, March 31, 2009 2:18 PM To: Mahan, Janet L[EQ]; [email protected] Subject: RE: Memory issue on sybase ARS 6.0.1 Also get these errors: ARERR [160] Decompression has failed ARERR [300] Malloc failed on server Janet Mahan -----Original Message----- From: Janet Mahan [mailto:[email protected]] Sent: Tuesday, March 31, 2009 1:20 PM To: [email protected] Cc: Mahan, Janet L[EQ] Subject: Memory issue on sybase ARS 6.0.1 Does anyone have any suggestions how to fix a memory issue where the arserverd process grows so that the processes die with malloc errors. It seems to be related to escalations that I have updating tickets every 4 or 6 minutes. I have opened tickets with BMC but our version is not really supported. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
