This is the case why we choose manual upgrade path where you have more control over the process. I suggest using manual approach and do oem upgrade later after db upgrade. Then you could enable tracing of emca and have enough time to investigate why it failing.
How To Manually Upgrade DBConsole Configuration After Database Upgrade [ID 1293264.1]
How to Trace / Debug the EMCA Tool in 10g and 11g [ID 330689.1]
Thanks for the time to answer my initial inquiry. We have to use the dbua as it has been the approved and, thus far, adhered approach for all prior upgrades. Prior to this last set of upgrades, we had no significant delay in the OEM upgrade step of the dbua. In reality, the OEM upgrade portion is NOT failing, but completing correctly. We are just try to see if there are a few actions we could do up front to reduce the OEM upgrade time. Thanks again.
You would agree that in order to propose the action required to decrease time of OEM upgrade, we need to identify and understand why its taking so long, especially as you said, its not something you have seen in other environments.
So, have you got more detail where this time is spent? The upgrade process is updating SYSMAN schema, does it stuck on something running in the schema, blocking by some process?