HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- instance profile problem with 11iv3, SGeSAP 5.0, M...
Operating System - HP-UX
1833300
Members
2970
Online
110051
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
12-03-2009 07:52 AM
12-03-2009 07:52 AM
instance profile problem with 11iv3, SGeSAP 5.0, MCSG 11.19
Bonjour,
I have a problem with instance profiles on a SAP BW cluster, kernel 6.40.
The SAP configuration is quite simple : one dbci, named una00019, in a legacy package. This package can failover to the AS server, named una00020, which is a simple dialog instance. When dbci fails over, AS server is stopped, so no package for the dialog instance. Relocatable IP for dbci package is named pbwdbci.
When I start the package, SAP is started by SGeSAP with the command :
"/usr/sap/PBW/SYS/exe/run/startsap r3 DVEBMGS00"
So SAP looks for start profile START_DVEBMGS00_una00019 on una00019, or START_DVEBMGS00_una00020 on una00020.
For the moment I guess it is a normal behavior.
When I stop the package, SGeSAP calls :
"/usr/sap/PBW/SYS/exe/run/stopsap r3 DVEBMGS00 pbwdbci"
Note the third parameter "pbwdbci" which is the relocatable IP.
Yes, but SAP looks for profile START_DVEBMGS00_pbwdbci instead of START_DVEBMGS00_una00019 or START_DVEBMGS00_una00020.
Yes but I have not configured such a start profile :-((((
I would expect that SGeSAP call stopsap without the third parameter.
So, did I missed something, or should I configure 3 profiles : one as una00019, one as una00020 and one as pbwdbci ?
Thanks in advance
Eric
I have a problem with instance profiles on a SAP BW cluster, kernel 6.40.
The SAP configuration is quite simple : one dbci, named una00019, in a legacy package. This package can failover to the AS server, named una00020, which is a simple dialog instance. When dbci fails over, AS server is stopped, so no package for the dialog instance. Relocatable IP for dbci package is named pbwdbci.
When I start the package, SAP is started by SGeSAP with the command :
"/usr/sap/PBW/SYS/exe/run/startsap r3 DVEBMGS00"
So SAP looks for start profile START_DVEBMGS00_una00019 on una00019, or START_DVEBMGS00_una00020 on una00020.
For the moment I guess it is a normal behavior.
When I stop the package, SGeSAP calls :
"/usr/sap/PBW/SYS/exe/run/stopsap r3 DVEBMGS00 pbwdbci"
Note the third parameter "pbwdbci" which is the relocatable IP.
Yes, but SAP looks for profile START_DVEBMGS00_pbwdbci instead of START_DVEBMGS00_una00019 or START_DVEBMGS00_una00020.
Yes but I have not configured such a start profile :-((((
I would expect that SGeSAP call stopsap without the third parameter.
So, did I missed something, or should I configure 3 profiles : one as una00019, one as una00020 and one as pbwdbci ?
Thanks in advance
Eric
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