Skip to ContentSkip to Footer
Start of content
- Community Home
- >
- Servers and Operating Systems
- >
- Operating System - HP-UX
- >
- Serviceguard
- >
- MC/ServiceGuard and application start/stop scripts
Serviceguard
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
-
- Forums
-
Blogs
- Hybrid Cloud
- Edge
- Data & AI
- Working in Tech
- AI Insights
- Alliances
- Around the Storage Block
- Behind the scenes at Labs
- Careers in Tech
- HPE Storage Tech Insiders
- Inspiring Progress
- IoT at the Edge
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Russia
- HPE Blog, UK & Ireland
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-09-2002 10:56 AM
12-09-2002 10:56 AM
Re: MC/ServiceGuard and application start/stop scripts
David.
First: you need su - user -c
(su minus user)
to activate all environment variables.
Just to ensure that I also added . .profile; before proshut. If .profile you can set any env. variables your DB requires.
If you created package files from the template, you have all variables you need for MC/SG. Env variables required by application has to be initalized in your startup/shutdown script.
If you login as proguser, you can issue commands to shutdown your database, right?
So, I do not see any reasons for the line I mentioned earlier to fail to do the job.
WAIT is required, so script will not start umount and vgchage before DB is down.
Hope this helps,
0leg
First: you need su - user -c
(su minus user)
to activate all environment variables.
Just to ensure that I also added . .profile; before proshut. If .profile you can set any env. variables your DB requires.
If you created package files from the template, you have all variables you need for MC/SG. Env variables required by application has to be initalized in your startup/shutdown script.
If you login as proguser, you can issue commands to shutdown your database, right?
So, I do not see any reasons for the line I mentioned earlier to fail to do the job.
WAIT is required, so script will not start umount and vgchage before DB is down.
Hope this helps,
0leg
Professionals will prevail ...
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-11-2002 06:25 AM
12-11-2002 06:25 AM
Re: MC/ServiceGuard and application start/stop scripts
This problem has been fixed! After several days of working with HP on what could possibly be happening, I talked with an engineer that said that I needed to load patch PHSS_26270 in order to remain on a supported version of MCSG. I loaded this patch last night and all of my problems went away. Everything works great now! Thanks for all of your help.
- « Previous
-
- 1
- 2
- Next »
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.
End of content
United States
Hewlett Packard Enterprise International
Communities
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP