Cleaning up a failed software installation
Using this scenario, you can clean up software products and service updates after an interrupted or failed installation.
Note: It is recommended that you first perform a system backup before installing software updates to ensure safe system recovery.
The cleanup procedure attempts to revert the update to its previous state. For example, when cleaning up an update that was interrupted in the COMMITTING state, the cleanup procedure attempts to return the update to its APPLIED state.
If an update installation is interrupted, run the lslpp -l command to see the current state of the update. For example, if you run lslpp -l on an interrupted update installation, it might report the update status as APPLYING rather than APPLIED.
If the interruption occurs during the initial state of an installation, then the cleanup procedure attempts to delete the installation entirely and restore the previous version of the product (if there is one). When the previous version is restored, it becomes the active version. When the previous version cannot be restored, the software is listed by the lslpp -l command as BROKEN.
When the product is deleted or BROKEN, you can attempt to reinstall the software. Any product in the BROKEN state cannot be cleaned up; it can only be reinstalled or removed.
If prompted to reboot (restart) the system after running the cleanup procedure, then do so now.
If you get a message indicating that no products were found that could be cleaned up, you may have executed the cleanup procedure when it was not needed. Try your installation again.
Using this scenario, you can clean up software products and service updates after an interrupted or failed installation.
Things to consider
The information in this how-to scenario was tested using specific versions of AIX. The results you obtain might vary significantly depending on your version and level of AIX.
The cleanup procedure attempts to delete items that were partially installed or left in an incomplete state. This scenario applies only to the update or installation of optional software products.
The information in this how-to scenario was tested using specific versions of AIX. The results you obtain might vary significantly depending on your version and level of AIX.
The cleanup procedure attempts to delete items that were partially installed or left in an incomplete state. This scenario applies only to the update or installation of optional software products.
Note: It is recommended that you first perform a system backup before installing software updates to ensure safe system recovery.
The cleanup procedure attempts to revert the update to its previous state. For example, when cleaning up an update that was interrupted in the COMMITTING state, the cleanup procedure attempts to return the update to its APPLIED state.
If an update installation is interrupted, run the lslpp -l command to see the current state of the update. For example, if you run lslpp -l on an interrupted update installation, it might report the update status as APPLYING rather than APPLIED.
If the interruption occurs during the initial state of an installation, then the cleanup procedure attempts to delete the installation entirely and restore the previous version of the product (if there is one). When the previous version is restored, it becomes the active version. When the previous version cannot be restored, the software is listed by the lslpp -l command as BROKEN.
When the product is deleted or BROKEN, you can attempt to reinstall the software. Any product in the BROKEN state cannot be cleaned up; it can only be reinstalled or removed.
To initiate a cleanup procedure using SMIT:
- Type smit maintain_software on the command line.
- Select Clean Up After Failed or Interrupted Installation and press Enter.
To initiate a cleanup procedure from the command line:
- Type installp -C on the command line and press Enter.
If prompted to reboot (restart) the system after running the cleanup procedure, then do so now.
If you get a message indicating that no products were found that could be cleaned up, you may have executed the cleanup procedure when it was not needed. Try your installation again.
Thanks for sharing with us. If someone wants to know about the Safety Software and Occupational health and Safety Software
ReplyDelete