| Author |
Topic |
|
ejcorcoran
Starting Member
10 Posts |
 Posted - 2003-11-13 : 10:11:22
|
| We are running Windows 2000 Advanced Server SP3, SQL 2000 Enterprise Server SP3, all of the latest patches and updates (minus win2k sp4).The server has 4GB of RAM, of which only 2GB is currently in use. We have 4.19GB of disk space avaiable on the C: drive and 6.25GB on our H: drive (Where we store the databases and logs).When attepting to run a job I receive the following error:Error 22022: Unable to post notification to SQLServerAgent (reason: MapViewOfFile()returned error 8, 'Not enough storage is available to process this command.') This job has run succesfully in the past.I cannot find any information on this error message. I have plenty of storage on the server.Please help.Thank you,EJCorcoran |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2003-11-13 : 11:44:51
|
| What is the job doing?http://www.clrsoft.comSoftware built for the Common Language Runtime. |
 |
|
|
ejcorcoran
Starting Member
10 Posts |
Posted - 2003-11-13 : 11:56:53
|
| The job is tranfering data from one database to another. The first step of the job is to update a column with the current date. That step is generating the error. I tried to skip that step and go directly to the transfer step, and that also errored out. The problem has now escalated, and I cannot manually start any job on the server. I created a test job to copy a text file from one directory to another. It returns the same error message. Like I staed earlier, I have a few GBs to spare on these drives.Thank you for oyur consideration.EJCorcoran |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-11-13 : 12:47:11
|
| Can your databases automatically expand if they run out of room? That option might have been turned off. It is possible that you are filling up the transaction log faster than it can expand. This has happened to me before. Is your log file full? If so, what is your database recovery model set to?Tara |
|
|
|
ejcorcoran
Starting Member
10 Posts |
Posted - 2003-11-13 : 13:10:02
|
| The databses in question are set to autoexpand by 10%. Before starting this discussion we changed msdb to autogrow by 10% instead of by 1mb, as it was originally set to. That, of course, had absolutely no effect.I have done backups of the two databses in question and msdb, no change (I should have thought of that). The recovery model on the two databases is set to full.The problem is now affecting all of my jobs. I cannot maually start any of them.Thank you for looking into this.EJCorcoran |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-11-13 : 13:14:28
|
| msdb wouldn't help you out on this. tempdb is what you need to look at. msdb is used to store information about DTS packages, backups, etc. Are you running transaction log backups on the databases that are set to FULL? Full backups will not clear out the transaction log. Why do you have msdb set to FULL recovery model? That's kind of strange.Tara |
|
|
|
ejcorcoran
Starting Member
10 Posts |
Posted - 2003-11-13 : 13:31:32
|
| MSDB is set to simple, sorry , I misstated myself. I have full and log backups of the other 2 databases and a full back up of msdb. We looked at msdb because that's where the job are stored, but, alas to no avail. Thankfully, I have backups of everything on the server.What do I need to look at on tempdb? In all honesty, I was told "Don't touch that, EVER!" when I started this job. But if it will fix things, I'll do it. Do I need to backup tempdb, and should I be backing it up on a regular basis?Thank you all again,EJCorcoran |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-11-13 : 13:34:33
|
| No do not backup tempdb. This database never has to be backed up.You need to probably allocate more space to tempdb. It probably isn't able to grow fast enough for your data transfers. You should probably do some reading on what tempdb does.Tara |
|
|
|
ejcorcoran
Starting Member
10 Posts |
Posted - 2003-11-13 : 13:55:07
|
| I was hoping that you would say that. Unfortunately my boss has decided that the jobs on the DB need to run, so he had me reboot it. That has "fixed" the problem, but I still don't know what the problem is!If you have any thoughts on this, please help, but I cannot implement those solutions and see if they worked, since, after reboot, the jobs are again working. (The server's previous reboot was last week, before that it was two months, so I cannot think that it just needed to be rebooted.)Thank you again for all your help, it is nice to have timely, expert support.EJCorcoran. |
|
|
|
|
Storage Error?