yes i validated the publication after adding the articles.
The publication is valid., still getting the error in creating the subsciption.
Main Topics
Browse All TopicsHi,
I have 2 rep servers REP_TEST1 and REP_TEST2. The routes have been defined from REP_TEST1 to REP_TEST2 and vice versa. Now i am trying to test the scenerio of publication/subscription. I created a test database on 2 ASE'S. test on ASE1 and test on ASE2.
I created 2 tables t1 and t2 in test1 of ASE1 and ASE2. I created the replication def for t1 and t2 on REP_TEST1. Then i created the publication and then added the articles (2 tables ) into the publication.
Now when i create the subscription on REP_TEST2 i am getting the following error:
1> define subscription test_sub_for_pub_1
2> for publication test_pub_1
3> with primary at SYB_ASE1.test
4> with replicate at SYB_ASE2.test
5> for new articles
6> go
Msg 15359, Level 12, State 0:
Server 'REP_TEST2':
Subscription test_sub_for_pub_1 for the publication does not exist for this replicate database.
could someone please tell me why i am geting this error. Both the test databases have been configured with the rep servers and normal table/subscrption replication is working there. Publication/subscription mehtod is giving the above error.
Thanks
Deepak
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
>What happens when you run check publication at both RepServers?
It says publication is valid on both rep servers
"Publication test_pub_1 for SYB_ASE1.test is valid. The number of articles in the publication is 2."
>What happens if you just use create subscription instead of define/activate/validate?
normal subscriptions for table rep def are working fine. and getting created.
>Do the tables exist in ASE2?
yes both the tables exist in ASE2
No, I mean creating the subscription to the publication as the single-command
create subscription sub_name for publication pub_name
rather than three commands: define / activate / validate
You can do this for repdef subscriptions *and* for publication subscriptions.
Also - the snippet you gave us in your original post - is that an exact copy/paste? Because first you say the databases are called "test1" but your "define subscription" command calls them "test".
Lastly, try just running a check subscription (at the replicate RS).
Business Accounts
Answer for Membership
by: Joe_WoodhousePosted on 2009-08-26 at 22:40:20ID: 25194889
Did you validate the publication first?
om/help/in dex.jsp?to pic=/ com.s ybase.info center.hel p.rs.15.2/ title.htm
"Creating an article invalidates the publication, which makes it ineligible for subscription. After you create an article, you must change the status of the publication to VALID, using validate publication, before you can create subscriptions against it."
From the Replication Server Admin Guide vol. 1... available at
http://infocenter.sybase.c
I can't imagine trying to do anything in RepServer for the first time without this manual (and the Reference Guide) constantly open...