get rid of calls to dbms_utility.name_resolve if possible
-
Notifications
You must be signed in to change notification settings - Fork 187
Labels
Description
opened
Calls to dbms_utility.name_resolve are causing issues in the environments where schema_name and an object within the schema share the same name.
This was raised as an issue in utPLSQL itself:
https://stackoverflow.com/questions/45350935/utplsql-installation-ora-04047-error-when-exec-ut-run/48541758#48541758
And here is a bit of background to that issue from one of IBM forums:
https://www.ibm.com/developerworks/community/forums/html/topic?id=d8087c9d-39c2-4cf3-8e29-8611f48a4d6e
Need to review the need to call dbms_utility.name_resolve functionality as well as ways to efficiently replace it (if it's really needed)
Metadata
Metadata
Assignees
No one assigned
Labels
Type
No type
Fields
No fields configured for issues without a type.
Projects
No projects
Milestone
No milestone
Relationships
None yet
Development
No branches or pull requests