800xA Update 18.104.22.168 to 22.214.171.124
There was an error when installing Update media system update from 126.96.36.199 to 188.8.131.52
The snapshots of error attached. Kindly let me know for any files for your reference.
(We had to format the system due to plant start-up emergency.)
Voted best answer
The 0x8abb00c9 is an error code I've never encountered myself before, however a search makes me believe it may relate to RNRP and the system installer waiting for system status that never arrives. See the context below taken from another support case:
2019-06-03 16:14:55:688#4, level = 1, SERVER1, AfwSMClient, AfwSMClient, Error, Tag: n/a, PID: 2272, TID: 4128
CNodeStatusReporter::UpdateStatus - Calling GetAll on m_pNodeStatus failed, hr = 0x8abb00c9
2019-06-03 16:15:49:621#5, level = 1, SERVER1, AfwSystemStatusService, AfwSystemStatusService, Error, Tag: n/a, PID: 1324, TID: 1312
NetworkStatus::CRnrpEventClient::EvaluateAndUpdateMyConnectionState - Own node has no valid area!
Login to the node, check that RNRP status tools work and deliver information about the RNRP network. If not, find out why.
This error may be intermittent, so a reboot to kick off a new attempt to complete the upgrade may work. Sometimes setting the "ABB RNRP" and/or "ABB ServiceManager Service" to Automatic (Delayed Start) in Control Panel>Administrative Tools>Services has helped. However, I recommend that you file a support case with your regional support team in case you end up using this solution (as it may have side effects).
The patching of Oracle in an IM has (in my own eyes) always been a risky moment. Sometimes the upgrade scripts become hung up due to some 3rd party software interacting with Oracle in an unforeseen way (the old manual upgrade instruction had a text explaining the need to shutdown any custom client application software preventing it from interfere with the upgrade). In pre-SV6 the manual patching could be partly made (or at least completed) in by starting Windows in Safe Mode (when 3rd party applications typically cannot run/interfere).
Despite trying to run this Oracle patch command manually (but without the -silent argument) to be able to see what happens, after having taken proper backups, shut everything down including a Configuration Wizard > Maintenance Stop, I sincerely recommend asking for assistance from your regional ABB support team.
Be extremely careful about using Exclude Node during an update. In practise, excluded noded need to be rebuilt from scratch.