Re: SAPInstance does not start and asking for START_PROFILE

Fabian Herschel <[email protected]> Wed, 14 Jan 2015 20:46:59 +0100
Newsgroups gmane.linux.highavailability.user
Message-ID <[email protected]>
Hi Muhammad,

could you try:
primitive SAPInst-DVEBMGS00 ocf:heartbeat:SAPInstance \
op monitor interval="120" timeout="60" \
op start interval="0" timeout="300" \
op stop interval="0" timeout="300" \
params InstanceName="TLP_DVEBMGS00_thltlp"
DIR_EXECUTABLE="/usr/sap/TLP/DVEBMGS00/exe"
START_PROFILE="/sapmnt/TLP/profile/TLP_DVEBMGS00_thltlp"

Or even let the parameters DIR_EXECUTABLE and START_PROFILE unset, so 
SAPInstance could use the automatical detection.

If you set the param START_PROFILE it must be a full file path NOT 
relative to DIR_PROFILE.

Hope that helps
Best regards
Fabian

On 01/14/2015 08:12 PM, Muhammad Sharfuddin wrote:
> OS: SLES 11 SP 3
> pacemaker-1.1.9-0.19.102
> corosync-1.4.5-0.18.15
> resource-agents-3.9.5-0.32.22
>
> starting the SAP Instance resource fails with following errors:
>
> Jan 14 18:22:16 thltlp1 SAPInstance(SAPInst-DVEBMGS00)[50450]: ERROR:
> Expected
> TLP_DVEBMGS00_thltlp to be the instance START profile, please set
> START_PROFILE
> parameter!
> Jan 14 18:22:16 thltlp1 crmd[47231]:   notice: process_lrm_event: LRM
> operation
> SAPInst-DVEBMGS00_start_0 (call=81, rc=6, cib-update=66, confirmed=true)
> not configured
>
> following is the resource configurations:
> primitive SAPInst-DVEBMGS00 ocf:heartbeat:SAPInstance \
> op monitor interval="120" timeout="60" \
> op start interval="0" timeout="300" \
> op stop interval="0" timeout="300" \
> params InstanceName="TLP_DVEBMGS00_thltlp"
> DIR_EXECUTABLE="/usr/sap/TLP/DVEBMGS00/exe"
> START_PROFILE="TLP_DVEBMGS00_thltlp" DIR_PROFILE="/sapmnt/TLP/profile"
>
> i.e START_PROFILE is configured but cluster is not starting the SAP
> Instance.
>
> Please help
>

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems