Fail over Between Gateways

Hello Thanks in advance...
currently we are using 2 management servers NW.contoso.com and WD.contoso.com and four gateway servers(abc.com,xyz.com,123.com,987.com)reporting to above management servers NW.contoso.com as primary and WD.contoso.com as secondary,
Primary Management Server(NW.contoso.com)
abc.com,xyz.com,123.com,987.com
Failover Management server(WD.contoso.com)
abc.com,xyz.com,123.com,987.com
so my aim is to change the primary management server of 123.com and 987.com to WD.contoso.com and set failover as NW.contoso.com,but when i tried to configure the WD.contoso.com as primary management server for 123.com and 987.com am getting error saying
its not possible to set the same server as primary and fail over.
could any one can help me out of this

Thanks Alexis for your reply,
i removed the fail
over management server using
power shell command, now the server is
reporting to NW.contoso.com(primary MS) and there was no fail-over MS,if i changed the primary management server
to WD.contoso.com using power shell command whether it will get communicated with its new management server,,because
in one article i read "An issue that occurs if there is not a fail over server set up already for the Gateway Server and you change the Primary Server programmatically is that the Gateway Server becomes orphaned due to the Gateway Server still
trying to connect to it’s previous Primary Server, since the Gateway Server does not receive it’s new configuration before the Management Servers and therefore the Management Server rejects the Gateway Server’s connection."

Similar Messages

Load-balancing and fail-over between web containers and EJB containers

When web components and EJB components are run in different OC4J instances, can we achieve load-balancing and fail-over between web containers and EJB containers?
null

It looks like there is clustering, but not loadbalancing available for rmi
from the rmi.xml configuration. The application will treat any ejbs on the
cluster as one-to-one look-ups. Orion will go out and get the first ejb
available on the cluster. See the docs on configuring rmi.xml (and also the
note below).
That is a kind-of failover, because if machine A goes down, and the
myotherAejbs.jar are on machine B too, orion will go out and get the bean
from machine B when it can't find machine A. But it doesn't go machine A
then machine B for each remote instance of the bean. You could also specify
the maximum number of instances of a bean, and as one machine gets "loaded",
orion would go to the next available machine...but that's not really
loadbalancing.
That is, you can set up your web-apps with ejbs, but let all of the ejbs be
remote="true" in the orion-application.xml file:
<?xml version="1.0"?>
<!DOCTYPE orion-application PUBLIC "-//Evermind//DTD J2EE Application
runtime 1.2//EN" "http://www.orionserver.com/dtds/orion-application.dtd">
<orion-application deployment-version="1.5.2">
<ejb-module remote="true" path="myotherAejbs.jar" />
<ejb-module remote="true" path="myotherBejbs.jar" />
<ejb-module remote="true" path="myotherCejbs.jar" />
&ltweb-module id="mysite" path="mysite.war" />
... other stuff ...
</orion-application>In the rmi.xml you would define your clustering:
<cluster host="230.0.0.1" id="123" password="123abc" port="9127"
username="cluster-user" />
Tag that is defined if the application is to be clustered. Used to set up
a local multicast cluster. A username and password used for the servers to
intercommunicate also needs to be specified.
host - The multicast host/ip to transmit and receive cluster data on. The
default is 230.0.0.1.
id - The id (number) of this cluster node to identify itself with in the
cluster. The default is based on local machine IP.
password - The password configured for cluster access. Needs to match that
of the other nodes in the cluster.
port - The port to transmit and receive cluster data on. The default is
9127.
username - The username configured for cluster access. Needs to match that
of the other nodes in the cluster.

NFS fail-over

Hello all
We are planning to use remote home directories for our non-system user accounts on our Solaris boxes.
We have two servers to use for fail over.
Is it possible to set up NFS to fail over between both servers?
Cheers
--Andreas

If they can't be on the same subnet, then they can't fail each other over directly. You'd have to have client support, and there's no NFS client I'm aware of that will do that on read/write filesystems.
You could make it work if you could force unmount the clients after a server failure, but that would be annoying.
If the servers had a presence on the same subnet, they could each host a virtual IP address that clients would connect to.
Darren

Help regarding how to instantiate the failed over URLS in OWSM gateway.

Hi all,
I am working on a scenario like...
I have a webserviceAA which takes ID and Name and dumps it into a tableAA.This service is registered with the OWSM gateway.While registering the service, "in the failover URL" section, I will give the end point of another webserviceBB, which performs the same functionality as webserviceAA does.
Once I register the service, I remove the tableAA from my database.
Then I will test the wsdl of webserviceAA using the console's test page.
Obviously, the gateway tries to invoke the webserviceAA, but fails to insert ID and Name in to the table as the table is dropped. Now my gateway goes to the "failoverURLs" and tries to instantiate webserviceBB(takes ID and Name and inserts them into tableBB).
I am able to see that the webserviceBB is getting instantiated in my BPEL Console, but thing is like the gateway is not able to pass ID and Name to the webserviceBB.....
Can any one tell me .. how do I pass values to failed over webservices.......
Hope most of you have tried out with this....
Thanks .....
Manoj Nair....

exact same problem. Any solution out there?

SQL Server 2014 Always on HA takes 8-14 seconds to fail over. Application side timeouts occur

Hi All,
I have a very similar post in the SQL Server 2014 forums too (https://social.technet.microsoft.com/Forums/sqlserver/en-US/adb5e338-907e-4405-aa62-d3ea93c7a98a/sql-server-2014-always-on-ha-takes-814-seconds-to-fail-over-application-side-timeouts-occur?forum=sqldisasterrecovery) -
advice in the end was to post a question here.
SQL Server Nodes, 2014 (12.0.2480.0)
1 Share witness (on separate subnet)
1 Cluster
1 Listener
I have been testing the response time to failovers – both manual (right-click, fail over in SSMS) and Automatic (shut down the primary host). The way I am testing response is to have a SSMS query running on my desktop, connected to the listener querying
a small table and hit execute.
The Query response time, from execute to receiving the result, has been between 8 and 14 seconds based on my testing. My previous experience (in a separate environment) showed around 2 second fail over times in a very similar configuration.
Availability DB is 200Mb and is not actively used. The nodes are synchronised.
SQL Server Hosts: Windows 2012, 2 cpu, 8gb RAM.
Questions:
1: It’s a big question but what should I expect for a ‘normal’ fail over time. Keep in mind this scenario is about as simple as it gets.
2: As it stands an 8 to 14 second ‘outage’ could cause some applications to time out. Or am I being un-reasonable? I am seeing the very simple query in SSMS to time out with this:
Msg 983, Level 14, State 1, Line 2
Unable to access availability database 'DATABASE' because the database replica is not in the PRIMARY or SECONDARY role. Connections to
an availability database is permitted only when the database replica is in the PRIMARY or SECONDARY role. Try the operation again later.
Cluster logs are long - this section accounts for 8 seconds of the 11 second outage I experienced. I can supply the full log if required. Also this log is just the 2 cluster nodes, I removed the witness share to make sure it was as simple as possible.
00001090.00002128::2015/02/25-03:05:08.255 INFO [GEM] Node 2: Deleting [1:65 , 1:71] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:10.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:11.888 INFO [GEM] Node 2: Deleting [1:72 , 1:73] (both included) as it has been ack'd by every node
00001090.00002698::2015/02/25-03:05:11.889 INFO [GUM] Node 2: Processing RequestLock 2:49
00001090.00002128::2015/02/25-03:05:11.890 INFO [GUM] Node 2: Processing GrantLock to 2 (sent by 1 gumid: 67)
00001090.00002698::2015/02/25-03:05:11.890 INFO [GUM] Node 2: executing request locally, gumId:68, my action: /dm/update, # of updates: 1
00001090.00002128::2015/02/25-03:05:12.890 INFO [GEM] Node 2: Deleting [1:74 , 1:74] (both included) as it has been ack'd by every node
00001ee4.00002130::2015/02/25-03:05:15.107 INFO [RES] Network Name: Agent: Sending request Netname/RecheckConfig to NN:5b81e7bd-58fe-4be9-a68a-c48ba2aa552b:Netbios
00001090.00002128::2015/02/25-03:05:16.988 INFO [GUM] Node 2: Processing RequestLock 1:28
Thanks in advance.
Keegan

Hi Keegan,
From these event log , what I can see is "Sending request Netname" wasted the time .
Could you please tell us the network configuration of that cluster nodes ?
If I recall correctly , it is recommended to only remain Tcp/IP protocol and disable NetBIOS over TCP/IP for "Private Network" , also do not configure DNS/Wins default gateway for "Private Network" :
https://support.microsoft.com/kb/258750?wa=wsignin1.0
After that please test again .
Best Regards,
Elton JI
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Automatic windows agent fail over in SCOM 2012 / 2012 R2

Hi All,
I have a question with respect to SCOM 2012 / 2012 R2 windows agent fail over.
For example i have only 400 windows agents and i have 2 MS in my environment. So 200 windows agents are managed by MS1 and the rest 200 are managed by the MS2.
What i want to know is if either of the MS (MS1 or MS2) Shutdown / restart or any thing happens to them, Do the agents automatically fail over to the other MS ? As i have not configured ant thing for this as i don't know.
So is there any configuration to be done for the above to happen after the deployment of both the management servers is done before discovering the agents or does it automatically understand take the rest 200 agents thinking that the other MS is down ?
Gautam.75801

Hi All,
I have a question with respect to SCOM 2012 / 2012 R2 windows agent fail over.
For example i have only 400 windows agents and i have 2 MS in my environment. So 200 windows agents are managed by MS1 and the rest 200 are managed by the MS2.
What i want to know is if either of the MS (MS1 or MS2) Shutdown / restart or any thing happens to them, Do the agents automatically fail over to the other MS ? As i have not configured ant thing for this as i don't know.
So is there any configuration to be done for the above to happen after the deployment of both the management servers is done before discovering the agents or does it automatically understand take the rest 200 agents thinking that the other MS is down ?
Gautam.75801
This happens automagically for Windows agents within a domain that are assigned to a Management Server. For other scenarios, such as Gateways, the Gateways should be configured for failover between Management Servers, and the agents attached to those
Gateways should be configured to failover between the Gateways. Cross platform agents report to a resource pool, so that happens automagically as well.
To confirm your scenario, simply run the Get-SCOMAgent cmdlet.
To test you can do the following, assuming first agent in the array isn't a Management Server/Gateway :)
$SCOMAgents = get-scomagent
$SCOMAgents[0].PrimaryManagementServerName
$SCOMAgents[0].GetFailoverManagementServers()
Supporting article:
http://blogs.technet.com/b/jimmyharper/archive/2010/07/23/powershell-commands-to-configure-gateway-server-agent-failover.aspx

Front End pool failed over

Hi all,
1. I setup a pool with three Front End servers (FQDN of pool is pool.site1.sip96x2.com and it's pointed to IP address of three Front End servers). Everything works fine. But When I disable network interface on FE1 and FE2, the Lync clients are disconnected.
I haven't understood clearly how the Lync clients failed over in a pool? Please clarify to me.
2. I have two central site (Root site and Primary site, they have different domain sip96x2.com and site1.sip96x2.com). The simple URL dialin is pointed to Front End server at Root site. So if the link between Root site and Primary site is down, how can the
users at Primary site connect to dialin URL?
3. In building topology for Front End pool, I checked Override FQDN internal web service and the FQDN is "poolint.site1.sip96x2.com". I created three A records "poolint.site1.sip96x2.com" and pointed to three IP addresses of Front End
servers. Is it right?
Thanks so much!

Ah ok, well first thing if I am reading this correctly, pool pairing Standard with Enterprise is not supported. You should only pair Standard with Standard and Enterprise with Enterprise (even though topology builder won't stop you) Take a look here for
support scenarios http://technet.microsoft.com/en-us/library/jj204697.aspx
To deal with the simple URLs in the event of failover you need to add them using Powershell. Take a look at this article which explains and gives an example: http://blogs.perficient.com/microsoft/2012/01/configuring-simple-urls-for-multiple-lync-pools/
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer"
Georg Thomas | Lync MVP
Blog www.lynced.com.au | Twitter
@georgathomas
Lync Edge Port Check (Beta)

OCR and voting disks on ASM, problems in case of fail-over instances

Hi everybody
in case at your site you :
- have an 11.2 fail-over cluster using Grid Infrastructure (CRS, OCR, voting disks),
where you have yourself created additional CRS resources to handle single-node db instances,
their listener, their disks and so on (which are started only on one node at a time,
can fail from that node and restart to another);
- have put OCR and voting disks into an ASM diskgroup (as strongly suggested by Oracle);
then you might have problems (as we had) because you might:
- reach max number of diskgroups handled by an ASM instance (63 only, above which you get ORA-15068);
- experiment delays (especially in case of multipath), find fake CRS resources, etc.
whenever you dismount disks from one node and mount to another;
So (if both conditions are true) you might be interested in this story,
then please keep reading on for the boring details.
One step backward (I'll try to keep it simple).
Oracle Grid Infrastructure is mainly used by RAC db instances,
which means that any db you create usually has one instance started on each node,
and all instances access read / write the same disks from each node.
So, ASM instance on each node will mount diskgroups in Shared Mode,
because the same diskgroups are mounted also by other ASM instances on the other nodes.
ASM instances have a spfile parameter CLUSTER_DATABASE=true (and this parameter implies
that every diskgroup is mounted in Shared Mode, among other things).
In this context, it is quite obvious that Oracle strongly recommends to put OCR and voting disks
inside ASM: this (usually called CRS_DATA) will become diskgroup number 1
and ASM instances will mount it before CRS starts.
Then, additional diskgroup will be added by users, for DATA, REDO, FRA etc of each RAC db,
and will be mounted later when a RAC db instance starts on the specific node.
In case of fail-over cluster, where instances are not RAC type and there is
only one instance running (on one of the nodes) at any time for each db, it is different.
All diskgroups of db instances don't need to be mounted in Shared Mode,
because they are used by one instance only at a time
(on the contrary, they should be mounted in Exclusive Mode).
Yet, if you follow Oracle advice and put OCR and voting inside ASM, then:
- at installation OUI will start ASM instance on each node with CLUSTER_DATABASE=true;
- the first diskgroup, which contains OCR and votings, will be mounted Shared Mode;
- all other diskgroups, used by each db instance, will be mounted Shared Mode, too,
even if you'll take care that they'll be mounted by one ASM instance at a time.
At our site, for our three-nodes cluster, this fact has two consequences.
One conseguence is that we hit ORA-15068 limit (max 63 diskgroups) earlier than expected:
- none ot the instances on this cluster are Production (only Test, Dev, etc);
- we planned to have usually 10 instances on each node, each of them with 3 diskgroups (DATA, REDO, FRA),
so 30 diskgroups each node, for a total of 90 diskgroups (30 instances) on the cluster;
- in case one node failed, surviving two should get resources of the failing node,
in the worst case: one node with 60 diskgroups (20 instances), the other one with 30 diskgroups (10 instances)
- in case two nodes failed, the only node survived should not be able to mount additional diskgroups
(because of limit of max 63 diskgroup mounted by an ASM instance), so all other would remain unmounted
and their db instances stopped (they are not Production instances);
But it didn't worked, since ASM has parameter CLUSTER_DATABASE=true, so you cannot mount 90 diskgroups,
you can mount 62 globally (once a diskgroup is mounted on one node, it is given a number between 2 and 63,
and other diskgroups mounted on other nodes cannot reuse that number).
So as a matter of fact we can mount only 21 diskgroups (about 7 instances) on each node.
The second conseguence is that, every time our CRS handmade scripts dismount diskgroups
from one node and mount it to another, there are delays in the range of seconds (especially with multipath).
Also we found inside CRS log that, whenever we mounted diskgroups (on one node only), then
behind the scenes were created on the fly additional fake resources
of type ora*.dg, maybe to accomodate the fact that on other nodes those diskgroups were left unmounted
(once again, instances are single-node here, and not RAC type).
That's all.
Did anyone go into similar problems?
We opened a SR to Oracle asking about what options do we have here, and we are disappointed by their answer.
Regards
Oscar

Hi Klaas-Jan
- best practises require that also online redolog files are in a separate diskgroup, in case of ASM logical corruption (we are a little bit paranoid): in case DATA dg gets corrupted, you can restore Full backup plus Archived RedoLog plus Online Redolog (otherwise you will stop at the latest Archived).
So we have 3 diskgroups for each db instance: DATA, REDO, FRA.
- in case of fail-over cluster (active-passive), Oracle provide some templates of CRS scripts (in $CRS_HOME/crs/crs/public) that you edit and change at your will, also you might create additionale scripts in case of additional resources you might need (Oracle Agents, backups agent, file systems, monitoring tools, etc)
About our problem, the only solution is to move OCR and voting disks from ASM and change pfile af all ASM instance (parameter CLUSTER_DATABASE from true to false ).
Oracle aswers were a litlle bit odd:
- first they told us to use Grid Standalone (without CRS, OCR, voting at all), but we told them that we needed a Fail-over solution
- then they told us to use RAC Single Node, which actually has some better features, in csae of planned fail-over it might be able to migreate
client sessions without causing a reconnect (for SELECTs only, not in case of a running transaction), but we already have a few fail-over cluster, we cannot change them all
So we plan to move OCR and voting disks into block devices (we think that the other solution, which needs a Shared File System, will take longer).
Thanks Marko for pointing us to OCFS2 pros / cons.
We asked Oracle a confirmation that it supported, they said yes but it is discouraged (and also, doesn't work with OUI nor ASMCA).
Anyway that's the simplest approach, this is a non-Prod cluster, we'll start here and if everthing is fine, after a while we'll do it also on Prod ones.
- Note 605828.1, paragraph 5, Configuring non-raw multipath devices for Oracle Clusterware 11g (11.1.0, 11.2.0) on RHEL5/OL5
- Note 428681.1: OCR / Vote disk Maintenance Operations: (ADD/REMOVE/REPLACE/MOVE)
-"Grid Infrastructure Install on Linux", paragraph 3.1.6, Table 3-2
Oscar

Which role do I need DFS or File server on fail over cluster server 2012 R2?

what I want to achieve is that I want to share all my user data files in a central location and to be highly available all the time whether it's a general share or folder redirection data. BUT I'm a bit confused; I have fail over cluster set-up
on server 2012, now I would like to add DFS as a role but than we have another role called File server and virtually it does the same thing as DFS? Means it creates a namespace share that can be access even one of the nodes goes down. Now I am thinking is
that DFS does the replication between two physical location but fail over cluster works slightly differently and with file server it pretty much does the same thing except for replicating data from one drive to another. Now what do you suggest I do or
did I get the concept wrong like a noob?

DFS and Failover Clustering for file shares provides a similar end result for file access, but they are significantly different implementations.
Clustering provides high availability to files by presenting shared access to set a files served from a cluster. With 2012 R2 Microsoft added the ability to create a Scale-out File Server that even allows all nodes of the cluster to server access to
the files for a higher level of performance and other great things. Bottom line with Failover Clusters for files is that there is a single copy of the file presented from the cluster.
DFS on the other hand provides high availability to files by presenting multiple copies of the file by making a copy in two or more locations and presenting a naming space that allows access to the file through any of the network paths. DFS works very
well for files that are primarily read-only. When you get into a situation where there is a lot of updating of the shared files, DFS is not a very good solution. There are ways to implement DFS for read/write files, but it generally requires a
good knowledge of how the files are used and how you want to manage them.
The key to answering your question comes in your first sentence "I want to share all my user data files in a central location and to be highly available all the time". My initial reaction to this is that central location means Failover Cluster
- there is only a single copy of the file. However, "all the time" can be compromised by network failures to the central site. Remote sites would not have access if they can't access the central site. DFS provides the ability to
have copies remotely, but then if you allow updating at multiple sites, you have to manage the merging of the changes, among other things.
. : | : . : | : . tim

Time out fail over

On this system:
OS: Solaris 10 11/06 s10s_u3wos_10 SPARC
Cluster version: 3.1u4
A- Normally after how much time resource is moved to the other node if ipmp fails (e.g. gateway is unreacheable) ?
B- What happens if ipmp fails in both server ? packages are kept on their nodes ?
C- Does it exist timeout over 10 minutes in cluster configuration ?

u have 2 options - u could increase the back end time out to a very large value so that server can wait rather than timing out rather than failing over or to do some thing like
<Object name=�default�>
NameTrans fn=map from=/ name=reverse-proxy-/
</Object>
<Object name=�reverse-proxy-/�>
Route fn=set-origin-server server=server1
ObjectType fn=http-client-config timeout=600
</Object>
see - http://docs.sun.com/app/docs/doc/820-4841/gdhrg?a=view
( or simply disable any fail over but have different individual servers distributing load across different application)
split your uri or application so that each application goes to 1 back end server. for example, let us say - u have 2 java applications that u would like jboss to do the job for you, u could do some thing like
now, u could edit your obj.conf or (<vs>-obj.conf) depending on your configuration so that it looks like this
<Object name=�default�>
NameTrans fn=map from=/ name=reverse-proxy-/
</Object>
<Object name=�reverse-proxy-/�>
<If $uri =~ /foo1>
Route fn=set-origin-server server=<ŝerver1>
</If>
<If $uri =~ /foo2>
Route fn=set-origin-server server=<ŝerver2>
</If>
</Object>
btw - i will file a RFE on your behalf for this feature.

Failed over to a Aysnc Replica and now previous primary replica(Now Secondary) is in NOT SYNC state

Hello All,
Here is my situation :
3 Nodes in an AG configuration, and its a multi-site cluster. Sync commit between 2 nodes in one DC and Async commit to a node in the DR DC.
AG is failed over to the Async Replica which is the DR site and all the databases comes up fine and application also can connect using the listener.
When checked the state of secondary databases, its in NOT SYNC mode. Data is suspended automatically. I can resume data movement to fix the problem, but was curious why this will be in NOT SYNC mode?
Thanks in advance.
Thank you,
Anup
<div> Anup | Database Consultant Blog: <a href="www.sqlsailor.com/">www.sqlsailor.com</a> Twitter: <a href="https://twitter.com/#!/AnupWarrier"> Follow me !</a>
 Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful. </div>

Hello Anup,
The reason this happens is because of the forced failover needed to be used when moving to an Async replica. It will cause all other replicas to become suspended due to the fact that it is never known if data loss will occur or not.
It might not make sense right now, but think about a situation where the databases are not synchronized and failover is forced (it has to work in all situations). There may be a good bit of data on the primary replica that has not yet made it (or partially)
to the async secondary. It wouldn't make sense to negotiate the primary back down (after all, it's the async one) and undo valid transactions. It also allows for a database snapshot or other method to be done on the old sync primary which could be used for
DR purposes to get those valid transactions and data out.
BOL Doc:
http://msdn.microsoft.com/en-us/library/hh213151.aspx#ForcedFailover
Sean Gallardy | Blog |
Twitter

ISE admin , PSN and monitoring node fail-over and fall back scenario

Hi Experts,
I have question about ISE failover .
I have two ISE appliaces in two different location . I am trying to understand the fail-over scenario and fall-back scenario
I have gone through document as well however still not clear.
my Primary ISE server would have primary admin role , primary monitoring node and secondary ISE would have secondary admin and secondary monitoring role .
In case of primary ISE appliance failure , I will have to login into secondary ISE node and make admin role as primary but how about if primary ISE comes back ? what would be scenario ?
during the primary failure will there any impact with users for authentication ? as far as PSN is available from secondary , it should work ...right ?
and what is the actual method to promote the secondary ISE admin node to primary ? do i have to even manually make monitoring node role changes ?
will i have to reboot the secondary ISE after promoting admin role to primary ?

We have the same set up across an OTV link and have tested this scenario out multiple times. You don't have to do anything if communication is broken between the prim and secondary nodes. The secondary will automatically start authenticating devices that it is in contact with. If you promote the secondary to primary after the link is broke it will assume the primary role when the link is restored and force the former primary nodes to secondary.

Thin Client connection not failing over

I'm using the following thin client connection and the sessions do not failover. Test with SQLPLUS and the sessions do fail over. One difference I see between the two different connections is the thin connection has NONE for the failover_method and failover_type but the SQLPLUS connection show BASIC for failover_method and SELECT for failover_type.
Is there any issues with the thin client the version is 10.2.0.3
jdbc:oracle:thin:@(description=(address_list=(load_balance=YES)(address=(protocol=tcp)(host=crpu306-vip.wm.com)(port=1521))(address=(protocol=tcp)(host=crpu307-vip.wm.com)(port=1521)))(connect_data=(service_name=ocsqat02)(failover_mode=(type=select)(method=basic)(DELAY=5)(RETRIES=180))))

You have to use (FAILOVER=on) as well on jdbc url.
http://download.oracle.com/docs/cd/B19306_01/network.102/b14212/advcfg.htm#sthref1292
Example: TAF with Connect-Time Failover and Client Load Balancing
Implement TAF with connect-time failover and client load balancing for multiple addresses. In the following example, Oracle Net connects randomly to one of the protocol addresses on sales1-server or sales2-server. If the instance fails after the connection, the TAF application fails over to the other node's listener, reserving any SELECT statements in progress.sales.us.acme.com=
(DESCRIPTION=
*(LOAD_BALANCE=on)*
*(FAILOVER=on)*
(ADDRESS=
(PROTOCOL=tcp)
(HOST=sales1-server)
(PORT=1521))
(ADDRESS=
(PROTOCOL=tcp)
(HOST=sales2-server)
(PORT=1521))
(CONNECT_DATA=
(SERVICE_NAME=sales.us.acme.com)
*(FAILOVER_MODE=*
*(TYPE=select)*
*(METHOD=basic))))*
Example: TAF Retrying a Connection
TAF also provides the ability to automatically retry connecting if the first connection attempt fails with the RETRIES and DELAY parameters. In the following example, Oracle Net tries to reconnect to the listener on sales1-server. If the failover connection fails, Oracle Net waits 15 seconds before trying to reconnect again. Oracle Net attempts to reconnect up to 20 times.sales.us.acme.com=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=tcp)
(HOST=sales1-server)
(PORT=1521))
(CONNECT_DATA=
(SERVICE_NAME=sales.us.acme.com)
*(FAILOVER_MODE=*
*(TYPE=select)*
*(METHOD=basic)*
*(RETRIES=20)*
*(DELAY=15))))*

Stateful bean not failing over

          I have a cluster of two servers and a Admin server. Both servers are running NT
          4 sp6 and WLS6 sp1.
          When I stop one of the servers, the client does n't automatically failover to
          the other server, instead it fails unable to contact server that has failed.
          My bean is configured to have its home clusterable and is a stateful bean. My
          client holds onto the remote interface, and makes calls through this. If Server
          B fails then it should automatically fail over to server A.
          I have tested my multicast address and all seems to be working fine between servers,
          my stateless bean work well, load balancing between servers nicely.
          Does anybody have any ideas, regarding what could be causing the stateful bean
          remote interface not to be providing failover info.
          Also is it true that you can have only one JMS destination queue/topic per cluster..The
          JMS cluster targeting doesn't work at the moment, so you need to deploy to individual
          servers?
          Thanks


Did you enable stateful session bean replication in the
          weblogic-ejb-jar.xml?
          -- Rob
          Wayne Highland wrote:
          >
          > I have a cluster of two servers and a Admin server. Both servers are running NT
          > 4 sp6 and WLS6 sp1.
          > When I stop one of the servers, the client does n't automatically failover to
          > the other server, instead it fails unable to contact server that has failed.
          >
          > My bean is configured to have its home clusterable and is a stateful bean. My
          > client holds onto the remote interface, and makes calls through this. If Server
          > B fails then it should automatically fail over to server A.
          >
          > I have tested my multicast address and all seems to be working fine between servers,
          > my stateless bean work well, load balancing between servers nicely.
          >
          > Does anybody have any ideas, regarding what could be causing the stateful bean
          > remote interface not to be providing failover info.
          >
          > Also is it true that you can have only one JMS destination queue/topic per cluster..The
          > JMS cluster targeting doesn't work at the moment, so you need to deploy to individual
          > servers?
          >
          > Thanks
          Coming Soon: Building J2EE Applications & BEA WebLogic Server
          by Michael Girdley, Rob Woollen, and Sandra Emerson
          http://learnweblogic.com

NIC not failing Over in Cluster

Hi there...I have configured 2 Node cluster with SoFS role...for VM Cluster and HA using Windows Server 2012 Data Center. Current set up is Host Server has 3 NICS (2 with Default Gateway setup (192.x.x.x), 3 NIC is for heartbeat 10.X.X.X). Configured CSV
(can also see the shortcut in the C:\). Planning to setup few VMs pointing to the disk in the 2 separate storage servers (1 NIC in 192.x.x.x) and also have 2 NIC in 10.x.x.x network. I am able to install VM and point the disk to the share in the cluster volume
1.
I have created 2 VM Switch for 2 separate Host server (using Hyper-V manager). When I test the functionality by taking Node 2, I can see the Disk Owner node is changing to Node 1, but the VM NIC 2 is not failing over automatically to VM NIC 1 (but I can
see the VM NIC 1 is showing up un-selected in the VM Settings). when I go to the VM Settings > Network Adapter, I get error -
An Error occurred for resource VM "VM Name". select the "information details" action to view events for this resource. The network adapter is configures to a switch which no longer exists or a resource
pool that has been deleted or renamed (with configuration error in "Virtual Switch" drop down menu).
Can you please let me know any resolution to fix this issue...Hoping to hear from you.
VT

Hi,
From your description “My another thing I would like to test is...I also would like to bring a disk down (right now, I have 2 disk - CSV and one Quorum disk) for that 2 node
cluster. I was testing by bringing a csv disk down, the VM didnt failover” Are you trying to test the failover cluster now? If so, please refer the following related KB:
Test the Failover of a Clustered Service or Application
http://technet.microsoft.com/en-us/library/cc754577.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Fail over Between Gateways

Similar Messages

Maybe you are looking for