Re: Timeout parameters

Posted by ErmanArslansOracleBlog on Nov 17, 2016; 8:19pm
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/Timeout-parameters-tp1540p1569.html

Hi Linda,

I don't think it is a good idea to skip the recompilation that is needed just after the db upgrade phase. It is a mandatory thing.
Also, EBS upgrade can be considered as a user level work. So, basically db session will be used by EBS 's patch wizard to create new packages, alter tables and so on.
Having a stable environment is necessary for a proper EBS upgrade.
You will probably fail in EBS upgrade if you skip the whole recompilation thing that is needed just after the db upgrade... (it is very risky, that's for sure)

However, alternatively, you can analyze the utlrp run and find the objects which it spents most of its time.. Note those objects, and if those objects are not mandatory(very critical ones) , just skip them.. (ofcourse test this carefully)

Also, I suggest you to try to increase the recompilation speed. Ensure it is running in parallel, ensure the resources are there for utlrp to consume, ensure there is no in-db wait --abnormal waits during utlrp run and check out this note : Utlrp.Sql Is Taking Too Long To Complete. (Doc ID 564605.1), this note is for 11g but will give you some ideas.


Lastly, you know Oracle has an automatic recompilation capability. You can give it a try.. However, you can never know all the database actions that EBS upgrade do (it may do an incompatible move, incompatible to auto recompile thing...)
Also remember the following:
--------------------------------
An INVALID Object problem may arise due to:

    Due to any patch installation.
    Database/Application level up-gradation
    DDL Changes

These changes may not cause compilation failures as the objects will be re-validated by on-demand automatic recompilation, but this can take an unacceptable time to complete, especially where complex dependencies are present.

For this reason it makes sense to recompile invalid objects in advance of user calls.  It also allows you to identify if any changes have broken the database code.