Why does my attempt to activate the upgrade fail due to a missing file, when the file is actually present?

Due to issues from previous releases there may be files present that have the names in improper cases. This should only present an issue for Linux/UNIX installations and will depend on the specifics of the options chosen when your cluster was being initially installed. If you encounter this issue you can resolve it by renaming the file to the appropriate name reported by the automated activation step and trying the operation again.

For example, if your cluster currently has the file /eservice/esc/conf/services/SD.xml in the cluster configuration, the activation step may complain that the file /eservice/esc/conf/services/sd.xml is missing (for your Linux/UNIX installation). Simply rename the file appropriately and continue.