Recreating An Existing Package Generates Timestamps Out Of Sync Which Causes ORA-6508
Last updated on JULY 05, 2017
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 to 126.96.36.199 [Release 11.1]
Information in this document applies to any platform.
***Checked for relevance on 21st Nov 2016***
If an existing package heavily referenced in the database is recreated, the dependancy mechanism that ensures that packages are recompiled may fail leaving timestamps out of synchronisation.
This generally results in errors such as:
ORA-04068: existing state of packages has been discarded
ORA-04065: not executed, altered or dropped stored procedure "<USER>.<PACKAGE>"
ORA-06508: PL/SQL: could not find program unit being called: "<USER>.<PACKAGE>"
when executing the package.
And these errors do not always automatically clear as they should when package state is reset in subsequent calls.
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