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 |
|
AnitaDBA2010
Starting Member
18 Posts |
 Posted - 2011-01-13 : 16:15:22
|
| Hi All-We are seeing some issue with publicationWhen i launch replicaiton monitor, i see that status of pulications is 'Retrying failed command'And when i look under the Agent Tab, and open the job snapshot agent which has a status 'Retrying failed command', the last action message is below. Can anyone guide how to fix this issue?Message: There is not enough space on the disk.Stack: at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.ThrowNativeBcpOutException(CConnection* pNativeConnectionWrapper)at Microsoft.SqlServer.Replication.Snapshot.SqlServer.NativeBcpOutProvider.BcpOut(String strBcpObjectName, String strBcpObjectOwner, String strBaseBcpObjectName, Boolean fUnicodeConversion, String strDataFile, String strLoadOrderingHint, String strWhereClause, Boolean useTableLockHint, Int32 bcpFileFormatVersion)at Microsoft.SqlServer.Replication.Snapshot.SqlServer.BcpOutThreadProvider.DoWork(WorkItem workItem)at Microsoft.SqlServer.Replication.WorkerThread.NonExceptionBasedAgentThreadProc()at Microsoft.SqlServer.Replication.AgentCore.BaseAgentThread.AgentThreadProcWrapper() (Source: MSSQLServer, Error number: 0)Publication Type: TransactionalThanksAnitaAnita |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
AnitaDBA2010
Starting Member
18 Posts |
Posted - 2011-01-13 : 16:36:37
|
| Thanks Tara. i figured that out of from the error message. but where do look we for the disk space so that we can fix it ? I am not navigate where this disk space is lessRegardsAnitaAnita |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
AnitaDBA2010
Starting Member
18 Posts |
Posted - 2011-01-13 : 18:10:22
|
Thanks Tara,Now i see that error message is gone and the publication status is ok. But i see the new critical error for subscription under subscription watch list which saysThe concurrent snapshot for publication 'MASHProduction' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent for the publication should be startedI believe right now There might be tomany logs to write in subcription and It will create a snapshot and dump everything to Subscrib db , so i will need to wait till it finishes. DB size is 8 GM ThanksAnitaquote:
Originally posted by tkizer
Look at all of your drives.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog
Anita |
|
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2011-01-13 : 20:29:49
|
| You need to (1) determine where the snapshot folder is, which you can find under properties in replication monitor and (2) as Tara said, free up some disk space.I seriously doubt that waiting is going to help. In fact, since the agent isn't running, there is nothing to wait for. The snapshot didn't finish because you ran out of disk space. And it's not going to try again until you restart it (unless it is scheduled -- which it shouldn't be, unless it's a snapshot publication).Free up disk space, then re-run snapshot agent, then resynch the subscriptions. |
|
|
|
AnitaDBA2010
Starting Member
18 Posts |
Posted - 2011-01-13 : 21:01:06
|
| Thanks Tara and russell.I created a new replication set up as i was advised the current one had issues all the time. the issue persist today even aft6er freeing space. so finally i had to create a new set upthe replication looks good now with no issues and low latency , i will monitor it few days and see how it goesThanksAnitaAnita |
|
|
|
|
|
|
|
|
Publication issue