The best is to go with the standby database and it would be more easier to handle with less hassel. Here is a pot hole on the approach that you are about to try. Solution Description:
When a user requests to connect to an <alias>, SQL*Net will randomly choose one
of the addresses in the address list. If that address fails for any reason,
SQL*Net will not choose another address in the address list, it will return
the appropriate error.
Please note that in this example all three addresses use the same protocol and
host. If you are running Parallel Server, then your addresses in the address
list can use different hosts. Also, each address in the address list can use
If you are using Parallel Server and want to use load balancing across
multiple servers, the sid name on each server must be the same.
Talkin about backup server my boss asked me what high availability does Oracle offer, I mentioned Parallel Server & Advanced Replication. Our enviroment is already using Sun Cluster technology in a data center so I told him that OPS would offer availability + load balancing now he asks me about Replication I went a bit stoned because I think Replication is really for disasters like the whole data center gets blown up and we would have another replication in another city. And I dont see much point of having two server replicating each other in the same building.
Anyone have a suggestion of using OPS or Replication? I would guess OPS is cheaper to setup?
I didnt even mention standby database because if OPS is used we get availability and load balancing, with Raid 5 we have redundant disks in our situation so in case of disk corruption we can still recover, would standby database provide any improvement in case we lose a disk for whatever reason in the enviroment we are?
By the way since I am not an expert with Solaris does anyone know if Sun Cluster offers load balancing for database servers? (As far as I know it only offers availability)