|
security
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Design Master Unavailable in Replica SetI have a single replica of a database on my server. The design master of this
database was located on another server, but this server was shut down. No other replicas exist. Obviously the replica cannot synchronise with the DM anymore. I now want to make my replica the new design master, but I cannot get this to work since I cannot seem to remove the old design master from the replica list. When I do try to synchronise the replica with the DM, I get an error message saying that the DM-database cannot be found and will be deleted from the replica list. However, when I go into "synchronise now" again, the DM-datbase is still in the set. What do I have to do to get this resolved. Any help much appreciated You need to turn this replica into the design master. Tools, Replication,
Recover design master. -- Show quoteHide quoteJoan Wild Microsoft Access MVP Stof wrote: > I have a single replica of a database on my server. The design master > of this database was located on another server, but this server was > shut down. No other replicas exist. Obviously the replica cannot > synchronise with the DM anymore. I now want to make my replica the > new design master, but I cannot get this to work since I cannot seem > to remove the old design master from the replica list. > When I do try to synchronise the replica with the DM, I get an error > message saying that the DM-database cannot be found and will be > deleted from the replica list. However, when I go into "synchronise > now" again, the DM-datbase is still in the set. > > What do I have to do to get this resolved. > > Any help much appreciated
Show quote
Hide quote
"Joan Wild" <jwild@nospamtyenet.com> wrote in And after doing that, create a new replica and transfer DM status tonews:OF5cj6fHHHA.4056@TK2MSFTNGP03.phx.gbl: > Stof wrote: >> I have a single replica of a database on my server. The design >> master of this database was located on another server, but this >> server was shut down. No other replicas exist. Obviously the >> replica cannot synchronise with the DM anymore. I now want to >> make my replica the new design master, but I cannot get this to >> work since I cannot seem to remove the old design master from the >> replica list. When I do try to synchronise the replica with the >> DM, I get an error message saying that the DM-database cannot be >> found and will be deleted from the replica list. However, when I >> go into "synchronise now" again, the DM-datbase is still in the >> set. >> >> What do I have to do to get this resolved. > > You need to turn this replica into the design master. Tools, > Replication, Recover design master. it, so that your production replica (the one that's always being used for data editing) is not your DM. The minimum proper number of replicas in any replica set is THREE: 1. Design Master *NOT* for editing 2. Replica1 for editing 3. Replica2 for editing It's just a bad idea to use your DM for anything but making schema changes. Joan / David,
Thanks for your reply. When I try "Recover Design Master", I get the error message "The value specified is not a ReplicaID for any member in the replica set." and nothing happens. Perhaps this is caused by the original DM still being in the replica set (but no longer available)? Any more thoughts? Show quoteHide quote "David W. Fenton" wrote: > "Joan Wild" <jwild@nospamtyenet.com> wrote in > news:OF5cj6fHHHA.4056@TK2MSFTNGP03.phx.gbl: > > > Stof wrote: > >> I have a single replica of a database on my server. The design > >> master of this database was located on another server, but this > >> server was shut down. No other replicas exist. Obviously the > >> replica cannot synchronise with the DM anymore. I now want to > >> make my replica the new design master, but I cannot get this to > >> work since I cannot seem to remove the old design master from the > >> replica list. When I do try to synchronise the replica with the > >> DM, I get an error message saying that the DM-database cannot be > >> found and will be deleted from the replica list. However, when I > >> go into "synchronise now" again, the DM-datbase is still in the > >> set. > >> > >> What do I have to do to get this resolved. > > > > You need to turn this replica into the design master. Tools, > > Replication, Recover design master. > > And after doing that, create a new replica and transfer DM status to > it, so that your production replica (the one that's always being > used for data editing) is not your DM. > > The minimum proper number of replicas in any replica set is THREE: > > 1. Design Master *NOT* for editing > > 2. Replica1 for editing > > 3. Replica2 for editing > > It's just a bad idea to use your DM for anything but making schema > changes. > > -- > David W. Fenton http://www.dfenton.com/ > usenet at dfenton dot com http://www.dfenton.com/DFA/ > David will be able to answer that question (as he knows much more than I do
about replication), however it appears to me that you don't need or want replication anymore. Is that the case? Why did you have replication if all you had was one replica and a design master on a LAN? -- Show quoteHide quoteJoan Wild Microsoft Access MVP Stof wrote: > Joan / David, > > Thanks for your reply. > > When I try "Recover Design Master", I get the error message "The value > specified is not a ReplicaID for any member in the replica set." and > nothing happens. > > Perhaps this is caused by the original DM still being in the replica > set (but no longer available)? > > Any more thoughts? > > > > "David W. Fenton" wrote: > >> "Joan Wild" <jwild@nospamtyenet.com> wrote in >> news:OF5cj6fHHHA.4056@TK2MSFTNGP03.phx.gbl: >> >>> Stof wrote: >>>> I have a single replica of a database on my server. The design >>>> master of this database was located on another server, but this >>>> server was shut down. No other replicas exist. Obviously the >>>> replica cannot synchronise with the DM anymore. I now want to >>>> make my replica the new design master, but I cannot get this to >>>> work since I cannot seem to remove the old design master from the >>>> replica list. When I do try to synchronise the replica with the >>>> DM, I get an error message saying that the DM-database cannot be >>>> found and will be deleted from the replica list. However, when I >>>> go into "synchronise now" again, the DM-datbase is still in the >>>> set. >>>> >>>> What do I have to do to get this resolved. >>> >>> You need to turn this replica into the design master. Tools, >>> Replication, Recover design master. >> >> And after doing that, create a new replica and transfer DM status to >> it, so that your production replica (the one that's always being >> used for data editing) is not your DM. >> >> The minimum proper number of replicas in any replica set is THREE: >> >> 1. Design Master *NOT* for editing >> >> 2. Replica1 for editing >> >> 3. Replica2 for editing >> >> It's just a bad idea to use your DM for anything but making schema >> changes. >> >> -- >> David W. Fenton http://www.dfenton.com/ >> usenet at dfenton dot com http://www.dfenton.com/DFA/ Stof <S***@discussions.microsoft.com> wrote in
news:4A52FED1-55FD-4F8D-A8F6-832CA68602F3@microsoft.com: Have you tried setting up a workstation to fake the old machine?> When I try "Recover Design Master", I get the error message "The > value specified is not a ReplicaID for any member in the replica > set." and nothing happens. > > Perhaps this is caused by the original DM still being in the > replica set (but no longer available)? Match the share/path of the lost DM, but with no file there, and then when you attempt to synch with it, the DM will be deleted from the replica set. Other than that, I'm pretty much at a loss. This is why I always advise that the DM be put somewhere very safe. And it has to remain in that location. |
|||||||||||||||||||||||
Other interesting topics