Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
rikleo2001
Posting Yak Master
185 Posts |
 Posted - 2008-12-12 : 06:50:05
|
| Hi GuysI am experiencing problem with setting up mirrioring and conencting to mirror and principal server via JDBC. Does the current MS JDBC driver not work for mirrored databases hosted on SQL named instances with non-default ports? Even if the port is specified in the connection object?Here are some test I have done.Mirroring Enabled Enabled Enabled Enabled Disabled DisabledPort Used 1433 1433 21437 21437 1433 21437Failed Over to standby node No Yes No Yes n/a n/aResult with IBM driver OK Failure 1 Failure 2 Failure 4 OK OKResult with Microsoft driver OK OK Failure 3 Failure 5 OK OKFailure 1 Login Failures' seen on Primary node, no activity seen on Standby node Failure 2 Unknown token 0x49' error seen on client Failure 3 Connection timeouts seen. Expected to be due to SQL Broswer Service being blocked by network firewalls over UDP port 1434. Failure 4 Login Failures' seen on Primary node, no activity seen on Standby node Failure 4 Login Failures' seen on Primary node, no activity seen on Standby node. My main objective is to get DB mirrioring working for named instanace and get Application connectivity via JDBC on specific port.Much appreciate your help.RikSKR |
|
|
sodeep
Master Smack Fu Yak Hacker
7174 Posts |
Posted - 2008-12-12 : 09:43:47
|
| Did you apply Failover partner for JDBC driver in connection strings? |
 |
|
|
|
|
|
JBDC and Mirrioring Issue with Named instance? Urg