Description

jgebal

opened on Jan 31, 2018

Issue body actions

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)

Activity

1. jgebal

   added

   enhancement

   on Jan 31, 2018
2. jgebal

   changed the title [-]get rid of valls to dbms_utility.name_resolve if possible[/-] [+]get rid of calls to dbms_utility.name_resolve if possible[/+] on Jan 31, 2018
3. Shoelace commented on Feb 14, 2018

   

   Shoelace

   on Feb 14, 2018

   Member

   More actions

   i added the calls to name_resolve ear;y on. it is supposed to be the way oracle itself resolves the name so maybe its just not catching the exception correctly.
   ut_metadata.do_resolve doesnt catch any exceptions so that is probably all thats needed..

   i dont think you can get rid of it otherwise the 'authid current_user' stuff doesnt work for running as not the ut owner.
4. jgebal

   added a commit that references this issue on Jun 15, 2019

   Removed dependency on `dbms_utility.name_resolve`.

   This issue will close once commit 85942e9 is merged into the 'develop' branch.

   85942e9
5. jgebal

   closed this as completedin #939on Jun 16, 2019
6. lwasylow

   added a commit that references this issue on Jun 18, 2019

   Release/v3.1.7 (#942)

   This issue will close once commit 1a5c525 is merged into the 'develop' branch.

   1a5c525

Issue actions