OK, here's what I don't get on this: The biggest def file I have is around 200 MB, and that's including most of ITSM 7. How is a 10+ GB temp file justified? If it's working as designed, make them justify the design.
Rick On 9/18/07, Shellman, David <[EMAIL PROTECTED]> wrote: > > ** Here's an update on the issue. The file size was 10 Gig and growing > rapidly. The file was specifically tied to exporting workflow from the > admin tool. As soon as we would cycle the service associated with the AR > System the file would disappear. When I would start the export process, the > file would appear. > > We just moved over to the Windows environment from SUN systems. I don't > ever remember seeing anything like this on SUN. If the system would have > been writing a file this large in system workspace, the SUN guys would have > been all over me. > > I got a response from Support yesterday. It's working as designed. I > haven't ever had the admin tool time out with server busy error with an > export of workflow before. I also did not see (could have missed it some > where) that exporting workflow would create a huge temporary file in a > system temp directory. If we would have known this before we would have > setup disk space much differently. > > Dave > > > ------------------------------ > *From:* Action Request System discussion list(ARSList) [mailto: > [EMAIL PROTECTED] *On Behalf Of *Rick Cook > *Sent:* Monday, September 17, 2007 1:27 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Large file in system temp directory > > > ** Was this an import that someone in your environment actually initiated, > or just some random function of AR System? > > Rick > > On 9/16/07, Shellman, David <[EMAIL PROTECTED]> wrote: > > > > ** > > > > We moved over to AR System 7.0.1 Patch 003 on Windows 2K3 server that > > connects to a separate Windows 2K3 server running Oracle 10g. > > > > We ran into a situation tonight where a large file was being created in > > the c:\windows\temp directory. The file was growing quickly. When the AR > > System services were stopped, the file would disappear immediately. After > > some trial and error, we discovered that the file was associated with trying > > to create an export file of all the workflow on the server. The export > > would time out and this file would continue to grow. Currently using > > 7.0.1 Patch 003 admin tool. > > > > I created a ticket with BMC/Remedy. We'll see how many hoops I have to > > jump through before I get them to understand it's the result of an export. > > > > 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 > > > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
