SQLServerCentral / SQL Server 7,2000 / Replication / Initial snapshot for publication is not yet available / Latest Posts

RE: Initial snapshot for publication is not yet available

Neeraj Dwivedi — Wed, 17 Apr 2013 08:39:06 GMT

Look into Distributor's sql agent jobs.

RE: Initial snapshot for publication is not yet available

amit.kini — Sun, 04 Nov 2012 23:27:33 GMT

We have a MS SQL DB server for Cricket DB .The requirement is to Enable a Oracle Subscription for a sql server Publisher on our cricket DB, so that we can send live updates in real time.I am facing an issue while configuring the subscription.This is what I have tried:1. Configured a sql server publication with articles2. Tried to configure an Oracle subscriber to publication configured in step 1 but seems like the Data source Name is not being recognized by the sql server.It does say the subscription is configured but it gives error while initializing the snapshot.Any idea on what could be going wrong here?Also, one issue here is, I think it looks for TNSNAMES.ORA file for the data source name that I provide. I have sql developer as the oracle client and I don’t connect using the TNS name.In this case where do I need to place the TNSNAMES.ora file? Any thoughts on this would be appreciated. Also if you are aware of any alternate way to approach this it would be helpful. Please advise.

RE: Initial snapshot for publication is not yet available

mohammed moinudheen — Mon, 20 Jun 2011 07:32:11 GMT

[quote][b]azhar.iqbal499 (6/20/2011)[/b][hr]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[/quote]Please don't cross post as the issue you are facing is being followed in this link.http://www.sqlservercentral.com/Forums/Topic1128015-391-1.aspx

RE: Initial snapshot for publication is not yet available

azhar.iqbal499 — Mon, 20 Jun 2011 01:50:57 GMT

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

RE: Initial snapshot for publication is not yet available

tharvesmohideen — Tue, 23 Jun 2009 06:29:15 GMT

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

RE: Initial snapshot for publication is not yet available

Apollo74x — Wed, 17 Dec 2008 11:13:24 GMT

[quote][b]Apollo74x (11/14/2008)[/b][hr]http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=626299&SiteID=1Apparently 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[/quote]FYI - I have not had any issues since I stopped using replication monitor.

RE: Initial snapshot for publication is not yet available

Apollo74x — Fri, 14 Nov 2008 11:54:26 GMT

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=626299&SiteID=1Apparently 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

RE: Initial snapshot for publication is not yet available

dbamohsin — Tue, 28 Oct 2008 03:20:25 GMT

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'

RE: Initial snapshot for publication is not yet available

GilaMonster — Mon, 27 Oct 2008 11:38:54 GMT

[quote][b]Mohsin Patel (10/27/2008)[/b][hr]Does this have something to do with replication deciding that the subscription needs to be reinitialised? [/quote]If the subscription gets reinitialised, a new snapshot must be generated. The distribution agent will give that error until a fresh snapshot is available.

RE: Initial snapshot for publication is not yet available

dbamohsin — Mon, 27 Oct 2008 11:31:28 GMT

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?

RE: Initial snapshot for publication is not yet available

vinod.mallolu — Fri, 12 Sep 2008 01:02:52 GMT

[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.

RE: Initial snapshot for publication is not yet available

Amit Kumar — Tue, 06 Feb 2007 00:13:00 GMT

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

Amit

Initial snapshot for publication is not yet available

homebrew01 — Mon, 05 Feb 2007 23:07:00 GMT

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