adop actualize_all.. Compiling invalids !!!

Hi Experts,

I am planning to run actualize_all in production system. When I am running it in non-Prod environment, I can see it is compiling invalids (using dbms_scheduler) and it is causing many concurrency wait events like 'row cache lock', library cache lock/pin etc.. We have a sensitive system in this regard.

So my question is, theoretically its an online activity/phase but is it practical to run this in a very very high transactional EBS environment ? Oracle doesn't recommend compiling object in an very active database then how is this phase doing the same ? Is it compiling objects in old edition, which I doubt because I could see the last_ddl of objects changing run edition of DB.