| unrelated procedure goes invalid [message #648161] |
Wed, 17 February 2016 15:58  |
 |
uman2631
Messages: 16
Registered: November 2011
|
Junior Member |
|
|
I have two procedures, call them Procedure A and Procedure B. They do very different things, and the only object they share is that they both select from the same table, and they both use UTL_FILE.
If I make a minor code change to Procedure A, Procedure B goes invalid. I cannot figure out why. Nor does Oracle try to recompile the invalid procedure "on the fly," as I thought it would, it just fails to execute Procedure B. Recompiling Procedure B (with no code changes of course), always fixes the problem. But I can't figure out why Procedure B is going invalid at all. The usual suspects don't seem to pan out: the only dependent object is this one table, the associated public synonym and UTL_FILE, none of which is modified in any way. No changes to any grants. Procedure B code is not modified at all. A select from DBA_DEPENDENCIES on Procedure B shows only the synonym (which is not changing) and UTL_FILE (which is not changing). A select from DBA_DEPENDENCIES on Procedure A shows the synonym, UTL_FILE, and 2 other synonyms/tables that it uses that Procedure B does not (and are not changing). I'm confuddled.
Any ideas?
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
