Oracle. I agree something isn't right. Our entire system is home grown. We're talking 319 forms, 2487 Active Links, 1888 Filters, 119 Escalations, 93 Active Link Guides, 29 Filter Guides, 271 Menus and 49 Groups. A heck of a lot less than the ITSM Suite. The server guys reconfigured the Windows temp space to a larger external drive before I pinpointed the file being associated with an export. We also don't have much space on the c: drive of the server. Shouldn't have to. Support wants me to do some more testing for them. Dave
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Tuesday, September 18, 2007 10:58 AM To: [email protected] Subject: Re: Large file in system temp directory ** Well, that still doesn't make sense, because even your DB, including all indexes, isn't 10 GB. Either there's some horribly inefficient design, or there is a local issue. I have Windows servers that don't have 10 GB of open disk space, and I create def files for and on them all the time without running out of space. Is this SQL, or Oracle? Rick On 9/18/07, Shellman, David <[EMAIL PROTECTED]> wrote: From my understanding it's kind of a scratch file that is then processed down to what comes out in the def file. It seems to me that it shouldn't be that much bigger than the size of the def file that gets created. Worse case maybe an order of magnitude larger. I think that somehow it's tied into the timeout due to server busy message. To me it looks like some kind of looping condition that continues to gather data but no where to report it. The admin tool has dropped the link and creates a 0 size def file. I haven't had a response to my question about the timeout condition. Dave ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Tuesday, September 18, 2007 10:12 AM To: [email protected] Subject: Re: Large file in system temp directory ** 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 __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
