|
|
You're in the
sql server replication
group:replication is pending mode
sql server replication:
job owner in SQL Server Agent, Jobs and then run it manually? Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book: =
Kevin,
try changing the job owner to sa and then run the job. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book:
hi guys,
Publication is in pending status. I don't know what is the problem.. = I am using DOMAIN account(administrator). Publisher and subscriber are = on same machine. =20 Error I got in my event viewer. SQL Server Scheduled Job 'Replication agents checkup' = (0xF2F0DE84FCFB1B46A009419F676E83A9) - Status: Failed - Invoked on: = 2005-09-20 10:40:01 - Message: The job failed. Unable to determine if = the owner (CORP\user) of job Replication agents checkup has server = access (reason: Could not obtain information about Windows NT group/user =
but it's under pending mode.
[quoted text, click to view] "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message = Kevin,news:e2KvrjfvFHA.3500@TK2MSFTNGP09.phx.gbl... try changing the job owner to sa and then run the job. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book:
now it's active.
Could you tell me what is difference between reinitialize subscription = and synchronize? is that almost the same thing? I'm assuming reinitialize subscription will refresh all the data, and synchronize is just download the latest data. [quoted text, click to view] "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message = Kevin - I'm not too sure what's happening here - can't you change the =news:eXJhGhgvFHA.2076@TK2MSFTNGP14.phx.gbl... job owner in SQL Server Agent, Jobs and then run it manually? Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book: =
Kevin wrote on Wed, 21 Sep 2005 10:26:34 -0400:
[quoted text, click to view] > Since it's in active mode, and I'm using transaction replication, > I did a test. I change column defintion for one of the column on > publisher, and when I go to subscriber, how come I don't see the change? > I also wait about 12 hours, it is still not there. Is it because it's > depending on schedule? how do I force the synchronization? Did you make the change using ALTER TABLE, or via the the sp_repladdcolumn/sp_repldropcolumn procs or replication properties dialogs in EM?. Check BOL for "Schema Changes on Publication Databases", according to that ALTER TABLE changes to the schema are not replicated (I think I read that SQL Server 2005 will be able to do this though). Dan
Kevin,
reinitialize will require that a new snapshot be generated and sent down = to the subscriber as a set of odbcBCP files. On the other hand, = synchronize will run the distribution/merge agent and send down the = latest changes. For merge the flow of data is in both directions and is = just pub -> sub for normal transactional replication. In the case of = snapshot replication, synchronization and reinitialization are quite = similar, but there's a big difference for the other methods. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book:
Since it's in active mode, and I'm using transaction replication,=20
I did a test. I change column defintion for one of the column on = publisher, and when I go to subscriber, how come I don't see the change? = I also wait about 12 hours, it is still not there. Is it because it's = depending on schedule? how do I force the synchronization? [quoted text, click to view] "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message = Kevin,news:uMDS2PovFHA.2008@TK2MSFTNGP10.phx.gbl... reinitialize will require that a new snapshot be generated and sent = down to the subscriber as a set of odbcBCP files. On the other hand, = synchronize will run the distribution/merge agent and send down the = latest changes. For merge the flow of data is in both directions and is = just pub -> sub for normal transactional replication. In the case of = snapshot replication, synchronization and reinitialization are quite = similar, but there's a big difference for the other methods. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book:
YES. I changed it using alter table using following script. but I =
drop the article and then alter table, AND THEN I re-add article back = in publication. SO even that method won't work? altering the subscriptions =20 exec sp_dropsubscription @publication =3D 'tTestFNames'=20 , @article =3D 'tEmployees'=20 , @subscriber =3D 'RSCOMPUTER' , @destination_db =3D 'testrep'=20 =20 exec sp_droparticle @publication =3D 'tTestFNames' , @article =3D 'tEmployees' =20 --- Change column definition alter table tEmployees alter column Forename varchar(100) null =20 exec sp_addarticle @publication =3D 'tTestFNames'=20 , @article =3D 'tEmployees'=20 , @source_table =3D 'tEmployees'=20 =20 exec sp_addsubscription @publication =3D 'tTestFNames' , @article =3D 'tEmployees' , @subscriber =3D 'RSCOMPUTER'=20 , @destination_db =3D 'testrep'=20 [quoted text, click to view] "Daniel Crichton" <msnews@worldofspack.co.uk> wrote in message =
news:uYj2fPsvFHA.2132@TK2MSFTNGP15.phx.gbl... > Kevin wrote on Wed, 21 Sep 2005 10:26:34 -0400: >=20 >> Since it's in active mode, and I'm using transaction replication, >> I did a test. I change column defintion for one of the column on >> publisher, and when I go to subscriber, how come I don't see the = change? >> I also wait about 12 hours, it is still not there. Is it because = it's >> depending on schedule? how do I force the synchronization? >=20 > Did you make the change using ALTER TABLE, or via the the=20 > sp_repladdcolumn/sp_repldropcolumn procs or replication properties = dialogs=20 > in EM?. Check BOL for "Schema Changes on Publication Databases", = according=20 > to that ALTER TABLE changes to the schema are not replicated (I think = I read=20 > that SQL Server 2005 will be able to do this though). >=20 > Dan=20 >=20
This is OK - if you're using transactional replication, you'll also need =
to run the snapshot then the distribution agents for it to go over. = Also, Daniel's quite right that this type of tinkering is supported = directly using the 'Replicate Schema Changes' option on the subscription = options pane of SQL Server 2005 (by default is enabled). Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book:
Kevin,
this isn't necessarily true - some people run the distribution agent = continuously, some on a schedule. It depends on the latency you want, = and the load you want to put your servers under, so your setup might be = optimized for your purposes. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book:
hi paul,=20
When I forced the replication to run by "run agent now" under Status = tab, I saw Distribution Agent has some errors on Replication Monitor. = Session timeout is the error message. I realized that distribution = agent is not started. So I started the distribution agent. I'm = assuming replication will now work. I'm a little confused about the process. I just want to know why Distribute agent was stopped in the first place. = Is it because I must manually start the distribute agent service when I = force a replication? And since it is transactional replication, shouldn't distribute agent = service always up and running? [quoted text, click to view] "Paul Ibison" <Paul.Ibison@Pygmalion.Com> wrote in message = This is OK - if you're using transactional replication, you'll also =news:uoQGAEuvFHA.460@TK2MSFTNGP15.phx.gbl... need to run the snapshot then the distribution agents for it to go over. = Also, Daniel's quite right that this type of tinkering is supported = directly using the 'Replicate Schema Changes' option on the subscription = options pane of SQL Server 2005 (by default is enabled). Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book:
hey paul.
you told me to use sa account to solve this problem before. but I don't understand something, when I use domain account to do = replication,=20 it's in pending mode for publication, but once I use sa account to do=20 replication, then it's in active mode. =20 Both of my servers are running on my local machine, and both server and = sql agents are running under my domain account. why can't I use domain account to=20
Kevin,
I think you should be able to and this is a bug of some sort which is = preventing validation of domain user accounts. As you have a workaround = it's probably not worth getting PSS involved, but if you do, please let = us know the outcome. Cheers, Paul Ibison SQL Server MVP, www.replicationanswers.com (recommended sql server 2000 replication book:
Don't see what you're looking for? Try a search.
|
April 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |