- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: SGeSAP 04.50 configuration problems
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2007 11:28 PM
07-30-2007 11:28 PM
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
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2007 01:24 AM
07-31-2007 01:24 AM
Re: SGeSAP 04.50 configuration problems
@ 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
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2007 02:20 AM
07-31-2007 02:20 AM
Re: SGeSAP 04.50 configuration problems
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
Any ideas what may cause this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2007 06:31 PM
07-31-2007 06:31 PM
SolutionAlthough 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-31-2007 07:40 PM
07-31-2007 07:40 PM
Re: SGeSAP 04.50 configuration problems
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-01-2007 12:04 AM
08-01-2007 12:04 AM