This procedure describes how to clean up after an interrupted installation of optional software products. The cleanup procedure attempts to delete software products that were partially installed or that have been left in an "ing" state(that is, applying, committing, rejecting, or removing). For example, if your attempt to install a service update was not successful, the update may be in the "applying" rather than the "applied" state. The "ing" states indicate that the action you were attempting did not complete successfully. The output of the lslpp command with the -l option indicates the state of the software products on the system.
The cleanup procedure attempts to revert the product to its previous state. For example, if you are cleaning up an update that is in the committing state, the cleanup procedure attempts to return the update to the applied state. If you have a product in the committing state or an update in the applying state, then the cleanup procedure attempts to delete the failed installation and restore the previous version of the product (if there is one). In this case, the previous version of the product becomes the active version. If the previous version of the product cannot be restored, then the software product enters the BROKEN state. If the cleanup procedure has deleted the product or if the product is in the BROKEN state, you can attempt to reinstall the software. Any product that was already in the BROKEN state cannot be cleaned up; it can only be reinstalled or removed.
The system automatically performs a cleanup when an installation cannot be completed because of a failure or interruption. Normally, the only condition under which you may have to use the cleanup procedure described in this section is if the system shuts down or loses power during an installation or if the installation process terminates abnormally. Occasionally, you will be prompted to reboot (restart) the system after running the cleanup procedure.
For more information on the cleanup process and the output from the installp command (which includes the different software states), refer to "Optional Software Installation and Update Concepts".
Note: This procedure applies only to the installation of optional software products. If your AIX Version 4.3 Base Operating System installation was unsuccessful, go to "Accessing a System That Will Not Boot".
The next section contains a procedure for cleaning up software, using either the Web-based System Manager application or the System Management Interface Tool (SMIT). The installp -C command can also be used to clean up software.
If the installation you are performing with the Web-based System Manager application fails, perform the following steps.
After performing the cleanup operation, restart the installation process.
Another troubleshooting option allows you to verify the software installed on the system. Perform the following steps to verify the software:
This procedure describes how to clean up your system after an unsuccessful installation of software other than the Base Operating System. Perform this procedure if the system instructed you to perform a cleanup when you attempted to install optional software.
If the system successfully reverts to the previous version, it becomes the currently active version. If this cannot be done, then the software product is marked as BROKEN.