Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sumwanlah
Starting Member
43 Posts |
 Posted - 2002-05-30 : 07:34:35
|
Something to tingle your spider senses!!!I've read a couple of postings related to this. So far, I've yet to see any hint of a solution about it. Not that I'm offering one now. Just thought I chip in with a little analysis here.I'd encountered some problems recently with only one of my servers. It has got a few linked server connections setup. I knew of the problems only when I wasn't getting fresh data from these linked servers.When I clicked on the links, I get an OLEDB error. Can't recall right now the exact message, but it ends off with "Provider out of memory". Dropping and recreating these server links won't work of course. Then I verified that this error is confined to only one server, cos I created the same links on other servers, with no problems.Someone posted a suggestion to reboot the server. Took up that suggestion once before, thank goodness it worked that time. But when the error occured again, several weeks later, I thought it's not a good idea to reboot again. Downtime is usually a no-no, remember??  So I resisted as long as I could, for a couple of hours at least, but I succumbed to that desire to reboot! Hah! But not before doing much investigating.I noticed that the primary disk space has less than a couple of Megs left!! I know, I know... It's bad management man! Luckily my datas in another disk. So I started clearing some space. When I got to the Temp directory however, I found many .TMP files, some of them as big as 50Megs! Now, this server of mine is purely a SQL server, of course, so my conclusion is that these .TMP files are generated by the SQL server. Correct me if I'm wrong on this. My reasoning is because the .TMP filenames are prefixed either with 'JET' or 'MMC'.Since the latest incident, it's been three weeks now. I'm still monitoring the remaining disk space and diligently removing the .TMP files. Things are working normally so far... A good improvement considering it occured twice in the three weeks prior.Could these temp files possibly be the cause of this "Out of memory" problem? In the first place, are these files related to SQL server or not?------------------------What goes around...? Is the belt around my waist! |
|
|
|
|
|
|
|
Linked Servers: OLEDB Memory Problems?