Spotlight installed on a cluster with loading balancing will give the following error when connecting:
"This profile appears to have load balancing set on. It cannot be diagnosed due to potential problems with failover"
Error occurs when the tnsnames entry is set to (LOAD_BALANCE = ON) instead of (LOAD_BALANCE = OFF)
If you connect Spotlight on Oracle (SoO) to an Oracle cluster, we require that you connect to a TNSNames entry for one of the instances in the cluster, rather than a TNSNames entry that has the keyword LOAD_BALANCE or FAILOVER in it (in which case Oracle will choose which instance to connect you to).
The reason is because if you connect SoO to a cluster in such a way that Oracle might try to switch Spotlight's session to another instance on the cluster, then SoO will produce errors in that scenario. Basically SoO is not designed to have its Oracle session moved from one instance to another instance. So we placed that limitation in the connection logic of SoO. So although setting load balancing to ON is not officially supported you can connect SoO to a cluster, but in doing so, you have to specify that it connects to a specific instance in that cluster.
Note that if you want to diagnose a RAC, you should use Spotlight on Oracle RAC. Make sure you are creating a Spotlight on RAC connection rather than a Spotlight on Oracle connection. When you bring up the connection manager, be sure to click on "Spotlight on Oracle RAC" on the left panel before you create a new connection profile.
© ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center