What are the challenges of RAC with Dbvisit Replicate?
• The database instances can go up and down
• Instances can be added and dropped
• The machine running Replicate can go down
• Replicate can connect to database that goes down
The concepts are similar for any clusterware involved, examples are provided for Oracle Clusterware 11.2
Best Practices
| Note |
|---|
Unless noted otherwise, the practices are same for mine, apply and optional fetcher. |
...
To create an application VIP, use the following syntax:
| Section |
|---|
| Column |
|---|
| | Panel |
|---|
| appvipcfg create -network=network_number -ip=ip_address -vipname=vip_name
-user=user_name [-group=group_name] [-failback=0 | 1]
|
Where network_number is the number of the network, ip_address is the IP address, vip_name is the nameof the VIP (we use dbvrepVIP further on), user_name is root (as root privileges are needed to reconfigure network interfaces). The default value of the -failback option is 0. If you set the option to 1, then the VIP (and therefore Replicate as well) fails back to the original node when it becomes available again. |
|
...