Operating System - HP-UX
1834134 Members
2252 Online
110064 Solutions
New Discussion

Re: SGeSAP 04.50 configuration problems

 
SOLVED
Go to solution
Timo Louhelainen
Occasional Advisor

SGeSAP 04.50 configuration problems

Hi,

I'm configuring SGeSAP 4.50 & HP-UX 11.31 & SG 11.17.01. Now I'm trying to integrate Oracle & SAP start/stop to my SG package configuration, but getting errors from customer defined run commands.

My run command is:

. /etc/cmcluster/vcpdb1/sapwas.cntl start VCP

But I get this error:
"/etc/cmcluster/VCP/sapwas.cntl execution error - check call syntax in customer_defined_run|halt_commands."

I noticed that my start commands gets modified so that the package directory, /etc/cmcluster/vcpdb1, changes to /etc/cmcluster/VCP. So it seems that SGeSAP's startup scripts changes the package directory name to name.

I tested the startup with this command:
. /etc/cmcluster/vcpdb1/sapwas.cntl start vcpdb1 and then the startup command worked fine.

I looked SGeSAP 4.50 release notes, but didn't find anything related to this. Also there are no patches for SGeSAP 4.50 nor SG 11.17.01.

__
Timo
5 REPLIES 5
Stephen Doud
Honored Contributor

Re: SGeSAP 04.50 configuration problems

The Managing Serviceguard Extension for SAP, February 2007 (for 11iv3)
@ http://docs.hp.com/en/T2803-90004/T2803-90004.pdf
describes the implementation of the /etc/cmcluster/VCP/sapwas.cntl command on pages 138 and 143.

If you have implemented it correctly, then check sap.config in the package directory, or sap.config in more complicated setups (see pg 154)

FYI: There Release notes:
Serviceguard Extension for SAP Version B.04.50 Release Notes, February 2007
@ http://docs.hp.com/en/T2803-90003/T2803-90003.pdf
--or--
http://docs.hp.com/en/T2803-90003/index.html

... contain a compatibility matrix for SGeSAP and HPUX etc.

Timo Louhelainen
Occasional Advisor

Re: SGeSAP 04.50 configuration problems

I've done the configuration according to SGeSAP manual T2803-90004 (Feb-07) on the pages you mentioned. I also done the configuration according to page 154 for sap.conf. I've done this same configuration without any problems for HP-UX 11.23, SG 11.17 and SGeSAP 04.01.

But the problem is that package startup script /etc/cmcluster/vcpdb1/vcpdb1.sh fails directly when it tries to perform customer defined run commands (. /etc/cmcluster/vcpdb1/sapwas.cntl start VCP). It gives this error:
"/etc/cmcluster/VCP/sapwas.cntl execution error - check call syntax in customer_defined_run|halt_commands."
If I can understand correctly, it doesn't even start to perform this command.
As you can see from the errormsg that one of the sap scripts (I think it is
/etc/cmcluster/sap.functions) changes startup directory, defined command is /etc/cmcluster/vcpdb1/sapwas..... but the errormsg returns /etc/cmcluster/VCP/sapwas.... So it changes package directory name to which is the second argument for the sapwas.cntl -control file.

Any ideas what may cause this?
Carsten Krege
Honored Contributor
Solution

Re: SGeSAP 04.50 configuration problems

Unlike other applications integrated into SG, the SGeSAP expects all package scripts and sap*conf files to live in the /etc/cmcluster/ directory. YOu are not supposed to have a separate directory for each package. E.g. the CI, the DB and the DI packages should all be located in the same dir /etc/cmcluster/VCP. You should not use a directory /etc/cmcluster/vcpdb1.

Although this is different than usual, it helps a lot if you run multiple SAP Instances on a single machine and also it will be hard to get it work correctly if you do it your way. The scripts are really designed that you stick with the default naming conventions.

Carsten
-------------------------------------------------------------------------------------------------
In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move. -- HhGttG
Timo Louhelainen
Occasional Advisor

Re: SGeSAP 04.50 configuration problems

That's what I also figured out that I need to change directory structure under /etc/cmcluster and not have separate directories for DB and CI packages.

On the older version of SGeSAP it worked with 'non-standrd' directory names.

But anyway this answered to my question and solved the problem. I still need to discuss this with my customer.

Thank's for your help Carsten!

__
Timo
Timo Louhelainen
Occasional Advisor

Re: SGeSAP 04.50 configuration problems

.