Hi Anil,
as already discussed via other channels - but should also be visible here to document the results - there are different methods to start a SAP system - you can do it by just starting the complete system including the Database, the central service instance and the dialog instance(s) using a startsap command. This is also why starting an entire SAP system using startsap could not be compaired with
starting the system with a cluster including resource monitoring.
The cluster (here pacemaker) is using sapcontrol and it is intended that the cluster starts the database and each SAP instance separately. This means you need to define a resource foe the database, a
resource for the central services instance (JAVA SCSnn) and a resource per application server instance (JAVA Jmm).
As in your case you want to start/stop the SAP system together, do not want to run Enqueue-Replication and likes to run all resources of a SAP system colocated - the easiest way to get this is to group all those resources in just one resource group.
And please use the most current packages (updates) available for SLES and SLE HA. It is important - just as an example: For SLE 11 HA SP2 only the update of the resource-agents package does contain
the newer SAPDatabase which is enabled to communicate with the sap host agent. This new method drastically strip down the configuration needs for a SAP Database. You do not longer need to configure the Java nor Directory parameters - they are even deprecated now.
Regards
Fabian