How To Avoid Bouncing the Database after Changing a Workflow Package?
Last updated on SEPTEMBER 04, 2016
Applies to:Oracle Workflow - Version 18.104.22.168 to 12.2.5 [Release 11.5.10 to 12.2]
Information in this document applies to any platform.
Checked for relevance on 13-JUL-2013
A change is made to a Workflow related package and the package is compiled, the concurrent managers are bounced and the following error occurs in the workflow:
Error Message ORA-04061: existing state of has been invalidated ORA-04061:
existing state of package body "XXX.XX_XX_XXXXXXX' has been invalidated
Is there another way to correct this without bouncing the database?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms