Maximo 7.6.1 Configdb Runnig for 12+ Hours Due to Full Table Scan

We have an configb process that is taking more than 12 hours to run. I am uploading logs (configdb & restorefrombackup) and a AWR Report from the Oracle DBAs they ran for us. We also ran an Explain Plan which I have uploaded.
ExplainPlanA = update locations set etrphone = 0 where etrphone is null;
ExplainPlanB = update locations set etrphone = 0;

My colleague's analysis of the Explain Plans: "So... it would appear to me that removing the WHERE xxxxx IS NOT NULL reduces the cost from 26,415 (full table scan of LOCATIONS) to 1. I'd speculate that is a good saving and (with an IBM change) could save 11 hours during your dbConfig."

IBM WebSphere Application Server 8.5.5.15
Version
Tivoli's process automation engine 7.6.1.1-IFIX20200724-1613 Build 20190514-1348 DB Build V7611-365 HFDB Build HF7611-28
IBM Maximo Asset Management Work Centers 7.6.0.4 Build $build$ DB Build V7604-119
IBM Tpae Integration Framework 7.6.1.1-MIF_7611_IFIX.20200707-0957 Build 20190422-1259 DB Build V7611-01
IBM Maximo for Utilities 7.6.0.2-20200121-1511 Build 20171128-1353 DB Build V7602-68 HFDB Build HF7602-11
IBM Maximo Spatial Asset Management 7.6.0.5-20200728-1718 Build 20190522-1410 DB Build V7605-09 HFDB Build HF7605-07
IBM Maximo Asset Management 7.6.1.1 Build 20190514-1348 DB Build V7611-01
IBM Maximo for Transportation 7.6.2.5-20200303-1447 Build 20180730-2210 DB Build V7625-10 HFDB Build HF7625-16
IoT Connection Utility 7.6.0.2 Build 20190426-2206 DB Build V7602-07
Server OS Linux 3.10.0-1160.11.1.el7.x86_64
Server DB Oracle 12.1 (Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

A fix needs to be investigated in the configDB class, inside alterTable() method. When the table is being rebuilt there is a full table scan that happens during UPDATE. See Explain Plans provided by the customer