Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Initial snapshot for publication is not yet available Expand / Collapse
Author
Message
Posted Monday, February 5, 2007 11:07 PM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: 2 days ago @ 9:18 PM
Points: 2,834, Visits: 8,543

I'm not sure why my transactional replication is giving me:  "The initial snapshot for publication 'XYZ' is not yet available."   I have 1 publication going to 3 subscribers on different servers. After creating new subscriptions on Subscriber #3, the subscriptions on Subscriber #1 stopped pulling new data (was running fine for months)

Does re-creating a snapshot at the publisher, to go to a new subscriber have an effect on my long running original subscription ?? 

I reinitialized the subscription on subscriber #1, re-ran the snapshot at the publisher, then when it finished, I re-ran the subscription pull job. at subscriber #1. It completes normally, but finishes in just a few seconds & does nothing. It seems I have to drop the subscription and re-create it.

Any thoughts




Post #342644
Posted Tuesday, February 6, 2007 12:13 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, September 29, 2010 4:02 AM
Points: 28, Visits: 22

Hi

Re-generate snapshot and execute it for the subscriber #1. If it does not work, drop & re-create subscription. Then it will work.

Amit




Post #342651
Posted Friday, September 12, 2008 1:02 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, July 5, 2013 7:55 AM
Points: 1, Visits: 91
[size="7"][/size]

this error will come because of lack of paging memory in the selected drive.

ask your system engineer to check the paging drive memory. and ask him to chenge the drive to a drive which has more memory, or ask him to delete unnecessary data from the paging selected drive.

this solution worked for me.
Post #568292
Posted Monday, October 27, 2008 11:31 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Friday, April 11, 2014 4:21 AM
Points: 97, Visits: 392
can anyone confirm the above reply? i had a similar issue in that after about 65 attempts to retry the transaction, no more retries were attempted, and the distribution agent gave the "The initial snapshot for publication '' is not yet available" error.

Does this have something to do with replication deciding that the subscription needs to be reinitialised?



My DBA Ramblings - SQL Server | Oracle | MySQL | MongoDB | Access
Post #592298
Posted Monday, October 27, 2008 11:38 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 1:43 PM
Points: 40,411, Visits: 36,861
Mohsin Patel (10/27/2008)

Does this have something to do with replication deciding that the subscription needs to be reinitialised?


If the subscription gets reinitialised, a new snapshot must be generated. The distribution agent will give that error until a fresh snapshot is available.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #592306
Posted Tuesday, October 28, 2008 3:20 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Friday, April 11, 2014 4:21 AM
Points: 97, Visits: 392
Hi,

i'm trying to find out why the subscription would be marked for reintialisation? the attempts to run the transaction were over a period of about 2 hours - no where near the retention period.

It seemed really random that the attempts the Dist. agent was making to run that transaction stopped and the message changed to the ;initial snapshot for publication is not yet available'



My DBA Ramblings - SQL Server | Oracle | MySQL | MongoDB | Access
Post #592688
Posted Friday, November 14, 2008 11:54 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, September 15, 2014 9:56 AM
Points: 78, Visits: 344
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=626299&SiteID=1

Apparently using replication monitor causes this problem. I'm going to reiniatalize our replication tonight, not use replicaton monitor for a week and see if this is really the problem.

James
Post #603000
Posted Wednesday, December 17, 2008 11:13 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, September 15, 2014 9:56 AM
Points: 78, Visits: 344
Apollo74x (11/14/2008)
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=626299&SiteID=1

Apparently using replication monitor causes this problem. I'm going to reiniatalize our replication tonight, not use replicaton monitor for a week and see if this is really the problem.

James


FYI - I have not had any issues since I stopped using replication monitor.
Post #621484
Posted Tuesday, June 23, 2009 6:29 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Saturday, September 13, 2014 10:52 PM
Points: 336, Visits: 379
HI All,

I also faced the same error once. This is raised if the distributor retries to connect the subscriber few times and markes with this error.

To resolve this what I followed are;
stop the agent first.
right click on publication and start the snapshot agent.
Once it sompleted, now you start the distribution agent.
It will reinitialize the subscriber and problem gets solved.

This is ok for few records or with high banded network connection. But for huge records about millions of records then it will affect all other groups.

So I am trying with new option, if i could succeeded I will post the steps i followed.

regards,
Tharves
Post #740092
Posted Monday, June 20, 2011 1:50 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, November 20, 2014 5:50 AM
Points: 140, Visits: 455
I am facing same sort of problem. Please tell me where to start Distribution agent. I am not able to find exact screen at the distributor from where I can run/stop Distribution agent. I only find Log and snapshot agent there.
Thanks
Post #1128013
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse