Re: ORA-04068: existing state of packages has been discarded

Posted by ErmanArslansOracleBlog on Jan 02, 2019; 8:32am
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/ORA-04068-existing-state-of-packages-has-been-discarded-tp7030p7031.html

your db version is up-to-date..
ORA-04068 can be a result of compilation. It may be an expected behaviour in specific cases.
I mean, in most cases incidences of ORA-4068 and its associated errors are correct,

Read the following for further details ->

Troubleshooting PL/SQL Program Unit Invalidation Related Errors (e.g. ORA-4068, ORA-4065, ORA-6508, PLS-907) (Doc ID 2298084.1)

However; the weird thing is that  the utlrp.sql increased your invalid count to 15000...
Probably, utlrp.sql compiled an object that was referenced by several other objects.

1)Did you check the concurrent program that was generating ORA-04068? What was the PLSQL object that the concurrent program was trying to use?

2)What was the invalid count before running utlrp.sql?

3)Did you only grant some synonyms? or did you recreate any synonyms ?

4)What is the value of the hidded parameter named -> "_DISABLE_FAST_VALIDATE" ?

5)any errors in the alert log?

6)Are specific objects always involved or does the problem seem to randomly affect any package?

7)What, if any, DDL is executed just before the state goes bad? This may be found in audit data, via DDL triggers or by checking DBA_OBJECTS.LAST_DDL_TIME to identify whether DDL might have been executed that in some way relates to the affected packages.

8)How is the problem cleared, albeit temporarily, e.g. by flushing the shared pool, manually recompiling certain objects, recreating synonyms etc?

Note that, adadmin compiles invalid apps schema objects + their dependencies.. utlrp.sql on the other hand; compiles all the invalids in the database.