A pos system has a large application volume and a large data volume! Statistical analysis of historical transactions affects another application to a certain extent. The two applications are OLTP and OLAP respectively.
In fact, many projects have such two-party application requirements. recently, a large number of reading and downloading data from another system caused high CPU usage and high I/O usage. LINUX has a load of 104.
Therefore, application cutting is required for the new RAC. Two applications are deployed on two different instances at ordinary times. If one instance crashes, it is automatically switched to another instance.
Configure the RAC of the two nodes and add the service.
Srvctl add service-d POSDB-s posc-r 'posdb1'-a 'posdbdb'-P basic-e session
CRS_STAT-T under grid finds that both services are on one node. SERVICE_NAMES of both instances are POSC and POSWEB
The service runs to another instance only after the instance is restarted.
When this is not what we want, use reconnect.
The final process is fixed SERVICE_NAMES, which is invalid and disabled, and then effective and starts the service. Then the service goes to the location where it should be.
After testing, the switchover is possible, but after the instance is restored, the above service will not automatically run back to the original place.