Hi.
The situation is:
We have 2 nodes in cluster. On the cluster the ORACLE DB server is running. There are 5 DB instances. Each has it's own floating ip adress. If one instance fails, the cluster do DB switch to other cluster node. It means:
DB1 is fails on node1, then it is switched to node2.
So DB1 is run on node2 but all others DBinstances are still on node1.
Can the agent handle such a DB cluster switching. I know how to bind agent for psychical cluster node on one virtual IP address.
But how to bind agent to run along with the active DBinstance node, not a psychical one.
So - whenever is the active database, the agent will work on this node and no matter of the facts, it has to manage also other node's databases.
That's the question.
(be or not to be)
active DB cluster node
For a similar problem with oracle RAC, I have used the loadbalancing method with a script that add or delete resources on the correspondent DB node active.
The script check if the DB switch and if occour deletes resources from that node and add in the other.
The best was connecting the DB switch with resources, when I done this I have used Patrol.
The script check if the DB switch and if occour deletes resources from that node and add in the other.
The best was connecting the DB switch with resources, when I done this I have used Patrol.
Agent switching has to be coordinated with DB siwtching. Agent is installed on a volume available to the active node only and configured to respond to the DB virtual hostname. When DB switching occurs, shutdown agent and unmount the volume in the outgoing node, then mount the volume and start the agent in the incoming node.
Yes, but .. agent can not be switched on other node, because it has to manage oracle jobs on first node. As it was said to me: switch to other oracle database node is not the server node switch.
so agent has to run on first and second server node, but has to determine on which server node one of the DBinstances is running. Others instances continue running on initial node.
so agent has to run on first and second server node, but has to determine on which server node one of the DBinstances is running. Others instances continue running on initial node.
- philmalmaison
- Nouveau
- Posts: 1148
- Joined: 08 Jun 2007 12:00
- Location: Ile de France