HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Service Guard Configuration for SAP
Operating System - HP-UX
1838230
Members
5982
Online
110125
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-10-2006 05:46 AM
04-10-2006 05:46 AM
Service Guard Configuration for SAP
HI
I am using the old sap.conf to stop the secondary failover central instance and application server with lines.
RMNR[0]=00 ; RMDEP[0]=0 ; RMADM[0]=ca2adm
RMDEPNR[0]=00 ; RMDEPHOST[0]=hpusam07 ; RMDEPPLATFORM[0]="HP-UX"
RMDEPNR[1]=-1
My application server is no longer running (does not exist) and I want to change these three lines so the central instance still stops, but it does not reference the app server.
Do I just comment out the second line indicating the hpusam07 application server? Or are there other changes also.
thanks
brad
I am using the old sap.conf to stop the secondary failover central instance and application server with lines.
RMNR[0]=00 ; RMDEP[0]=0 ; RMADM[0]=ca2adm
RMDEPNR[0]=00 ; RMDEPHOST[0]=hpusam07 ; RMDEPPLATFORM[0]="HP-UX"
RMDEPNR[1]=-1
My application server is no longer running (does not exist) and I want to change these three lines so the central instance still stops, but it does not reference the app server.
Do I just comment out the second line indicating the hpusam07 application server? Or are there other changes also.
thanks
brad
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-10-2006 08:43 AM
04-10-2006 08:43 AM
Re: Service Guard Configuration for SAP
I am not sure about the structure of the old sap functions extension but it is done exactly the way you described for the systems which are no longer running, i.e., just comment out the lines referencing that particular server(s) then halt the package or cluster. Sorry I do not have first hand experience with the older SAP functions, hence I can not give you a definitive answer.
My educated advise is to watch the package log, as the it is halting and if there is a long delay where the script is trying to reach the non-existent server/instance, on a separate terminal window, run ps -ef commands and grep for the some meaningful patterns on the log line where the process got stuck. When you find the culprit, just kill the process and package halt should continue with the next step.
Hope this helps
My educated advise is to watch the package log, as the it is halting and if there is a long delay where the script is trying to reach the non-existent server/instance, on a separate terminal window, run ps -ef commands and grep for the some meaningful patterns on the log line where the process got stuck. When you find the culprit, just kill the process and package halt should continue with the next step.
Hope this helps
________________________________
UNIX because I majored in cryptology...
UNIX because I majored in cryptology...
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