A while back, I wrote this post about the dreaded “existing state of the packages” error when recompiling code that is used in a Workflow process.
There is some degree of official guidance on what you need to do now, contained in Metalink note 754993.1 – “How can you Avoid Bouncing the Database after Changing a WF Package”. The advice is, to be honest, perhaps a little Draconian and unwieldy, but the guidance from Oracle is that all you need to do is:
- Shut down the concurrent managers
- Flush the shard pool
- Update the package
- Restart the concurrent managers
Now, that certainly will do it (so would bouncing the database, though!) – the likelihood of a developer shutting down the managers, then flushing the pool, and THEN compiling their code is probably quite low, though