Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Expiration\s+\=\s+FEAR\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Expiration\s+\=\s+FEAR\s*$/: 7 ]

Total 7 documents matching your query.

1. Expiration = FEAR (score: 1): Author: Scott Fluegge <sfluegge AT VENATORGROUP DOT COM>; Date: Mon, 29 Mar 1999 09:39:40 -0400; Hi all, I have a problem that seems to have effected a bunch of people here. Expiration... I upgraded ADSM and fixed my management classes (I had them set to retain omly=1 and retain extra=1 for an S; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-03/msg01665.html (10,837 bytes)
2. Re: Expiration = FEAR (score: 1): Author: Russell Street <russells AT AUCKLAND.AC DOT NZ>; Date: Tue, 30 Mar 1999 09:44:45 +1200; Yes. The first time from 3.1.1.3 to 3.1.2.1 the system did that. Now it expiration takes >24 hours, examines about 9 million objects and deletes a few hundred thousand. This is on a system with 32 m; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-03/msg01695.html (11,299 bytes)
3. Re: Expiration = FEAR (score: 1): Author: "Price, Robert R." <pricerr AT WESTINGHOUSE DOT COM>; Date: Tue, 30 Mar 1999 10:10:05 -0500; I too have seen this behavior after migrating to 3.1.2.1. The expiration, which used to run successfully in about one hour, now takes days utilizing as much cpu as it can get. The object counts in th; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-03/msg01708.html (12,190 bytes)
4. Re: Expiration = FEAR (score: 1): Author: Gerhard Rentschler <g.rentschler AT RUS.UNI-STUTTGART DOT DE>; Date: Tue, 30 Mar 1999 17:54:09 +0200; Robert, there is a known problem with expire inventory looping. I think you should open a pmr. I have a similar one which causes backup sessions to hang. Best regards Gerhard -- Gerhard Rentschler em; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-03/msg01709.html (10,955 bytes)
5. Re: Expiration = FEAR (score: 1): Author: Price, Robert R. [SMTP:pricerr AT WESTINGHOUSE DOT COM]; Date: Sun, 04 Oct 2015 17:46:05 -0500; I too have seen this behavior after migrating to 3.1.2.1. The expiration, which used to run successfully in about one hour, now takes days utilizing as much cpu as it can get. The object counts in th; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-03/msg01710.html (10,973 bytes)
6. Re: Expiration = FEAR (score: 1): Author: "Jones, Anthony" <Jones4A AT KOCHIND DOT COM>; Date: Tue, 30 Mar 1999 10:04:49 -0600; These issues are "supposedly" fixed in the latest release of ADSM Server. The ftp site has the latest 3.1.2.20 version for AIX server available. Read the README.SRV.txt. Anthony Jones Platform Techno; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-03/msg01713.html (13,129 bytes)
7. Re: Expiration = FEAR (score: 1): Author: Ilona Kersey <ijk AT GTE DOT NET>; Date: Tue, 30 Mar 1999 14:36:53 -0500; upgrade to 3.1.2.20 did not fix this ... expiration still hanging ijk ilona.kersey AT swpc.siemens DOT com Siemens Westinghouse Power Corporation; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-03/msg01726.html (13,025 bytes)

Current List: 1 - 7
Page: [1]