Client handoff and Roaming

Hi all,
I've installed four WLC 5.1.151.0 and the clients have roaming issues. When a client roams i can see it as "Mobility Role: Anchor" on the first WLC it connected and as "Mobility Role: Foreign" on the WLC it roamed to. The problem is after the roaming the client can't reach the network, no ping, no communication. I can ping the client from the controller it roamed to, but not from the first controller it connected (the anchor). Mobility groups are configured correctly, "Symmetric mobility tunneling mode" and "AP Groups VLAN Feature Enable" are disabled. I've configured all the controllers as DHCP with different scopes on the same subnet, so its a inter-controller roaming, not inter-subnet. I can't upgrade the controller software soon because its a production environment. To fix the problem I remove the client from the first controller, refresh its Wifi interface so it connects directly to the second controller and the network works again. Any help is welcome. Thank you.
Gian Paolo

Maybe I've fixed. All the WLCs wireless interfaces associated to the SSID have address in 10.110.0.0/16 subnet but from the first controller I can't ping anything above 10.110.0.0/24 network. I've changed the netmask of all WLCs some days ago but looks like WLC_01 didn't accepted the new netmask (I've used the web interface). It's odd, maybe a problem of browser caching or something, reviewing the saved configuration of yesterday the netmask is definitely wrong. I've changed the netmask from command line and now roaming works, I can ping any client in 10.110.0.0/16 subnet.
What confused me was checking eping and mping that worked all the time because WLCs have addresses 10.110.0.x.
Thank you all for the support.

Similar Messages

How to improve client handover and roaming between AP's

Improving client Handover and roaming between APs
There are a few standards and methodologies available to use to improve handover of clients between APs. Most are focused on VOIP technologies, but it must always be remembered that we cannot control the client Handover (especially with legacy clients) we can only encourage them. Some Standards and methods work well for some environments and some do not - test the recommendations extensively before implementing in a live Production environment. It must also be noted that all settings take effect immediately once applied, however from a client perspective it might need to re-associate for the changes to take effect client side.
As with everything else in IT, if a perfect method/solution existed there would only be one - try them all and keep the best.
The Standards and Definitions
802.11k
IEEE 802.11k allows a device to quickly identify nearby APs that are available for roaming. When the signal strength of the current AP weakens and the device needs to roam to a new AP, it will already know the best candidate AP with which to connect to.
802.11r
IEEE 802.11r specifies fast Basic Service Set (BSS) transitions between access points by redefining the security key negotiation protocol, allowing both the negotiation and requests for wireless resources to occur in parallel.
When a device roams from one AP to another on the same network, 802.11r streamlines the authentication process. BSS allows a devices to associate with APs more quickly. Coupled with 802.11k's ability to quickly identify the target AP, BSS's faster association method may enhance application performance.
Handoff Assist
The AP monitors the RSSI for every associated client. If the RSSI for a specific client falls below "low-rssi-threshold" and continues to fall for the "rssi-falloff-wait-time", then the AP will send a de-auth to the client.
The de-auth is meant to kick the client away from the current AP and get it to re-authenticate to a nearby AP. This will have the effect of helping a client handover between 2 APs.
BUT (Big But), if the client gets de-authed and takes a while to re-authenticate (if it even does re-authenticate automatically after a de-auth), then this will have the effect of destroying communication instead of helping it -- mostly found with legacy clients.
Remove Lower Transmit Rates
Removing lower transmit rates is a way to promote better roaming, BUT not all clients respond well, or even respond to it.
The practice is that the basic rates are a subset of the transmit rates. If you only want to allow speeds 9 and up, you would select only the transmit rates of 9 and up, and the basic rates of 9 and 11. If a legacy client expects the rates of 1 and 2 it will not connect.
Local Probe Threshold
Local probe Threshold prevents a client from connecting to an AP with a too low a signal - helps more with initial connection than roaming.
The local probe threshold parameter is not supposed to force clients to roam as soon as they pass near an access point with a good signal, but rather to NOT hold on to an access point with a weak signal (avoiding sticky clients).
PMK Caching
Defined by 802.11i and is a technique available for authentication between a single AP and a station. If a station has authenticated to an AP, roams away from that AP, and comes back, it does not need to perform a full authentication exchange. Only the 802.11i 4-way handshake is performed to establish transient encryption keys.
Opportunistic Key Caching (OKC)
Is a similar technique to PMK, but not defined by 802.11i, for authentication between multiple APs in a network where those APs are under common administrative control. An Aruba deployment with multiple APs under the control of a single controller is one such example. Using OKC, a station roaming to any AP in the network will not have to complete a full authentication exchange, but will instead just perform the 4-way handshake to establish transient encryption keys
Implementation and Configuration
802.11k
802.11k is configured in your VAP profile. Tick the option to “Advertise 802.11k”. There after set the Handover Trigger Feature Settings.
Tick the “Enable Handover Trigger feature” and then set RSSI threshold by specifying the -dBm level at what the hand over trigger should be sent to the client
802.11r
802.11r is configured under SSID of your VAP profile. Tick the option to “Advertise 802.11r”
HandofF Assist
Station Handoff Assist is enabled in RF Optimization under the RF Management section of AP configuration.
Tick the “Station Handoff Assist” option to enable it, next set the Low RSSI Threshold – the threshold determines above what level no deauth gets sent
Lower Transmit Rates
Transmit rates can be adjusted in the Advanced tab of SSID under your VAP profile.
Remember that the basic rates are a subset of the transmit rates. If you only want to allow speeds 9 and up, you would select only the transmit rates of 9 and up, and the basic rates of 9 and 11
Local Probe threshold
Local Probe threshold can be adjusted in the advanced tab of SSID under your VAP profile.
Depending on the density of your APs consider values between 20 and 40 -- 40 being aggressive in an AP dense area.
Deny Broadcast Probes
Denying Broadcast Probes can cause problems with Roaming especially if the SSID is hidden – leave option disabled.

Hi, thank you for the helpful guidance. I have a basic question, if the device roam from one AP to another AP with the same SSID. Is there a need of re-authentication given a) the network uses EAP based authentication; b) the network uses MAC address authentication. If there is no need of EAP re-authentication, how the 802.11 keys are moved to the new AP. Thank you very much if you could help me clarify my thought.

EAP-TLS with WLC 5.2.178 Improve Performance and Roams?

Good Morning...
I've been working on moving our clients over to EAP-TLS with Machine Auth for sometime. I had moved the IT Department over a couple of months ago as a test with no issues reported and have tested on a few of our Medical Carts (CoWs) as well with no issues reported. However, upon deploying to a larger population of Carts (Specifically using Atheros 5006x 7.x Driver {No Client}) I've been getting some client drop complaints. If I look at the client history I do see a lot of "Client Associations" or Roams that occure anywhere from ever 2minutes, to every 10minutes to every 5 hours. These carts do move around ALOT as they are pushed from one Patient Room to another so I'm guessing the drops are occuring during a re-authentication phase as the device roams. Looking at the device you might not be able to tell it's dropping but the software we use (Meditech) is very connection sensitive in doing a simple ping you may see a couple of dropped packets until the client is fully connected again. So I'm guessing the roaming is the issue. What can we do to fight this or make it more effecient? It was mentioned to me by a colleague (who doesn't know where he saw it) that he thought it was possible to configure the WLC's to not reauthenticate on the roam? I'm guessing something must be able to be tweaked if the 7921's and 25's support EAP-TLS as this type of latency would never work. By the way I'm using an ACS 4.2 as my authentication platform mapped back to AD.

You will always reauth with a roam. That is part of the 802.11 spec. How you reauth will depend on the type of security you have setup. If you are using WPA2/AES or CCKM the reauths can be done with a PMK instead of needing to go through the entire reauthentication process. Try running "debug client " for a client having the issue and see if it gives you an idea of where the authentication is failing.

WAP2000 fails WDS and roaming

Hi,
I'm wondering if anyone on this forum has successfully used WAP2000 access points.
I'm particularly disappointed with these device:
Hardware Version:
1.0
Software Version:
2.0.0.5
I set two of them up with exactly the same wifi security settings, same channel and WDS, one of which is a repeater (MAC addresses correctly set).
Whenever I turn the repeater station on, the wireless supplicant not only doesn't extend it's coverage but if it's within the AP's outer range then it LOSES its connection with the AP. It's as if the wrieless repeater "jammed" the connection. I tried just about every possible setup and came to the conclusion that WDS does not work with my WAP2000 devices.
I don't even "require" WDS to work if at least a decent roaming could be done. So I setup 2 WAP2000 as 2 APs with exactly the same wifi security settings and different, non-overlapping channels (same SSID). Roaming *should* be fairly quick but it lasts between 30 and 50 seconds!
I replaced both WAP2000 APs with older WAP54G APs (same settings) and roaming is "fast" (less than 3 seconds!).
So on one hand I'm demonstrating that roaming does NOT depend ONLY on the client side and that APs can be the culprit.
On the other hand, I'm also showing how bad the WAP2000 product is (it's more expensive than the WAP54G but is completely unreliable).
No wonder there are so few references on the web to the WAP2000 device.
"Cisco" isn't as good as it sounds (I know it's "small business" but it's still Cisco).
If someone here has had a similar experience and has found a solution, please let me know.
Otherwise, I'm definitely not going to value the "Cisco/Linksys" brand as well as I did in the past.
Thanks,
Vieri

To get the best roaming, you need to make sure you have enough coverage. That usually means a good site survey was performed to specify how many access points and the locations of the access point. Without this piece, there is no guarantee of roaming.
As far as WDS, you can setup an autonomous ap as a WDS server that is either dedicated as a WDS or is a WDS server and also serves clients.
Sent from Cisco Technical Support iPhone App

Flash player 10 and roaming profile

Hi,
Some of my clients are having similar issues since they've upgraded from flash player version 9 to version 10. They all use roaming profile, i.e user documents and settings are stored on the server rather than individual machines.
The problem is that when they log in my application their login is successful but they don't get past that stage. This is because upon login, the application tries to write into a shared object but I believe it fails to do so.
If they revert back to Flash player 9, it's all fine. Client with no roaming profile don't experience this issue.
Therefore I believe there are some changes in Flash player 10 security. What should I do ?
Thanks

Hi !
I knew somebody from Adobe would finally reply
Well, I've actually come across this bug report this afternoon ! And I've asked my client to try the suggested workarounds. That was his reply :
' These work arounds are no good I’m afraid. These work arounds mean we have to mess around with file redirection which we don’t want to do. The reason these work arounds do work is that there is a Desktop folder in the local profile. When you re-direct the Desktop the local Desktop gets moved to the network. If we then re-create a local Desktop folder we break folder re-direction and there is potential for the user to have the wrong desktop displayed, or have files stored locally on their PC not being backed up. '
As you can see he's not so keen to change any network settings.
Do you have any other suggestions ?
Thanks

Alert or Notification for Client Open and Close

Hi All,
How to configure an Alert or Notification, if the Client (SCC4 and SE06) is open and in modifiable state, we have spoken to our solman team and got the confirmation that there is no MT Class for SCC4 and SE06.
If this is possible through any z program, please do help and provide your comments and suggestions.
Thanks & Regards
Praveen

It is possible to assign a different posting period variant to company code in a non-leading ledgers (the extreme right field) in the foll. node in SPRO.
Financial Accounting (New) -> Financial Accounting Global Settings (New) -> Ledgers -> Ledger -> Define and Activate Non-Leading Ledgers

How can I create a client console and work together with the Cache Server?

How can I edit the following Cache-Server.cmd file to create a client console and work together with the Cache Server?
The following is the cache server file: contacts-cache-server.cmd
@echo off
setlocal
if (%COHERENCE_HOME%)==() (
set COHERENCE_HOME=c:\coherence
set CONFIG=C:\home\oracle\coherence\Contacts
set COH_OPTS=%COH_OPTS% -server -cp %COHERENCE_HOME%\lib\coherence.jar;C:\home\oracle\
coherence\Contacts;C:\home\oracle\coherence\Contacts\classes;
set COH_OPTS=%COH_OPTS% -Dtangosol.coherence.cacheconfig=%CONFIG%\contacts-cache-config.xml
java %COH_OPTS% -Xms1g -Xmx1g -Xloggc: com.tangosol.net.DefaultCacheServer %2 %3 %4 %5 %6 %7
:exitEdited by: junez on 23-Oct-2009 09:20

Hi
To run the console, change DefaultCacheServer to CacheFactory
Paul

Client dependent and client independent in ALE

I am going through pdf learning of an ALE scenario,i couldnot get wat is meant by client Independent and client dependent.
How can i conclude
Create message type (WE81){color:green} Client independent {color}
To create a new message type, follow these next few steps:
u2022 Enter transaction WE81 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Create logical message type)
u2022 Choose Create logical message type by double clicking on it
u2022 Click on change icon to enter change mode
u2022 Click on New entries to add a new type
u2022 Enter the required message type, in our case it is ZINVRV and an appropriate description
u2022 Save and exit.
Your message type has now been created. The next step will be to link it to the IDoc.
2.2.1. Link message to IDoc type (WE82 & BD69) {color:green} Client independent {color}
To link the message type to the IDoc type follow these next few steps:
u2022 Enter transaction WE82 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> EDI: Message Types and Assignment to IDoc Types)
u2022 Click on change icon to enter change mode
u2022 Click on New entries to create the link
u2022 Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
u2022 Save and exit
u2022 Enter transaction BD69 (ALE -> Extensions -> IDoc types -> Maintain message type for intermed. Structure -> Assign message type to IDoc for ALE)
u2022 Click on change icon to enter change mode
u2022 Click on New entries to create the link
u2022 Enter the message type ZINVRV and the BasicIDoc type as ZINVRV01
u2022 Save and exit
Your IDoc is now linked to your message type. We still need to link object types and add the message to the model before we can use the message.
2.2.2. Maintain object type for message type (BD59) Client independent
The ALE objects are used to create links between IDocs and applications objects, to control the serialisation, to filter messages in the customer model and to use listings.
For our own message type and IDoc you must maintain object types for the links.
If you want to check the serialisation for the message type, then you must maintain object types for the serialisation. If no serialisation object has been maintained for a given message type, then the serialisation will not be checked for this message type.
To add an object type to our message type, follow these next few steps:
u2022 Enter transaction BD59 (ALE -> Extensions -> ALE object maintenance -> Maintain object types)
DOC NAME: ALE_SCENARIO_DEVELOPMENT_PROCEDURE
Version 1 Page 6 of 16
ALE Scenario Development Guide
u2022 Type in your message type ZINVRV and press enter
u2022 Click on New entries
u2022 Enter your object type, LIFNR (We need to use the vendor as a filter object), the segment name where LIFNR resides, Z1INVRV, a number 1 for the sequence followed by the actual field name LIFNR
u2022 Save and exit.
You have now created an object that weu2019ll use as a filter object in the customer model to direct the flow of messages to the various logical systems based on the vendors in the filter of the message type ZINVRV.
We now need to add our new message type to the distribution model.
2.3. Configuring the Distribution Model
This task is performed on your ALE reference client.
2.3.1. Manual Configuration (BD64) {color:green} Client dependent {color}
To manually configure the customer distribution model, read the ALE configuration procedure, and follow these steps:
u2022 Perform the Maintain customer distribution model directly function. (ALE -> Distribution customer model -> Maintain customer distribution model directly)
u2022 Specify the customer model you want to maintain and the logical system that is to be the sender of the messages OR create a new model. (Create model ALE with logical system ALELS1C400)
u2022 Choose the receiving systems to which the sending system must forward message type ZINVRV to.
u2022 For each receiving logical system allocate the message type necessary for communication to the receiving systems as per ALE configuration procedure.
u2022 Create filter objects (in our case LIFNR as the object type with the associated vendor number, 0000018001 with leading zeros, in the object area) for the message types.
u2022 Save the entries.
Refer my query within color:green
Edited by: aditya sharma on Jul 14, 2010 12:57 PM
Edited by: aditya sharma on Jul 14, 2010 1:01 PM

A client is an independent business unit within an R/3 System, Data in the R/3 are classified as cleint-Dependent and client-independent.
Client-independent data such as ABAP Programs, R/3 repository objects throught the entire system. Other data is client-dependent. meaning, it can be viewed from one client. Cleint-dependent data includes customizing application and user data.
Eg.
Scripts are client dependent, means the changes done to SAP scripts in particular client will not be reflected in other client.
Smartforms are client independent, means changes done in one client will be reflected in all the clients.
Server : ECC6
Client : 100 , 200 , 300 , 400
Now suppose you have developed report in DV server client 100.
Then you will be able to see that in all clients.
Hence this is called as client independent. You can change anywhere and changes will be reflected to all ...
Now suppose you have developed a script in DV client 100.
You will not be able to see that in client 200 or 300 or 400 unless ytou copy that from client since it is client dependent.

Client Copy and System Restore query

Dear All,
I have few major doubt regarding client copy and system restor.
1. In my Quality system there are 2 clients: 100 and 200.In my PRD there is only 1 client 300(other than the standard default clients). My doubt is during remote client copy with SAP_ALL profile from PRD to QUA why the space increases only in MB.
I have been asked the same question by my management. They are saying PRD is 300GB and QUA is 220GB then why the space increases in MB though all data is copied in client 200(QUA) from client300(PRD)
2. If I delete client why the space is released in MB. Because according to them it should be in GBs.
3. Now my third query is I have to restore PRD backup in QUA.So I said that this requires same <SID> and Same sapce in the sapdatafiles(OS is HP-UX 11.31 and DB is Oracle 10g).So I have to explain them why these two things are contradary to each other. In case of client copy space required is only in MB and in case of System restore of PRD in QUA sapce require is in GBs.
Your suggestions will be highly obliged.
Regards,
PG

1. In my Quality system there are 2 clients: 100 and 200.In my PRD there is only 1 client 300(other than the standard default clients). My doubt is during remote client copy with SAP_ALL profile from PRD to QUA why the space increases only in MB.
Response > Because during client copy your customizing and other objects are copied.
The database structures,tables etc are already present.
2. If I delete client why the space is released in MB. Because according to them it should be in GBs.
Response > Since client deletion is not same as deleting database /customizing tables .If you delete complete dataspaces/tables then there will be sizeable difference.Similar logic as Response 1
3. Now my third query is I have to restore PRD backup in QUA.So I said that this requires same <SID> and Same sapce in the sapdatafiles(OS is HP-UX 11.31 and DB is Oracle 10g).So I have to explain them why these two things are contradary to each other. In case of client copy space required is only in MB and in case of System restore of PRD in QUA sapce require is in GBs.
Response > Since in a system copy you will copy data files (which includes tables,and all otehr strucutres ) hence the size required will be similar to PRD.

Logical Systems for client 000 and 001

I've just install solman 7.0 ehp1 sr1 and am going to create a new client from 001.
Do I need to create logical systems for clients 000 and 001?
Do I need to creat rfc's for these?
Thanks,
Daniel

no, no need.
you will create a logical system name for the copied client (such as 100)

What's the difference between client combo and server combo? Also, what would happen if I install both?

what's the difference between client combo and server combo? Also, what would happen if I install both?

One is for the base version of the Mac OS, the other is for the Server version. You can only install the one that matches your system.

Handoff and iMessage Not Working

I have multiple Apple devices (iPhone 6, 2 x iPhone 5s, iPad Air, MacBook Air, Mac Mini, iPod Touch 5th gen) all running the latest iOS (8.1) and Mac (Yosemite) operating systems and all on the same wi-fi network, logged into the same iCloud account with both Handoff and Bluetooth enabled. Handoff works perfectly across all devices for all apps with one exception - iMessage. Regardless of which device I start a message on it does not appear on any other device or the Macs. Starting a message on the Mac it will only appear on another device if I first close the message window on the Mac and reopen it. Personal instant hotspot works fine between the iPhone 6 and iPad and iPod touch but only occasionally does it appear on the MacBook Air and never connects. Have tried multiple reboots etc but problem still persists.

Had a similar problem...
open an app on mac...can see it on phone...
open an app on phone...cannot see it on mac...or see it once then its gone...
my problem (not sure if it is yours)...turned out bluetooth sharing was off on the mac...
Mac-->System Preference: Sharing
Turn on Bluetooth sharing; Turn on Internet sharing bluetooth PAN...
worked for me...

How to get the client date and time ?

Dear Sirs...
Using jdeveloper 10.1.2.0
How can i get the client date and time using the HttpServletRequest ?
thanks for any help in advance
best regards

If your code is running on the client pc you can just create a new instance of the java.util.Date class. That class automatically defaults to the current time of the client machine. Otherwise if you're running the code on the server, you could insert/post the client date/time by adding its string representation as a parameter to the HTTP request object.
Ronald

Questions related to the localstorage=false client restarted and join back

Hi, We are using the coherence 3.4.2 version. I notified a strange problem in our application, related to the coherence. I am posting here seeking for help. We are using JDK 1.6.0_16 on Linux 64 OS.
To simplify the problems, let me just say that we have 3 JVM running as now. One is we called the data server, starting with following JVM settings:
java -Xms1G -Xmx1G -server -Dlog4j.configuration=log4j.xml
-Dtangosol.coherence.cacheconfig=/xxx/coherence_config.xml
-Dtangosol.coherence.ttl=0
-Dtangosol.coherence.log=log4j
-Dtangosol.coherence.clusterport=5511
-Dtangosol.coherence.distributed.localstorage=true The other 2 JVMs will use the same JVM settings as above, except -Dtangosol.coherence.distributed.localstorage=false.
When I started the all servers in this order: data server -> one client jvm -> the other client jvm, I can see they all join into one cluster, and our application works fine.
Now, if I shutdown client1 and client2, and restarted them, the problems comes:
1) From the coherence log, I can see the client1 and client2 joined back in the cluster.
2) But when client1 is trying to get cache using the following api:
NamedCache cache = CacheFactory.getCache("cacheName");
Object o = (Object)cache.get(id);The cache object is there, but without any elements in it. So Object o will always to Null. But I know in this case, there is one element in the case, which I just put in before restarted client 1 and 2.
So in this case, I can get a cache object back, but without any element into it. This is not the case before the JVM restarted.
3) In the above case, the cache is defined as a replicated cache as following:
          <cache-mapping>
               <cache-name>cacheName</cache-name>
               <scheme-name>ReplicatedScheme</scheme-name>
          </cache-mapping>
          <replicated-scheme>
               <scheme-name>ReplicatedScheme</scheme-name>
               <backing-map-scheme>
                    <local-scheme>
                         <scheme-ref>unlimited-backing-map</scheme-ref>
                    </local-scheme>
               </backing-map-scheme>
          </replicated-scheme>
          
          <local-scheme>
               <scheme-name>unlimited-backing-map</scheme-name>
          </local-scheme>4) I tried to use the SimpleCacheExplorer example coming with the coherence to see if I can reproduce this case. But I can not. I use the same coherence.xml as our application. I used the same cache name in the SimpleCacheExplorer as in our application. I started 3 JVMs, one with localstorage=true, the other 2 with localstorage=false. Everytime, I restarted the other 2 JVMs, it can join back the cluster and get the value for the original key. So I am not sure which part in our application breaks this.
5) I list the coherence log below from our application. I added 2-3 lines comments just to list what happened then.
Any idea or hints about why this is happenning? Thanks for your help.

Here is the log:
############ start the data server
2009-11-19 14:55:07,389 Coherence Logger@1398577124 3.4.2/411 INFO   2009-11-19 14:55:07.132/65.613 Oracle Coherence 3.4.2/411 <Info> (thread=http-8080-1, member=n/a): Loaded operational configuration from resource "jar:file:/datacloud/trunk/install/apache-tomcat-6.0.18/webapps/datacloud/WEB-INF/lib/coherence.jar!/tangosol-coherence.xml"
2009-11-19 14:55:07,389 Coherence Logger@1398577124 3.4.2/411 INFO   2009-11-19 14:55:07.187/65.668 Oracle Coherence 3.4.2/411 <Info> (thread=http-8080-1, member=n/a): Loaded operational overrides from resource "jar:file:/datacloud/trunk/install/apache-tomcat-6.0.18/webapps/datacloud/WEB-INF/lib/coherence.jar!/tangosol-coherence-override-dev.xml"
2009-11-19 14:55:07,389 Coherence Logger@1398577124 3.4.2/411 DEBUG 2009-11-19 14:55:07.187/65.668 Oracle Coherence 3.4.2/411 <D5> (thread=http-8080-1, member=n/a): Optional configuration override "/tangosol-coherence-override.xml" is not specified
2009-11-19 14:55:07,389 Coherence Logger@1398577124 3.4.2/411 DEBUG 2009-11-19 14:55:07.190/65.671 Oracle Coherence 3.4.2/411 <D5> (thread=http-8080-1, member=n/a): Optional configuration override "/custom-mbeans.xml" is not specified
2009-11-19 14:55:07,389 Coherence Logger@1398577124 3.4.2/411 DEBUG
Oracle Coherence Version 3.4.2/411
Grid Edition: Development mode
Copyright (c) 2000-2009 Oracle. All rights reserved.
2009-11-19 14:55:08,356 Coherence Logger@9218328 3.4.2/411 DEBUG 2009-11-19 14:55:08.351/863.022 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=1): Member(Id=2, Timestamp=2009-11-19 14:55:08.15, Address=10.241.59.246:8089, MachineId=49398, Location=site:americas.nokia.com,machine:daec-linuxvpn059246,process:30265, Role=ApacheCatalinaStartupBootstrap) joined Cluster with senior member 1
2009-11-19 14:55:08,360 Coherence Logger@9230760 3.4.2/411 INFO   2009-11-19 14:55:08.360/66.841 Oracle Coherence GE 3.4.2/411 <Info> (thread=Cluster, member=n/a): This Member(Id=2, Timestamp=2009-11-19 14:55:08.15, Address=10.241.59.246:8089, MachineId=49398, Location=site:americas.nokia.com,machine:daec-linuxvpn059246,process:30265, Role=ApacheCatalinaStartupBootstrap, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=1) joined cluster "cluster:0xC3E1" with senior Member(Id=1, Timestamp=2009-11-19 14:40:47.04, Address=10.241.59.246:8088, MachineId=49398, Location=site:americas.nokia.com,machine:daec-linuxvpn059246,process:29459, Role=NokiaDcServerDataServer, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=1)
2009-11-19 14:55:08,386 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service ExpiryService with senior member 1
2009-11-19 14:55:08,386 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistSearchService with senior member 1
2009-11-19 14:55:08,386 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistributedCache with senior member 1
2009-11-19 14:55:08,386 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistSmallLRUService with senior member 1
2009-11-19 14:55:08,386 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistSmallLFUService with senior member 1
2009-11-19 14:55:08,386 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistSmallHYBRIDService with senior member 1
2009-11-19 14:55:08,386 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistMediumLRUService with senior member 1
2009-11-19 14:55:08,386 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistMediumLFUService with senior member 1
2009-11-19 14:55:08,386 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistMediumHYBRIDService with senior member 1
2009-11-19 14:55:08,386 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistLargeLRUService with senior member 1
2009-11-19 14:55:08,386 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistLargeLFUService with senior member 1
2009-11-19 14:55:08,387 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.385/66.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistLargeHYBRIDService with senior member 1
2009-11-19 14:55:08,682 Coherence Logger@9218328 3.4.2/411 DEBUG 2009-11-19 14:55:08.681/863.352 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=1): Member 2 joined Service DistributedCache with senior member 1
2009-11-19 14:55:08,686 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.686/67.167 Oracle Coherence GE 3.4.2/411 <D5> (thread=DistributedCache, member=2): Service DistributedCache joined the cluster with senior service member 1
2009-11-19 14:55:08,690 Coherence Logger@9218328 3.4.2/411 DEBUG 2009-11-19 14:55:08.686/863.357 Oracle Coherence GE 3.4.2/411 <D5> (thread=DistributedCache, member=1): Service DistributedCache: sending ServiceConfigSync containing 258 entries to Member 2
2009-11-19 14:55:08,693 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:08.693/67.174 Oracle Coherence GE 3.4.2/411 <D5> (thread=DistributedCache, member=2): Service DistributedCache: received ServiceConfigSync containing 258 entries
2009-11-19 14:55:09,593 Coherence Logger@9218328 3.4.2/411 DEBUG 2009-11-19 14:55:09.593/864.264 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=1): TcpRing: connecting to member 2 using TcpSocket{State=STATE_OPEN, Socket=Socket[addr=/10.241.59.246,port=8089,localport=37475]}
2009-11-19 14:55:09,597 Coherence Logger@9230760 3.4.2/411 DEBUG 2009-11-19 14:55:09.596/68.077 Oracle Coherence GE 3.4.2/411 <D5> (thread=TcpRingListener, member=2): TcpRing: connecting to member 1 using TcpSocket{State=STATE_OPEN, Socket=Socket[addr=/10.241.59.246,port=37475,localport=8089]}
2009-11-19 14:55:12,673 Coherence Logger@1144704103 3.4.2/411 INFO   2009-11-19 14:55:12.508/172.386 Oracle Coherence 3.4.2/411 <Info> (thread=pool-2-thread-1, member=n/a): Loaded operational configuration from resource "jar:file:/datacloud/trunk/install/lib/coherence.jar!/tangosol-coherence.xml"
2009-11-19 14:55:12,673 Coherence Logger@1144704103 3.4.2/411 INFO   2009-11-19 14:55:12.514/172.392 Oracle Coherence 3.4.2/411 <Info> (thread=pool-2-thread-1, member=n/a): Loaded operational overrides from resource "jar:file:/datacloud/trunk/install/lib/coherence.jar!/tangosol-coherence-override-dev.xml"
2009-11-19 14:55:12,673 Coherence Logger@1144704103 3.4.2/411 DEBUG 2009-11-19 14:55:12.514/172.392 Oracle Coherence 3.4.2/411 <D5> (thread=pool-2-thread-1, member=n/a): Optional configuration override "/tangosol-coherence-override.xml" is not specified
2009-11-19 14:55:12,673 Coherence Logger@1144704103 3.4.2/411 DEBUG 2009-11-19 14:55:12.517/172.395 Oracle Coherence 3.4.2/411 <D5> (thread=pool-2-thread-1, member=n/a): Optional configuration override "/custom-mbeans.xml" is not specified
2009-11-19 14:55:12,673 Coherence Logger@1144704103 3.4.2/411 DEBUG
Oracle Coherence Version 3.4.2/411
Grid Edition: Development mode
Copyright (c) 2000-2009 Oracle. All rights reserved.
2009-11-19 15:04:23,811 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:23.811/62.250 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistSmallLRUService with senior member 1
2009-11-19 15:04:23,811 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:23.811/62.250 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistSmallLFUService with senior member 1
2009-11-19 15:04:23,812 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:23.811/62.250 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistSmallHYBRIDService with senior member 1
2009-11-19 15:04:23,812 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:23.812/62.251 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistMediumLRUService with senior member 1
2009-11-19 15:04:23,812 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:23.812/62.251 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistMediumLFUService with senior member 1
2009-11-19 15:04:23,812 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:23.812/62.251 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistMediumHYBRIDService with senior member 1
2009-11-19 15:04:23,812 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:23.812/62.251 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistLargeLRUService with senior member 1
2009-11-19 15:04:23,812 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:23.812/62.251 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistLargeLFUService with senior member 1
2009-11-19 15:04:23,812 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:23.812/62.251 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistLargeHYBRIDService with senior member 1
2009-11-19 15:04:23,946 Coherence Logger@9218328 3.4.2/411 DEBUG 2009-11-19 15:04:23.946/1418.617 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=1): Member 2 joined Service DistributedCache with senior member 1
2009-11-19 15:04:23,953 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:23.952/62.391 Oracle Coherence GE 3.4.2/411 <D5> (thread=DistributedCache, member=2): Service DistributedCache joined the cluster with senior service member 1
2009-11-19 15:04:23,955 Coherence Logger@9218328 3.4.2/411 DEBUG 2009-11-19 15:04:23.953/1418.624 Oracle Coherence GE 3.4.2/411 <D5> (thread=DistributedCache, member=1): Service DistributedCache: sending ServiceConfigSync containing 259 entries to Member 2
2009-11-19 15:04:23,959 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:23.959/62.398 Oracle Coherence GE 3.4.2/411 <D5> (thread=DistributedCache, member=2): Service DistributedCache: received ServiceConfigSync containing 259 entries
2009-11-19 15:04:24,513 Coherence Logger@879081272 3.4.2/411 INFO   2009-11-19 15:04:24.351/181.083 Oracle Coherence 3.4.2/411 <Info> (thread=RMI TCP Connection(4)-127.0.0.2, member=n/a): Loaded operational configuration from resource "jar:file:/datacloud/trunk/install/lib/coherence.jar!/tangosol-coherence.xml"
2009-11-19 15:04:24,514 Coherence Logger@879081272 3.4.2/411 INFO   2009-11-19 15:04:24.355/181.087 Oracle Coherence 3.4.2/411 <Info> (thread=RMI TCP Connection(4)-127.0.0.2, member=n/a): Loaded operational overrides from resource "jar:file:/datacloud/trunk/install/lib/coherence.jar!/tangosol-coherence-override-dev.xml"
2009-11-19 15:04:24,514 Coherence Logger@879081272 3.4.2/411 DEBUG 2009-11-19 15:04:24.355/181.087 Oracle Coherence 3.4.2/411 <D5> (thread=RMI TCP Connection(4)-127.0.0.2, member=n/a): Optional configuration override "/tangosol-coherence-override.xml" is not specified
2009-11-19 15:04:24,514 Coherence Logger@879081272 3.4.2/411 DEBUG 2009-11-19 15:04:24.358/181.090 Oracle Coherence 3.4.2/411 <D5> (thread=RMI TCP Connection(4)-127.0.0.2, member=n/a): Optional configuration override "/custom-mbeans.xml" is not specified
2009-11-19 15:04:24,514 Coherence Logger@879081272 3.4.2/411 DEBUG
Oracle Coherence Version 3.4.2/411
Grid Edition: Development mode
Copyright (c) 2000-2009 Oracle. All rights reserved.
2009-11-19 15:04:24,546 Coherence Logger@879081272 3.4.2/411 INFO   2009-11-19 15:04:24.546/181.278 Oracle Coherence GE 3.4.2/411 <Info> (thread=RMI TCP Connection(4)-127.0.0.2, member=n/a): Loaded cache configuration from file "/datacloud/trunk/install/conf/coherence_config.xml"
2009-11-19 15:04:24,760 Coherence Logger@879081272 3.4.2/411 WARN   2009-11-19 15:04:24.760/181.492 Oracle Coherence GE 3.4.2/411 <Warning> (thread=RMI TCP Connection(4)-127.0.0.2, member=n/a): UnicastUdpSocket failed to set receive buffer size to 1428 packets (2096304 bytes); actual size is 89 packets (131071 bytes). Consult your OS documentation regarding increasing the maximum socket buffer size. Proceeding with the actual value may cause sub-optimal performance.
2009-11-19 15:04:24,786 Coherence Logger@9218328 3.4.2/411 DEBUG 2009-11-19 15:04:24.785/1419.456 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=1): TcpRing: connecting to member 2 using TcpSocket{State=STATE_OPEN, Socket=Socket[addr=/10.241.59.246,port=8089,localport=48995]}
2009-11-19 15:04:24,787 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:24.787/63.226 Oracle Coherence GE 3.4.2/411 <D5> (thread=TcpRingListener, member=2): TcpRing: connecting to member 1 using TcpSocket{State=STATE_OPEN, Socket=Socket[addr=/10.241.59.246,port=48995,localport=8089]}
2009-11-19 15:04:24,882 Coherence Logger@879081272 3.4.2/411 DEBUG 2009-11-19 15:04:24.882/181.614 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Service Cluster joined the cluster with senior service member n/a
2009-11-19 15:04:25,118 Coherence Logger@9218328 3.4.2/411 DEBUG 2009-11-19 15:04:25.112/1419.783 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=1): Member(Id=3, Timestamp=2009-11-19 15:04:24.917, Address=10.241.59.246:8090, MachineId=49398, Location=site:americas.nokia.com,machine:daec-linuxvpn059246,process:30657, Role=NokiaDcServerBuildBuildServer) joined Cluster with senior member 1
2009-11-19 15:04:25,118 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:25.115/63.554 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=2): Member(Id=3, Timestamp=2009-11-19 15:04:24.917, Address=10.241.59.246:8090, MachineId=49398, Location=site:americas.nokia.com,machine:daec-linuxvpn059246,process:30657, Role=NokiaDcServerBuildBuildServer) joined Cluster with senior member 1
2009-11-19 15:04:25,120 Coherence Logger@9242415 3.4.2/411 INFO   2009-11-19 15:04:25.120/181.852 Oracle Coherence GE 3.4.2/411 <Info> (thread=Cluster, member=n/a): This Member(Id=3, Timestamp=2009-11-19 15:04:24.917, Address=10.241.59.246:8090, MachineId=49398, Location=site:americas.nokia.com,machine:daec-linuxvpn059246,process:30657, Role=NokiaDcServerBuildBuildServer, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=1) joined cluster "cluster:0xC3E1" with senior Member(Id=1, Timestamp=2009-11-19 14:40:47.04, Address=10.241.59.246:8088, MachineId=49398, Location=site:americas.nokia.com,machine:daec-linuxvpn059246,process:29459, Role=NokiaDcServerDataServer, Edition=Grid Edition, Mode=Development, CpuCount=2, SocketCount=1)
2009-11-19 15:04:25,127 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.127/181.859 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member(Id=2, Timestamp=2009-11-19 15:04:23.541, Address=10.241.59.246:8089, MachineId=49398, Location=site:americas.nokia.com,machine:daec-linuxvpn059246,process:30753, Role=ApacheCatalinaStartupBootstrap) joined Cluster with senior member 1
2009-11-19 15:04:25,131 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.131/181.863 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service ExpiryService with senior member 1
2009-11-19 15:04:25,131 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.131/181.863 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistSearchService with senior member 1
2009-11-19 15:04:25,132 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.132/181.864 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistributedCache with senior member 1
2009-11-19 15:04:25,132 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.132/181.864 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistSmallLRUService with senior member 1
2009-11-19 15:04:25,132 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.132/181.864 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistSmallLFUService with senior member 1
2009-11-19 15:04:25,133 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.132/181.864 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistSmallHYBRIDService with senior member 1
2009-11-19 15:04:25,133 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.133/181.865 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistMediumLRUService with senior member 1
2009-11-19 15:04:25,133 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.133/181.865 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistMediumLFUService with senior member 1
2009-11-19 15:04:25,133 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.133/181.865 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistMediumHYBRIDService with senior member 1
2009-11-19 15:04:25,133 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.133/181.865 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistLargeLRUService with senior member 1
2009-11-19 15:04:25,133 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.133/181.865 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistLargeLFUService with senior member 1
2009-11-19 15:04:25,133 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.133/181.865 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 1 joined Service DistLargeHYBRIDService with senior member 1
2009-11-19 15:04:25,134 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.134/181.866 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=n/a): Member 2 joined Service DistributedCache with senior member 1
2009-11-19 15:04:25,219 Coherence Logger@9218328 3.4.2/411 DEBUG 2009-11-19 15:04:25.219/1419.890 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=1): Member 3 joined Service ReplicatedCache with senior member 3
2009-11-19 15:04:25,220 Coherence Logger@9249408 3.4.2/411 DEBUG 2009-11-19 15:04:25.220/63.659 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=2): Member 3 joined Service ReplicatedCache with senior member 3
2009-11-19 15:04:25,223 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:25.223/181.955 Oracle Coherence GE 3.4.2/411 <D5> (thread=ReplicatedCache, member=3): Service ReplicatedCache joined the cluster with senior service member 3
2009-11-19 15:04:26,310 Coherence Logger@9242415 3.4.2/411 DEBUG 2009-11-19 15:04:26.309/183.041 Oracle Coherence GE 3.4.2/411 <D5> (thread=Cluster, member=3): TcpRing: connecting to member 1 using TcpSocket{State=STATE_OPEN, Socket=Socket[addr=/10.241.59.246,port=8088,localport=58713]}
2009-11-19 15:04:26,312 Coherence Logger@9218328 3.4.2/411 DEBUG 2009-11-19 15:04:26.312/1420.983 Oracle Coherence GE 3.4.2/411 <D5> (thread=TcpRingListener, member=1): TcpRing: connecting to member 3 using TcpSocket{State=STATE_OPEN, Socket=Socket[addr=/10.241.59.246,port=58713,localport=8088]}

Questions on Client Failver and Fast Failover

've few questions regarding Client Failover and Fast Faiolver of Oracle Database HA. Before I ask those questions I would like to explain my environment. Below are the details.
- We have two physical locations called 'ABC' and 'PQR'
- ABC is the primary site.
- PQR is the standby site.
- In ABC, we have Oracle RAC database (11.2.0.2) with two nodes.
- In PQR, we have a single server standalone database (11.2.0.2) with ASM. This is not a RAC.
- Data Guard has been configured between ABC and PQR and it is working as expected.
- Please note that we have a licence for Active Data Guard.
- We have Oracle Identity Management products at both ABC and PQR and they are going to use RAC database as a primary database which is in ABC.
- We did not configure Data Guard broker yet.
We want to achieve below goals:
Goal 1:
Whenever RAC primary goes down completely, standby database should become primary database AUTOMATICALLY and it should allow read/write operation.
I guess this is called 'Fast Failover'. Please let me know if I am wrong.
Questions :
- To make this happen, Do I need to configure Data Guard Broker so that standy database becomes primary when RAC goes down completely with planned or unplanned outage.
- Let's say RAC goes down completely, how long does Data Guard broker take to make standby db as Primary.
- What about the client/application who already connected to RAC.
- Let's standby DB has become as primary and after sometime if RAC comes back , Does data guard automatically changes the role of RAC to primary ?
Goal 2:
As I explained above, all Oracle IDM products and applications speak to RAC database they only know about RAC database which is primary.They are not aware of standby database.
- Whenever a client session is in progress with RAC primary database, if RAC goes down completely , we would like to expect client session should get transferred standby datbase without loosing session information . However before this happens, standby database should become primary becuase client session may perform write operations.
- Whenever a client is trying to connect to RAC prmary and assume RAC is completely down, we would like to expect client connections should get transferred to standby database.
However before this happens, standby database should become primary becuase client session may perform write operations.
As per my knowledge, above scenarios are called 'client failver'. Please let me know if I am wrong.
Questions:
1. Please throw some light to achieve above features.
2. As per my understanding, before client failover happens, fast failover should have already occured and standby should get switch to primary role. I guess all this happens through TIMEOUT parameters. What are those.
Could you please help ?
Thanks

859875 wrote:
Goal 1:
Whenever RAC primary goes down completely, standby database should become primary database AUTOMATICALLY and it should allow read/write operation.
I guess this is called 'Fast Failover'. Please let me know if I am wrong.You are correct.
>
Questions :
- To make this happen, Do I need to configure Data Guard Broker so that standy database becomes primary when RAC goes down completely with planned or unplanned outage.Yes (you can also use Grid Control that will use Data Guard Broker).
>
Goal 2:
As I explained above, all Oracle IDM products and applications speak to RAC database they only know about RAC database which is primary.They are not aware of standby database.
- Whenever a client session is in progress with RAC primary database, if RAC goes down completely , we would like to expect client session should get transferred standby datbase without loosing session information:This is not possible: it is possible only for SELECT statement and only in a single RAC database.
You can find some interesting documents on MAA home page (best pratices, case studies...):
http://www.oracle.com/technetwork/database/features/availability/maa-090890.html

Client handoff and Roaming

Similar Messages

Maybe you are looking for