concurrency violation

Most service groups are of type failover (the default) meaning it should only run on one system at any one time and it can fail over to another system, so if VCS detects a failover group is running on more than one node then it reports a Concurrency Violation and then tries to offline on the node that VCS did not online it on.

So in your situation resource App_saposcol in group sapgtsprd was onlined on mapibm625 outside of VCS control when it was already online on another system in the cluster so VCS offlined it:

2014/12/03 06:46:55 VCS NOTICE V-16-1-10167 Initiating manual offline of group sapgtsprd on system mapibm625

If group should run on 2 systems at the same time then you should configure group as Parallel (set group attribute Parallel = 1) and then group will run on all systems in the cluster at the same time.

Mike

Mike has perfectly pointed the cause , To add to what Mike said, if application has to run on more than 1 node, you need to enable parallel attribute. However the application should have intelligence to run on multiple nodes at the same time without causing issues to data because multiple application instances may access same database underneath which may cause issues to DB,

G