Skip to Content

SAP on SUSE HA cluster

Dear Friends,

Need your help to configure SAP on SUSE HA cluster.

We have to configure SAP NW 7.3 as JAVA on SUSE HA CLUSTER. Currently SAP is running on oracle 11g and SUSE 11 SP3.

SUSE team has configured the cluster for IP, File system, Oracle and SAP.

Cluster Resource for IP, File system and oracle is starting without any issue. But the SAP Resource is failing to start. After all there details checks they are pointing this is problem related to SAP profile.

Now i am confused, what is a profile problem, Becuase SAP start stop us wroking fine when i am doing manual start and stop of SAP. but Cluster resource is not able to start the SAP.

If it is a problem problem, then what changes has to be done in profile. did any body face this issue or any idea what are the changes has to be done in profile from SUSE Cluster point of view.

Thanks,

Anil Bhandary

Add a comment
10|10000 characters needed characters exceeded

Related questions

4 Answers

  • Posted on Nov 28, 2013 at 11:54 AM

    Please follow the best practices provided by SUSE.

    You can find those best practices at https://www.suse.com/products/sles-for-sap/resource-library/sap-best-practices.html

    In your case the simple stack best practice (http://www.novell.com/docrep/2012/01/sap_on_sle_simple_stack.PDF) is matching best. You only need to transfer from an ABAP to an JAVA stack and from MaxDB to Oracle.

    The latter is very easy. Just use parameter DBTYPE="ORA" instead of DBTYPE="ADA". And adjust the SID parameter to your SID.

    For the SAP Instances you need to start the SCS (central services) first than Java Application Servers.

    So like an example SCS10 should be started before you start J20.

    The example in the simple stack document covers this by using a resource group including IP, LVM, FS, SAPDatabase (MaxDB Database), SAPInstance (ASCSxx) and SAPInstance (DVEBMGSyy) .

    You can easily adapt that to:

    a resource group including IP, LVM, FS, SAPDatabase (Oracle Database), SAPInstance (SCSxx) and SAPInstance (Jyy) .

    And do NOT add a Oracle Listener resource to the cluster as this service is controlled by the SAPDatabase resource agent.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 25, 2013 at 07:56 AM

    Hi,

    Follow the note, this will help..

    OSS 1763512 - Support details for SUSE Linux Enterprise High Availability

    OSS 1056161 - SUSE Priority Support for SAP applications

    BR,

    Prabhakar

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 25, 2013 at 10:41 AM

    Anil Bhandary wrote:

    But the SAP Resource is failing to start. After all there details checks they are pointing this is problem related to SAP profile.

    Now i am confused, what is a profile problem, Becuase SAP start stop us wroking fine when i am doing manual start and stop of SAP. but Cluster resource is not able to start the SAP.

    If it is a problem problem, then what changes has to be done in profile. did any body face this issue or any idea what are the changes has to be done in profile from SUSE Cluster point of view.

    Can you provide logs or more information?

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 02, 2013 at 04:46 PM

    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

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.