HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- executing swremove
Operating System - HP-UX
1834931
Members
2578
Online
110071
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
07-03-2006 09:39 AM
07-03-2006 09:39 AM
Hello , try remove the patch in state corrupt, the swremove finish successfully , when execute swlist -l fileset -a state |grep corru the ouput is :
PHCO_29382.UUCP corrupt
PHSS_33901.CORE-64SLIB corrupt
PHSS_33901.CORE-SHLIBS corrupt
PHSS_33901.LANG-64ALIB corrupt
PHSS_33901.LANG-MIN corrupt
PHCO_29382.UUCP corrupt
PHSS_33901.CORE-64SLIB corrupt
PHSS_33901.CORE-SHLIBS corrupt
PHSS_33901.LANG-64ALIB corrupt
PHSS_33901.LANG-MIN corrupt
legionx
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2006 11:10 AM
07-03-2006 11:10 AM
Solution
Shalom Jairo,
I would suggest re-installation of these two patches instead of swremove. They probably are dependencies on these patches preventing proper removal.
SEP
I would suggest re-installation of these two patches instead of swremove. They probably are dependencies on these patches preventing proper removal.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2006 11:32 AM
07-03-2006 11:32 AM
Re: executing swremove
Hi Jairo,
Normally the fileset with the dependancy are not removed. you should now reinstall the dependancy patches.
regards,
Krishna
Normally the fileset with the dependancy are not removed. you should now reinstall the dependancy patches.
regards,
Krishna
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2006 06:04 PM
07-03-2006 06:04 PM
Re: executing swremove
Here are the steps you can follow to remove the same:
Step #1 :The solution is to remove the patch from the IPD (Installed Products Database). Before making modifications be sure a good backup of /var/adm/sw has been created in case any modifications need to be backed out.
Step #2 :Create a directory in /tmp called patch_mods. The directory can be in /home or anywhere else except for /var/adm/sw.
Step #3 :Change directories to /var/adm/sw/products.
Step #4 :For each patch found to be in the corrupt state , copy the directory with the name of the patch from /var/adm/sw/products to /tmp/patch_mods.
Step #5 :Run swmodify -a state=configured OS-Core.Q4 to force a build of the IPD. The new IPD will not list the transient patches.
Step #6 :Run swlist -l fileset -a state. The patches whose directories were moved prior to the IPD rebuild should not be listed.
Step #7 :Run swinstall to install the patches again. The reinstall option of swinstall does not need to be on.
Hope this helps.
-Amit
Step #1 :The solution is to remove the patch from the IPD (Installed Products Database). Before making modifications be sure a good backup of /var/adm/sw has been created in case any modifications need to be backed out.
Step #2 :Create a directory in /tmp called patch_mods. The directory can be in /home or anywhere else except for /var/adm/sw.
Step #3 :Change directories to /var/adm/sw/products.
Step #4 :For each patch found to be in the corrupt state , copy the directory with the name of the patch from /var/adm/sw/products to /tmp/patch_mods.
Step #5 :Run swmodify -a state=configured OS-Core.Q4 to force a build of the IPD. The new IPD will not list the transient patches.
Step #6 :Run swlist -l fileset -a state. The patches whose directories were moved prior to the IPD rebuild should not be listed.
Step #7 :Run swinstall to install the patches again. The reinstall option of swinstall does not need to be on.
Hope this helps.
-Amit
If you are not a part of solution , then you are a part of problem
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