Prepatch Steps Failing When Applying Exalogic 18.104.22.168.0 PSU To Exalogic 22.214.171.124.0 Compute Nodes
(Doc ID 1489305.1)
Last updated on JULY 24, 2018
Applies to:Oracle Exalogic Elastic Cloud Software - Version 126.96.36.199.5 to 188.8.131.52.5
When applying Exalogic 184.108.40.206.0 PSU Patch 13967248 on Exalogic Compute Nodes running 220.127.116.11.0 PSU, issue of below "Appendix" pre-patching step failing for older versions of Exalogic PSUs in this case 18.104.22.168.0 is seen.
"Appendix: Instructions for pre-patching compute node with old versions of Exalogic packages installed"
Below are symptoms of this problem.
When running Exalogic 22.214.171.124.0 we need to follow above "Appendix" pre-patch step in the patch documentation to apply components from the 126.96.36.199.2 sub-directory of Patch 13967248 to compute node.
Files are copied from the patch media to /opt/baseimage_pre_patch. The user is then asked to:
- cd /opt/baseimage_pre_patch/scripts
- unmount all nfs file systems (umount -avt nfs)
- invoke "./ebi_pre_patch.sh"
The first invocation of ./ebi_pre_patch.sh is therefore made while /opt/baseimage_pre_patch/scripts is the working directory. The first invocation prior to the automatic "reboot -n" works as expected. However after the automatic restart, there will be no scripts (CheckSWProfile, ChechHWnFWProfile) inside /opt/exalogic.tools/tools directory which are used to do post patch validation checks.
Following are messages from the ILOM console output after the second invocation of "ebi_pre_patch.sh" from rc.local.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!