SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Initial snapshot for publication is not yet available


Initial snapshot for publication is not yet available

Author
Message
homebrew01
homebrew01
One Orange Chip
One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)One Orange Chip (29K reputation)

Group: General Forum Members
Points: 29440 Visits: 9222

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





Amit Kumar
Amit Kumar
SSC Veteran
SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)SSC Veteran (280 reputation)

Group: General Forum Members
Points: 280 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





vinod.mallolu
vinod.mallolu
SSC-Enthusiastic
SSC-Enthusiastic (175 reputation)SSC-Enthusiastic (175 reputation)SSC-Enthusiastic (175 reputation)SSC-Enthusiastic (175 reputation)SSC-Enthusiastic (175 reputation)SSC-Enthusiastic (175 reputation)SSC-Enthusiastic (175 reputation)SSC-Enthusiastic (175 reputation)

Group: General Forum Members
Points: 175 Visits: 174
[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.
dbamohsin
dbamohsin
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1140 Visits: 447
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
GilaMonster
GilaMonster
SSC Guru
SSC Guru (550K reputation)SSC Guru (550K reputation)SSC Guru (550K reputation)SSC Guru (550K reputation)SSC Guru (550K reputation)SSC Guru (550K reputation)SSC Guru (550K reputation)SSC Guru (550K reputation)

Group: General Forum Members
Points: 550489 Visits: 47744
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, MVP, M.Sc (Comp Sci)
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


dbamohsin
dbamohsin
Ten Centuries
Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)Ten Centuries (1.1K reputation)

Group: General Forum Members
Points: 1140 Visits: 447
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
Apollo74x
Apollo74x
Say Hey Kid
Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)

Group: General Forum Members
Points: 668 Visits: 423
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
Apollo74x
Apollo74x
Say Hey Kid
Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)Say Hey Kid (668 reputation)

Group: General Forum Members
Points: 668 Visits: 423
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.
tharvesmohideen
tharvesmohideen
Say Hey Kid
Say Hey Kid (696 reputation)Say Hey Kid (696 reputation)Say Hey Kid (696 reputation)Say Hey Kid (696 reputation)Say Hey Kid (696 reputation)Say Hey Kid (696 reputation)Say Hey Kid (696 reputation)Say Hey Kid (696 reputation)

Group: General Forum Members
Points: 696 Visits: 400
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
azhar.iqbal499
azhar.iqbal499
SSCommitted
SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)SSCommitted (1.6K reputation)

Group: General Forum Members
Points: 1556 Visits: 529
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
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search