RE: SRTxxx: the trouble with Tribbles?
These files are created by Informix, there are a few others also, in the directory in the "PSORT_DBTEMP" environment variable. The default is "/tmp" if it is not set. Wayne E. Martin Informix Database Administrator Kmart Corp. -----Original Message----- From: Doug Agnew [mailto:dagnew@charlottepipe.com] Sent: Tuesday, May 23, 2000 8:29 AM To: informix-list@iiug.org Subject: Re: SRTxxx: the trouble with Tribbles? Given the name SRTxxxx, I would guess rather that the files are sort work files. Check DBSPACETEMP, I think. (sorry, its early in the morning and my brain is on half-speed). At any rate, you need to direct your sort work areas to temporary dbspaces. HTH, Doug "Jedi Master Yoda" <yoda@dagobah.org> wrote in message news:slrn8iksja.21b.yoda@homer.cromwellmedia.co.uk... > INFORMIX-Universal Server Version 9.14.UC6 on SunOS 5.5.1 > Generic_103640-31 sun4u sparc SUNW,Ultra-2 > > The server has taken to creating hundreds of files in /tmp called things > like srt0105709_001 (where the number varies). Though the system is > short on physical memory, it has plenty of swap. Having searched the > documentation, Web, Usenet, IIUG and FAQs I can find nothing to explain > what they are. > > The problem is that eventually (over a few days) the files fill up > /tmp completely and bring the machine to its knees. I'm guessing > that since /tmp is on a swap filesystem these files are some kind of > logical representation of the shared memory blocks that Informix is > allocating. Either way, I need to know how to stop these files being > created/shared memory being grabbed. Any ideas?
On Tue, 23 May 2000 10:36:27 -0400, Martin, Wayne E. <WMartin@kmart.com> spouted: >These files are created by Informix, there are a few others >also, in the directory in the "PSORT_DBTEMP" environment >variable. The default is "/tmp" if it is not set. Thanks guys. According to the Performance Guide, sort files should go to the dbspaces specified in DBSPACETEMP. Although we have a DBSPACETEMP defined, the tempdbspace is completely empty, so it looks like something's gone pearshaped somewhere. I'll apply the trusty sysadmin's 4lb lump hammer to the side of the machine and see if that fixes it.