Incorrect PL/SQL Code is Executed After Upgrading to 11G
(Doc ID 1061820.1)
Last updated on FEBRUARY 07, 2019
Applies to:PL/SQL - Version 184.108.40.206 to 220.127.116.11 [Release 11.1 to 11.2]
Information in this document applies to any platform.
***Checked for relevance on 23-Sep-2013***
A package, referenced by a synonym, is updated but dependency checking bypasses the synonym when in fast-validate mode. This causes the synonym to reference an incorrect entry point in the package and so the wrong line of code could be incorrectly executed resulting in wrong results or ORA-7445 errors.
There are a number of ways that we can see this happening. For example, if a package (accessed via a synonym) had either global variables or functions/procedures A, B, C in that order and B had been accessed/invoked in an active session, if the package is recreated to have A, D, B, C then accessing/invoking B again would access/invoke D instead.
The 10928 mcode event trace shows the PL/SQL lines of code which are executed. When this event is turned on, it is possible to see an incorrect entry point in the code. For example, to switch on the event run the following in a SQLPlus session:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document