RE: Fully qualified proc names
- From: "Kemnitz, LeRoy" <leroy.kemnitz@xxxxxxxxxxxxxxxxxx>
- To: Sayan Malakshinov <xt.and.r@xxxxxxxxx>
- Date: Wed, 24 Feb 2021 13:09:38 +0000
Turns out that I didn’t find any other objects with the same name.
From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> On Behalf
Of Kemnitz, LeRoy
Sent: Tuesday, February 23, 2021 2:55 PM
To: Sayan Malakshinov <xt.and.r@xxxxxxxxx>
Cc: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
Subject: RE: Fully qualified proc names
Good idea!
I am searching now in the database.
From: Sayan Malakshinov <xt.and.r@xxxxxxxxx<mailto:xt.and.r@xxxxxxxxx>>
Sent: Tuesday, February 23, 2021 2:49 PM
To: Kemnitz, LeRoy
<leroy.kemnitz@xxxxxxxxxxxxxxxxxx<mailto:leroy.kemnitz@xxxxxxxxxxxxxxxxxx>>
Cc: ORACLE-L <oracle-l@xxxxxxxxxxxxx<mailto:oracle-l@xxxxxxxxxxxxx>>
Subject: Re: Fully qualified proc names
*External Email: Use caution responding, opening attachments, or clicking on
links.*
Hi LeRoy,
User A owns both procs.
Have you checked that there is no package or procedure with the same name as
your schema name?
Best regards,
Sayan Malakshinov
Oracle performance tuning expert
Oracle Database Developer Choice Award winner
Oracle ACE Associate
http://orasql.org
вт, 23 февр. 2021 г., 23:36 Kemnitz, LeRoy
<leroy.kemnitz@xxxxxxxxxxxxxxxxxx<
mailto:leroy.kemnitz@xxxxxxxxxxxxxxxxxx>>:
Hello –
I have a weird situation going on and wondering if anyone else has experienced
this and what is the solution.
I am running Oracle 12.1.0.2 on Linux 6. I have an app that passes data to
Oracle and Oracle processes it and sends back a response – which happens to be
an array.
This app has been running fine for years. Minimal changes. Starting last
week, one of the main procedures has stopped working with this error:
"Package: F_CEUS_BLACK_BOX -- ErrorMessage: ORA-06550: line 1, column 12:
PLS-00302: component 'PKG_BLACK_BOX_CDR_STAT_CONTROL' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored"
The proc is calling another proc at the line in error. After doing lots of
testing, it appears that the calling of the other proc is successful if we
remove the schema from the fully qualified name of the proc. User A owns both
procs. User B has privs to execute the procs. User B attempts to execute the
procs but fails that it must be declared.
We have tried this on my Dev and my Test env. Those 2 env seem to be working
fine with the schema name included in the name…..just my production is having
this issue. I am at a loss about what is going on!
Has anyone else seen this?? If so, how did you fix it??
LeRoy
[UW System Logo]
[All In Wisconsin]
[
https://www.wisconsin.edu/uwsa/digital-communication/wp-content/uploads/sites/68/2019/04/twitter-sm.png]<
https://twitter.com/uwsystem>
[
https://www.wisconsin.edu/uwsa/digital-communication/wp-content/uploads/sites/68/2019/04/FB-sm.png]<
https://www.facebook.com/uwsystem>
Other related posts:
