October 11, 2005 at 8:12 am
Has anyone noticed this type of an error in transactional replication.
The initial snapshot for article <table name> is not yet available.
Few of our prodn tables are not getting replicated to another server. the only diff it had when compared to the once that were working was vertical partioning was set to "TRUE" whereas alll others were "FALSE". now even if we manually set the vertical partition to false except for pk columns the rest were all not selected and filtered out. we tried using GUI and managed to select all columns this time but somehow it doesnt work and now we get this msg. any help on this will be greatly appreciated as this is affecting our systems badly. TIA
October 11, 2005 at 9:48 am
Sounds as though the snapshot job at the publisher has never run, so it can't be sent to the subscriber.
October 11, 2005 at 10:21 am
But all other articles are getting replicated except for a couple of them. Is there something that needs to be checked? thanks
October 11, 2005 at 10:30 am
They're all in the same publication ?? I dunno
October 11, 2005 at 1:15 pm
Yeah close to 23 table son one publication and alll works fne except for couple of table which arent getting replicated. anyone else has seen this happening. TIA
October 12, 2005 at 10:59 pm
Hi Ishaan,
I m also a greenhorn here, but from the way it feels there has to be some relation between vertical partition and key contraints. I came across same problem in Merge Replication. I solved it by keeping the allow null at Foreign Key constraint to false check for constraints at the secondary tables.
Rajesh.
October 12, 2005 at 10:59 pm
Hi Ishaan,
I m also a greenhorn here, but from the way it feels there has to be some relation between vertical partition and key contraints. I came across same problem in Merge Replication. I solved it by keeping the allow null at Foreign Key constraint to false check for constraints at the secondary tables.
Rajesh.
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply