<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2005
»
Administering
»
Mirroring In sql server 2005- Witness Full...
11 posts, Page 1 of 2
1
2
»»
Mirroring In sql server 2005- Witness Full Quorum
Rate Topic
Display Mode
Topic Options
Author
Message
VaibhavChoubey@SQL
VaibhavChoubey@SQL
Posted Monday, April 21, 2008 10:05 PM
SSC Veteran
Group: General Forum Members
Last Login: Monday, April 30, 2012 11:15 PM
Points: 295,
Visits: 109
Hi All,
I have established a Synchronous mirroring with witness ( to achieve automatic failover), I am getting all the configuration perfectly set except the value of "mirroring_witness_state" which is showing Connected on Principal and Disconnected on Mirror.
I believe these values should be Connected on both servers, but i am clueless why not.
Due to this when i try to test automatic failover my Mirror DB shows me "Disconnected ,In recovery". because it doesn't have anyone to make quorum with???? Any help highly appreciated.
Post #488344
Andy sql
Andy sql
Posted Monday, April 28, 2008 2:34 AM
SSC Eights!
Group: General Forum Members
Last Login: Tuesday, February 19, 2013 6:39 AM
Points: 893,
Visits: 871
Hi there,
If you run:
select * from sys.database_mirroring
on the Principal and the Mirror, check the following values. For a normal, synchronised mirror with Witness, the values should be:
-- mirroring_state = 4 (synchronized)
-- mirroring_role = 1 (principal) or 2 (mirror)
-- mirroring_witness_state = 1 (connected)
That should be enough for you to work out where your problem lies.
Andy
Post #491241
free_mascot
free_mascot
Posted Monday, April 28, 2008 6:17 AM
SSCommitted
Group: General Forum Members
Last Login: Wednesday, April 17, 2013 3:39 AM
Points: 1,768,
Visits: 1,312
Use Database Mirroring Monitor tool to narrow down your problem. Refer the following link for further reference.
http://msdn2.microsoft.com/en-us/library/ms365809.aspx
http://msdn2.microsoft.com/en-us/library/ms365781.aspx
Also best practice:
http://www.microsoft.com/technet/prodtechnol/sql/2005/technologies/dbm_best_pract.mspx
Good Luck!
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
Post #491321
VaibhavChoubey@SQL
VaibhavChoubey@SQL
Posted Monday, May 05, 2008 11:44 PM
SSC Veteran
Group: General Forum Members
Last Login: Monday, April 30, 2012 11:15 PM
Points: 295,
Visits: 109
Hi Everyone thankyou very much for your time.
I finally found out the problem, somehow my mirror server name was missing USERDNSDOMAIN and hence a connection was not getting established between Mirror and Witness. I explicitly added environmental variable %USERDNSDOMAIN% to server name and things worked.
Post #495400
jay-h
jay-h
Posted Tuesday, February 03, 2009 2:05 PM
Say Hey Kid
Group: General Forum Members
Last Login: Today @ 8:55 AM
Points: 685,
Visits: 1,707
I've got a similar problem with a key difference.
I currently have TWO databases mirrored, same primary, same mirror same witness.
One shows fully connected and synchronized in mirroring monitor
The other shows the witness connected to the primary but disconnected from the secondary. both databases synchronized. If I use the
select * from sys.database_mirroring
I get similar results. running it from the primary shows the witness connected for both databases. Running it from the mirror show connected for one, disconnected for the other.
...
-- FORTRAN manual for Xerox Computers --
Post #649336
Colleen Rossman
Colleen Rossman
Posted Tuesday, March 24, 2009 1:33 PM
Grasshopper
Group: General Forum Members
Last Login: Monday, September 12, 2011 2:07 PM
Points: 10,
Visits: 26
Hi - I haven't checked whether I need to add the environment variable %USERDNSDOMAIN% to my witness server or not, but wanted to let you know your post was by far the most valuable in all I've seen on mirroring issues.
I've been very frustrated with mirroring in general. When everything stays connected it works flawlessly but rarely do things remain connected and so far THREE support calls to microsoft has returned ZERO on our investment. (each call resulted in links to articles that are available for free to the general public with 'case closed' statuses).
Unfortunately my issue is only happening in production so I can't easily makes changes to my environment.
Colleen
Post #682768
alastair_bravey
alastair_bravey
Posted Wednesday, May 20, 2009 8:20 AM
Forum Newbie
Group: General Forum Members
Last Login: Tuesday, February 12, 2013 7:13 AM
Points: 1,
Visits: 107
I had this problem recently - I haven't tried the %USERDNSDOMAIN% solution however what worked for me was bouncing the server with the mirror&witness on. The mirror/witness connection just sparked into life after that and everything worked ok
Post #720586
Colleen Rossman
Colleen Rossman
Posted Monday, June 08, 2009 6:34 AM
Grasshopper
Group: General Forum Members
Last Login: Monday, September 12, 2011 2:07 PM
Points: 10,
Visits: 26
Found a valuable tip that I don't see posted anywhere: If you're having trouble establishing connection to the mirror, undoubtedly the error messages will lead you astray. Instead, setup log shipping using the GUI first. Then establish the mirroring session. Then remove log shipping. It works every time.
Post #730638
cdaly-822071
cdaly-822071
Posted Thursday, October 22, 2009 9:35 AM
SSC-Enthusiastic
Group: General Forum Members
Last Login: Thursday, May 02, 2013 3:13 PM
Points: 153,
Visits: 114
I recently had the same thing happen. Although, we have multiple db's on 1 box. The connection status on all other mirrors were fine. 1 db specifically was presenting connection problems from the mirror to the witness. I restarted the service on the witness instance and this resolved the witness connection problem. Hope this helps.
Thanks,
cdaly
Post #807259
michael nee
michael nee
Posted Tuesday, January 12, 2010 4:09 AM
Forum Newbie
Group: General Forum Members
Last Login: Wednesday, June 16, 2010 6:22 AM
Points: 2,
Visits: 70
Restarting the service on the Witness worked perfectly for me, thanks!
Post #845999
« Prev Topic
|
Next Topic »
11 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
