December 17, 2008 at 7:39 am
We discovered a problem yesterday with one of our subscriber databases in a merge replication scenario. Replication is/was failing due to:
--Could not allocate space for object 'MSmerge_genhistory' in database 'Kreus2_1' because the 'PRIMARY' filegroup is full. (Source: MSSQLServer, Error number: 1105)
The first thing I did was to check the data drive and found that there is more that 300GB of free space on this drive.
Next, I attempted to manually grow the file and received the following error:
--MODIFY FILE encountered operating system error 1450(Insufficient system resources exist to complete the requested service.) while attempting to expand the physical file.
At this point, i rebooted the server and after the restart was complete, checked the database Log which contained the following entries:
2008-12-17 07:11:27.72 spid51 G:\Program Files\Microsoft SQL Server\MSSQL\data\Kreus2_1.mdf: Operating system error 1450(Insufficient system resources exist to complete the requested service.) encountered.
2008-12-17 07:11:27.74 spid51 Error: 1105, Severity: 17, State: 2
2008-12-17 07:11:27.74 spid51 Could not allocate space for object 'MSmerge_genhistory' in database 'Kreus2_1' because the 'PRIMARY' filegroup is full..
2008-12-17 07:11:56.25 spid3 Recovery complete.
2008-12-17 07:11:56.25 spid3 SQL global counter collection task is created.
2008-12-17 07:11:57.00 spid51 Using 'xpsqlbot.dll' version '2000.80.194' to execute extended stored procedure 'xp_qv'.
2008-12-17 07:12:15.04 spid65 Error: 1105, Severity: 17, State: 2
2008-12-17 07:12:15.04 spid65 Could not allocate space for object 'MSmerge_genhistory' in database 'Kreus2_1' because the 'PRIMARY' filegroup is full..
2008-12-17 07:13:10.79 spid66 Error: 1105, Severity: 17, State: 2
2008-12-17 07:13:10.79 spid66 Could not allocate space for object 'MSmerge_genhistory' in database 'Kreus2_1' because the 'PRIMARY' filegroup is full..
2008-12-17 07:13:13.93 spid76 Using 'xprepl.dll' version '2000.80.760' to execute extended stored procedure 'xp_proxiedmetadata'.
2008-12-17 07:14:12.92 spid67 Error: 1105, Severity: 17, State: 2
The database is accessible and data does not appear to be corrupt. We still have users connected, so I'm waiting for them to get a "cannot grow file" error.
We are in the process of copying the backup to another server and restoring there to see if the problem follows. I'd like to note that this problem is only affecting this one database. I am able to grow/shrink my other db's.
Any ideas??
December 17, 2008 at 8:06 am
Can you please add one data file to primary file group in that case?
December 17, 2008 at 8:13 am
That did it. I don't know why I didn't try that earlier, I even thought about it and dismissed it for some reason.
Thanks!
December 17, 2008 at 8:19 am
it looks like the growth rate is in percentage. Try with fixed size mbs with smaller size say 100 mbs
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply