|
|
You're in the
sql server replication
group:The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated.
sql server replication:
Got the error and not too sure why
"The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated." Its strange.. A lot of my subscriptions have been throwing the error of late on a particular server. Why does it happen ? I know the distribution agents have been running or should be running . Its too late now to find out as its already errored out Do let me know all possible reason for why it may occur. Using transactional replication with SQL 2000
History retention period of what ? Are you referring to the no. of hrs ,
commands remain in the distribution db if they do not get distributed ? If so, i believe its the default of 72 hrs [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:%236OqWUprFHA.1028@TK2MSFTNGP12.phx.gbl... > what is your history retention period? If it is less than your retention > this can trigger the error. > > -- > Hilary Cotter > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > "Hassan" <hassanboy@hotmail.com> wrote in message > news:eigeWsmrFHA.3888@TK2MSFTNGP10.phx.gbl... >> Got the error and not too sure why >> >> "The subscription(s) have been marked inactive and must be reinitialized. >> NoSync subscriptions will need to be dropped and recreated." >> >> Its strange.. A lot of my subscriptions have been throwing the error of > late >> on a particular server. >> >> Why does it happen ? I know the distribution agents have been running or >> should be running . Its too late now to find out as its already errored > out >> >> Do let me know all possible reason for why it may occur. Using > transactional >> replication with SQL 2000 >> >> > >
what is your history retention period? If it is less than your retention
this can trigger the error. -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Hassan" <hassanboy@hotmail.com> wrote in message news:eigeWsmrFHA.3888@TK2MSFTNGP10.phx.gbl... > Got the error and not too sure why > > "The subscription(s) have been marked inactive and must be reinitialized. > NoSync subscriptions will need to be dropped and recreated." > > Its strange.. A lot of my subscriptions have been throwing the error of late > on a particular server. > > Why does it happen ? I know the distribution agents have been running or > should be running . Its too late now to find out as its already errored out > > Do let me know all possible reason for why it may occur. Using transactional > replication with SQL 2000 > >
Right click on Replication Monitor, select Distributor Properties, click the
properties button. Note the History Retention group. Set it there. -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Hassan" <hassanboy@hotmail.com> wrote in message news:u0YOYpqrFHA.1168@TK2MSFTNGP10.phx.gbl... > History retention period of what ? Are you referring to the no. of hrs , > commands remain in the distribution db if they do not get distributed ? If > so, i believe its the default of 72 hrs > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:%236OqWUprFHA.1028@TK2MSFTNGP12.phx.gbl... > > what is your history retention period? If it is less than your retention > > this can trigger the error. > > > > -- > > Hilary Cotter > > Looking for a SQL Server replication book? > > http://www.nwsu.com/0974973602.html > > > > Looking for a FAQ on Indexing Services/SQL FTS > > http://www.indexserverfaq.com > > "Hassan" <hassanboy@hotmail.com> wrote in message > > news:eigeWsmrFHA.3888@TK2MSFTNGP10.phx.gbl... > >> Got the error and not too sure why > >> > >> "The subscription(s) have been marked inactive and must be reinitialized. > >> NoSync subscriptions will need to be dropped and recreated." > >> > >> Its strange.. A lot of my subscriptions have been throwing the error of > > late > >> on a particular server. > >> > >> Why does it happen ? I know the distribution agents have been running or > >> should be running . Its too late now to find out as its already errored > > out > >> > >> Do let me know all possible reason for why it may occur. Using > > transactional > >> replication with SQL 2000 > >> > >> > > > > > >
There is 72 hrs for transaction retention and 48 hrs for history retention
.. But I dont understand what needs to trigger to inactivate ? [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:uv4diHurFHA.3596@TK2MSFTNGP15.phx.gbl... > Right click on Replication Monitor, select Distributor Properties, click > the > properties button. Note the History Retention group. Set it there. > > -- > Hilary Cotter > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > "Hassan" <hassanboy@hotmail.com> wrote in message > news:u0YOYpqrFHA.1168@TK2MSFTNGP10.phx.gbl... >> History retention period of what ? Are you referring to the no. of hrs , >> commands remain in the distribution db if they do not get distributed ? >> If >> so, i believe its the default of 72 hrs >> >> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >> news:%236OqWUprFHA.1028@TK2MSFTNGP12.phx.gbl... >> > what is your history retention period? If it is less than your >> > retention >> > this can trigger the error. >> > >> > -- >> > Hilary Cotter >> > Looking for a SQL Server replication book? >> > http://www.nwsu.com/0974973602.html >> > >> > Looking for a FAQ on Indexing Services/SQL FTS >> > http://www.indexserverfaq.com >> > "Hassan" <hassanboy@hotmail.com> wrote in message >> > news:eigeWsmrFHA.3888@TK2MSFTNGP10.phx.gbl... >> >> Got the error and not too sure why >> >> >> >> "The subscription(s) have been marked inactive and must be > reinitialized. >> >> NoSync subscriptions will need to be dropped and recreated." >> >> >> >> Its strange.. A lot of my subscriptions have been throwing the error >> >> of >> > late >> >> on a particular server. >> >> >> >> Why does it happen ? I know the distribution agents have been running > or >> >> should be running . Its too late now to find out as its already >> >> errored >> > out >> >> >> >> Do let me know all possible reason for why it may occur. Using >> > transactional >> >> replication with SQL 2000 >> >> >> >> >> > >> > >> >> > >
Hilary,
I understand the transaction retention period. Whats the history period about .. and how would that affect replication even if its past the 48 hrs. It says it keeps track of replication performance. What peformance does it keep track of and where ? [quoted text, click to view] "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message news:u6YTXL2rFHA.308@TK2MSFTNGP10.phx.gbl... >A subscriber is expired when the either the history or the transaction > retention period is elapsed. > > You may be bumping into this problem. > > http://support.microsoft.com/default.aspx?scid=kb;en-us;823649 > > > -- > Hilary Cotter > Looking for a SQL Server replication book? > http://www.nwsu.com/0974973602.html > > Looking for a FAQ on Indexing Services/SQL FTS > http://www.indexserverfaq.com > "Hassan" <hassanboy@hotmail.com> wrote in message > news:eKuhpq0rFHA.3352@TK2MSFTNGP14.phx.gbl... >> There is 72 hrs for transaction retention and 48 hrs for history > retention >> . >> >> But I dont understand what needs to trigger to inactivate ? >> >> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >> news:uv4diHurFHA.3596@TK2MSFTNGP15.phx.gbl... >> > Right click on Replication Monitor, select Distributor Properties, >> > click >> > the >> > properties button. Note the History Retention group. Set it there. >> > >> > -- >> > Hilary Cotter >> > Looking for a SQL Server replication book? >> > http://www.nwsu.com/0974973602.html >> > >> > Looking for a FAQ on Indexing Services/SQL FTS >> > http://www.indexserverfaq.com >> > "Hassan" <hassanboy@hotmail.com> wrote in message >> > news:u0YOYpqrFHA.1168@TK2MSFTNGP10.phx.gbl... >> >> History retention period of what ? Are you referring to the no. of hrs > , >> >> commands remain in the distribution db if they do not get distributed >> >> ? >> >> If >> >> so, i believe its the default of 72 hrs >> >> >> >> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message >> >> news:%236OqWUprFHA.1028@TK2MSFTNGP12.phx.gbl... >> >> > what is your history retention period? If it is less than your >> >> > retention >> >> > this can trigger the error. >> >> > >> >> > -- >> >> > Hilary Cotter >> >> > Looking for a SQL Server replication book? >> >> > http://www.nwsu.com/0974973602.html >> >> > >> >> > Looking for a FAQ on Indexing Services/SQL FTS >> >> > http://www.indexserverfaq.com >> >> > "Hassan" <hassanboy@hotmail.com> wrote in message >> >> > news:eigeWsmrFHA.3888@TK2MSFTNGP10.phx.gbl... >> >> >> Got the error and not too sure why >> >> >> >> >> >> "The subscription(s) have been marked inactive and must be >> > reinitialized. >> >> >> NoSync subscriptions will need to be dropped and recreated." >> >> >> >> >> >> Its strange.. A lot of my subscriptions have been throwing the >> >> >> error >> >> >> of >> >> > late >> >> >> on a particular server. >> >> >> >> >> >> Why does it happen ? I know the distribution agents have been > running >> > or >> >> >> should be running . Its too late now to find out as its already >> >> >> errored >> >> > out >> >> >> >> >> >> Do let me know all possible reason for why it may occur. Using >> >> > transactional >> >> >> replication with SQL 2000 >> >> >> >> >> >> >> >> > >> >> > >> >> >> >> >> > >> > >> >> > >
A subscriber is expired when the either the history or the transaction
retention period is elapsed. You may be bumping into this problem. http://support.microsoft.com/default.aspx?scid=kb;en-us;823649 -- Hilary Cotter Looking for a SQL Server replication book? http://www.nwsu.com/0974973602.html Looking for a FAQ on Indexing Services/SQL FTS http://www.indexserverfaq.com [quoted text, click to view] "Hassan" <hassanboy@hotmail.com> wrote in message news:eKuhpq0rFHA.3352@TK2MSFTNGP14.phx.gbl... > There is 72 hrs for transaction retention and 48 hrs for history retention > . > > But I dont understand what needs to trigger to inactivate ? > > "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > news:uv4diHurFHA.3596@TK2MSFTNGP15.phx.gbl... > > Right click on Replication Monitor, select Distributor Properties, click > > the > > properties button. Note the History Retention group. Set it there. > > > > -- > > Hilary Cotter > > Looking for a SQL Server replication book? > > http://www.nwsu.com/0974973602.html > > > > Looking for a FAQ on Indexing Services/SQL FTS > > http://www.indexserverfaq.com > > "Hassan" <hassanboy@hotmail.com> wrote in message > > news:u0YOYpqrFHA.1168@TK2MSFTNGP10.phx.gbl... > >> History retention period of what ? Are you referring to the no. of hrs , > >> commands remain in the distribution db if they do not get distributed ? > >> If > >> so, i believe its the default of 72 hrs > >> > >> "Hilary Cotter" <hilary.cotter@gmail.com> wrote in message > >> news:%236OqWUprFHA.1028@TK2MSFTNGP12.phx.gbl... > >> > what is your history retention period? If it is less than your > >> > retention > >> > this can trigger the error. > >> > > >> > -- > >> > Hilary Cotter > >> > Looking for a SQL Server replication book? > >> > http://www.nwsu.com/0974973602.html > >> > > >> > Looking for a FAQ on Indexing Services/SQL FTS > >> > http://www.indexserverfaq.com > >> > "Hassan" <hassanboy@hotmail.com> wrote in message > >> > news:eigeWsmrFHA.3888@TK2MSFTNGP10.phx.gbl... > >> >> Got the error and not too sure why > >> >> > >> >> "The subscription(s) have been marked inactive and must be > > reinitialized. > >> >> NoSync subscriptions will need to be dropped and recreated." > >> >> > >> >> Its strange.. A lot of my subscriptions have been throwing the error > >> >> of > >> > late > >> >> on a particular server. > >> >> > >> >> Why does it happen ? I know the distribution agents have been running > > or > >> >> should be running . Its too late now to find out as its already > >> >> errored > >> > out > >> >> > >> >> Do let me know all possible reason for why it may occur. Using > >> > transactional > >> >> replication with SQL 2000 > >> >> > >> >> > >> > > >> > > >> > >> > > > > > >
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 |