HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SGeSAP: Problems configuring ASCS
Operating System - HP-UX
1832990
Members
2519
Online
110048
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
04-19-2007 03:00 AM
04-19-2007 03:00 AM
SGeSAP: Problems configuring ASCS
I am setting up a ServiceGuard package which is using DVEBMGS AND ASCS but the ASCS is not being used for replicated emqueue. The enqueue in our case is part of the DVEBMGS. We also have the DB and CI together in one package.
When looking at the Manual and sap.config it tells you to configure the CINAME to be DVEBMGS OR ASCS. I have set this to DVEBMGS as that is the one which has the central instance.
It doesn't seem to tell you how to configure in an ASCS as well as a DVEBMGS if you want both without having the ASCS in a separate package.
I have tried putting a separate startsap command for the ASCS in the customer_defined_run_commands and that does start it but the package falls over due to a communication problem from the dispatcher. I feel that rather than forcing it to start the ASCS in this way it should be configured in properly so the extensions handles is.
Has anyone got any ideas how this should be done properly?
Cheers
Nick.
When looking at the Manual and sap.config it tells you to configure the CINAME to be DVEBMGS OR ASCS. I have set this to DVEBMGS as that is the one which has the central instance.
It doesn't seem to tell you how to configure in an ASCS as well as a DVEBMGS if you want both without having the ASCS in a separate package.
I have tried putting a separate startsap command for the ASCS in the customer_defined_run_commands and that does start it but the package falls over due to a communication problem from the dispatcher. I feel that rather than forcing it to start the ASCS in this way it should be configured in properly so the extensions handles is.
Has anyone got any ideas how this should be done properly?
Cheers
Nick.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-19-2007 07:43 PM
04-19-2007 07:43 PM
Re: SGeSAP: Problems configuring ASCS
If you have an ASCS this is the central instance (therefore the CINAME is set to ASCS). In such a setup DVEBMGS is usually the name of the first application server (although I never understood why they could not simply stick to consistent and reasonable naming convention) and should be put under DNAME[0].
The enqueue should really be part of the ASCS.
Carsten
The enqueue should really be part of the ASCS.
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
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
04-19-2007 09:25 PM
04-19-2007 09:25 PM
Re: SGeSAP: Problems configuring ASCS
I have actually tried that
e.g.
CINAME=ASCS
CINR=30
CIRELOC=[virtual ip address of package]
but I am still hitting problems. It comes up for so long then the dispatcher monitor spots a problem and shuts the package down. I am getting this error:
(dispmon_monitor): ERROR: No handshake possible - dispatcher process of DVEBMGS00 locked or no communication possible
Incidentally I was also having problems as the IP address I used mapped to a hostname in the /etc/hosts file which didn't correspond with a profile name of the ASCS. I corrected that so it did start up but I am left wondering what this handshake problem is caused by. Any ideas?
e.g.
CINAME=ASCS
CINR=30
CIRELOC=[virtual ip address of package]
but I am still hitting problems. It comes up for so long then the dispatcher monitor spots a problem and shuts the package down. I am getting this error:
(dispmon_monitor): ERROR: No handshake possible - dispatcher process of DVEBMGS00 locked or no communication possible
Incidentally I was also having problems as the IP address I used mapped to a hostname in the /etc/hosts file which didn't correspond with a profile name of the ASCS. I corrected that so it did start up but I am left wondering what this handshake problem is caused by. Any ideas?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP