HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Adding a new package to a cluster
Operating System - HP-UX
1833925
Members
3175
Online
110063
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
Go to solution
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
05-31-2006 02:58 AM
05-31-2006 02:58 AM
I had created the package scripts, edited the package ascii file, and edited the cluster ascii file with the new volume groups (because they are running OPS) for a new database in a Service Guard cluster. The DBAs needed to install their Oracle software, so I had the volume groups activated with a vgchange -a y.. In order for me to make this package part of the cluster, I need to de-activate the volume groups, then run the cmapplyconf -k -v -C cluster.ascii -P package.ascii to create the new binary..Does the cmapplyconf make the Volume groups sharable also? (vgchange -c y).. Then i will do a cmrunpkg pkkg to bring up the database on one of the nodes.. Please correct me if i am wrong..Thanks,,,Ed..
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2006 03:09 AM
05-31-2006 03:09 AM
Solution
The cmapplyconf does not make the VG sharable; however, once the vgchange -c y is done on any node for a given VG, it applies to all other nodes because that metadata are carried on the LVM disk themselves. You will need to do the vgimport on all potential adoptive nodes. I typically do this while the VG is not cluster aware (ie no -c y) and then as a last step, do the vgchange -c y on the node I intend to be the package's primary node.
If it ain't broke, I can fix that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2006 03:16 AM
05-31-2006 03:16 AM
Re: Adding a new package to a cluster
I had already imported the volume groups on the adoptive node.. I guess what you are saying is do the vgchange -a n VG first, then do the vgchange -c y VG to make them sharable, then do the cmapplyconf -k -v -C cluster.ascii -P pachage.ascii.. I appreciate your help... ed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-31-2006 08:06 AM
05-31-2006 08:06 AM
Re: Adding a new package to a cluster
Thank you for all your help... ed
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