During Step 2, "Patching factory image", of Mammoth Upgrade post_upgrade103 Fails with "Transaction check error"
(Doc ID 2816039.1)
Last updated on MARCH 08, 2023
Applies to:Big Data Appliance Integrated Software - Version 4.12.0 and later
During Step 2, "Patching factory image", of mammoth upgrade, upgrade post_upgrade103 fails with "Transaction check error".
Running "mammoth -p" may fail with an error like:
"mammoth -p" may succeed but one or more nodes may not be slated for reboot.
Checking the post_upgrade103 output file, /opt/oracle/BDAMammoth/bdaconfig/tmp/post_upgrade_script_<EPOCH_TIMESTAMP>.out, on the host where mammoth fails or on the host which is not slated for reboot , indicates that a "Transaction check error" is responsible for the failure.
An example error looks like below.
package libibumad-4:188.8.131.52-1.0.3.el7uek4.x86_64 is already installed
package libibumad-devel-4:184.108.40.206-1.0.3.el7uek4.x86_64 is already installed
package libibmad-4:1.3.12-1.0.4.el7uek4.x86_64 is already inst alled
package opensm-libs-4:3.3.19-1.0.5.el7uek4.x86_64 is already installed
Baseimage yum upgrade failed
Note: The list of packages can differ.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document