When… |
Actions... |
The result… |
---|---|---|
Normal behavior. |
The installer replaces current files with new. |
|
Installing an update and the patch history is missing (files are not found in the directory defined by the parameter PATCH_HISTORY_DIR in patch.conf) |
The installer creates new history files in the directory. The installer cannot determine compatibility but installs anyway because an update is a full distribution. |
|
Installing a fix and the patch history is missing (files are not found in the directory defined by the parameter PATCH_HISTORY_DIR in patch.conf) |
For a fix, the installer cannot determine compatibility. |
|
The installer is partway through the installation when there is a problem. The cluster contains some older files and some newer files. |
If the installer cannot complete, it reverses the update actions, removing the newer files and returning the older ones. |
|
Installing a fix and a file in the cluster is newer than the file in the patch (build number in cluster is larger than build number of patch). |
Prompt user to overwrite or preserve file. Install other files in the patch as usual. |
|
Installing a fix and a file in the cluster has been modified since the last patch (current file size does not match size that is recorded in patch history). |
Prompt user to overwrite or exit. |
|