Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8016677
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 4, 20262026-06-04T20:36:26+00:00 2026-06-04T20:36:26+00:00

This problem came up when trying out the Unit Testing capabilities of SQLDeveloper. When

  • 0

This problem came up when trying out the Unit Testing capabilities of SQLDeveloper.

When running a test for a procedure that is created within my schema I am seeing an error however when the same procedure is run in one of the oracle supplied schemas it works without an issue.

SQL Developer generates the following calls:

1) This one doesn’t work (error is shown below):

BEGIN
 "IANC"."SIMPLE_PARAMETER"(P_X => 123);
END;

2) This one does:

BEGIN
 "HR"."SIMPLE_PARAMETER"(P_X => 123);
END;

This is the procedure:

CREATE OR REPLACE PROCEDURE SIMPLE_PARAMETER 
(
  P_X IN NUMBER  
)
IS
BEGIN

  null;

END SIMPLE_PARAMETER;

The following is the output from SQLPLUS, where you can see when the procedure is run in my schema I see an error whilst when running the same procedure in another schema the procedure works as expected:

enter image description here

In case of need my I am using Oracle Enterprise Edition 11.2.0.1.0

Update

Screen shot showing procedure signatures

enter image description here

I should also mention that if I remove the schema name from the procedure call then the procedure runs and completes as expected.

Thanks in advance for any help received.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-04T20:36:27+00:00Added an answer on June 4, 2026 at 8:36 pm

    Are you sure that the SIMPLE_PARAMETER procedure in IANC is the same (or at least has the same signature) as the one in HR? What do you get from `DESCRIBE “IANC”.”SIMPLE_PARAMETER”.

    (P.S. since your identifiers are all upper-case, you shouldn’t need the double quotes at all.)

    Added: Another possibility is that you have a package called IANC in the IANC schema, so Oracle is looking for a procedure in that package called SIMPLE_PARAMETER that does not exist. Example:

    SQL> exec bigdecimaltest
    
    PL/SQL procedure successfully completed.
    
    SQL> exec dcosta.bigdecimaltest
    
    PL/SQL procedure successfully completed.
    
    SQL> create or replace package dcosta as
      2  end;
      3  /
    
    Package created.
    
    SQL> exec dcosta.bigdecimaltest
    BEGIN dcosta.bigdecimaltest; END;
    
                 *
    ERROR at line 1:
    ORA-06550: line 1, column 14:
    PLS-00302: component 'BIGDECIMALTEST' must be declared
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    

    This seems like buggy behavior — if the attempt to resolve the name as package.member doesn’t succeed, I think Oracle ought to then try it as schema.object, but it looks like once it has found a match on the package name it won’t reconsider that.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

While trying to figure out terminology for rendering, I came down to this problem
I came across this problem when trying to decode json into an array ,
This is a question that came from an earlier problem I had . Basically,
I'm trying to brush up my algorithmic skills and came across this problem. Here
I was trying this problem on spoj. First of all I came up with
i came across this problem, my code in the viewWillAppear method is not executed
While doing some small regex task I came upon this problem. I have a
Guys, I've came across this problem I can't resolve myselg, I'm pretty sure I
I was configuring syntax highlighting for my blog when I came across this problem.
Problem This question actually came up at work today. We are planning an experiment

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.