question

sql_hunter avatar image
sql_hunter asked

Replication error: There is not enough space on the disk

I have added a new table in the replication article. and reinitialized the subscription and ticked to create a new snapshot. however, I am getting error 'There is not enough space on the disk'. further analysis i have noticed in the error log the below: Replication-Replication Snapshot Subsystem: agent * scheduled for retry. The replication agent had encountered an exception. Source: Replication Exception Type: Microsoft.SqlServer.Replication.NativeSqlConnectionException Exception Message: There is not enough space on the disk. Message Code: 0 I have experienced this issue before several times. I have resolved this type of issue by simply deleting the snapshot from \\\\Relpdata\\unc\\. But this time this trick is not working. Can any explain the reason of this error and the solution of this. I thought it is a connection error. So I tried to setup the security parameters and rerun the snapshot creation. but it did not help me.
replicationerror message
2 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Forgive me, but is there indeed enough space on the physical disk for the snapshot? How much free space does the drive have?
2 Likes 2 ·
more than 50 GB. Where my database size is something around 15GB datafile. around 10 GB Index file.
0 Likes 0 ·
sql_hunter avatar image
sql_hunter answered
Thank you all for your help. I have resolved this issue. It was really a disk space issue. I checked the compressed option in the snapshot location. there is a limit the compress cabinet, which is something around 2.7 GB. My compressed snapshot was exceeding that limit. Though i had enough space available in the disk. When I unticked that it created the snapshot and replication work normally. One thing is still unknown to me is why the Backward_comp_level = 40. i thought it should be 100 as i am using SQL 2008r2. If anyone can answer, please.
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

NeerajTripathi avatar image
NeerajTripathi answered
It seems that snapshot generated from addition of article with old snapshot ate all space and deletion of old snapshot depends on distribution retention period that is configured on distribution properties. Also, it's better to generate the snapshot of only added articles despite of generation of complete database snapshot by disabling publication properties(immediate_sync , allow_anonymous). Please check the below link. http://saveadba.blogspot.in/2011/08/adding-new-article-without-generating.html
2 comments
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

It has not resolved the issue yet. I had check there was nothing in the location \\\\repldata\\unc\\ . I have tried your suggestion to add single article and run the snapshot from job monitor (followed your link http://saveadba.blogspot.in/2011/08/adding-new-article-without-generating.html). Still getting same error 'There is not enough space on the disk'. Also the snapshot is generating for all the article, though i followed the above link to generate it only for the single article.
0 Likes 0 ·
sp_helpsubscription running this sp, i have noticed that the subscription_status = 3. What is the meaning of 3. i know this value should be either 0,1 or 3. sp_helppublication running this, noticed Backward_comp_level = 40. i was expecting 100, as i am using sql 2008r2. Also how much space does the snapshort requires? Any comment on these?
0 Likes 0 ·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.