MCSG Extension for SAP

[Paul Barmettler]

dear experts,

I recently tried to start a SAP system with Release 6.2 on the adoptive node. It failed due to a script hang and failing RCF's. I have seen that the /usr/sap/SID/SYS/exe/run/sapstart was used instead of /home/sidadm/sapstart_[hostname]_[SAPID] as usual with SAP Release < 4.6D (see attached log file)
What ist the reason for that, and how can I avoid it?
btw: starting the package on the primary node works fine.
Revisions:
SGeSAP Revision 3.09.00 / MCSG 11.15 on HP-UX 11.11

Thanks for your responses

[Geoff Wild]

I avoid it by using a basic control script and use customer_defined_run_commands to start SAP:

function customer_defined_run_cmds
{
# ADD customer defined run commands.
: # do nothing instruction, because a function must contain some command.
# start PRD
/etc/cmcluster/PRDDBCI/sapdbci.cntl startDBCI IPR
test_return 51
# start OEM Intelligent Agent
su - oraprd -c "/oracle/PRD/db/scripts/start_agent.sh"
# source oracle cron
su - oraprd -c "crontab /oracle/PRD/db/crontabs/oraprd.cron"
# start samba
/opt/samba/bin/startsmb -w
}


Rgds...Geoff

[Paul Barmettler]

Hi Geoff,

we also use

function customer_defined_run_cmds
{
# ADD customer defined run commands.
# do nothing instruction, because a function must contain some command.

/etc/cmcluster/SID/sapdbci.cntl startDBCI SID
test_return 51
}

in our dbci.cntl file.
Any other hints?

[Duncan Edmonstone · Accepted solution]

Isn't this the problem described in the release notes:

http://docs.hp.com/en/B7885-90019/ch01s05.html#babdiiah

HTH

Duncan

[Geoff Wild]

Okay - check your function files in /etc/cmcluster -

FUNC_FILE=${FUNC_FILE:-/etc/cmcluster/sap.functions}
CUST_FILE=${CUST_FILE:-/etc/cmcluster/customer.functions}

See if they are different from primary node...

Rgds...Geoff