After deploying a customization via Developer Studio's 'Generate Code and Deploy' followed by a Dictionary Cache refresh, unrelated custom API packages start throwing ORA-04061 ('existing state... has been invalidated') / ORA-06508 errors when called from active sessions or background jobs, even though the deployed code has nothing to do with the failing package.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Run Compile Invalid Objects (Solution Manager > System Information and Utilities > Oracle Objects) right after every deployment — a deployment can leave unrelated PL/SQL packages in an invalidated state in Oracle's dependency tracking, and any session or job that tries to call into one of those invalidated packages before it's recompiled hits exactly this kind of ORA-04061/ORA-06508 error. Explicitly recompiling invalid objects as a standard post-deployment step clears this up, rather than needing to identify which specific packages got invalidated.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions