Q
Problem solve Get help with specific problems with your technologies, process and projects.

Receiving ORA-06550 error

I've read an answer for the error ORA-06550. I'm getting the same error but in my case, I don't think it could be a permission problem. I created another user, with the same properties that I've been having the problems with, then I imported all the data. Therefore I have a clone user. With the second, I can run all without any problem, but with the first I always get the error.

Hi Brian. I've read an answer for the error ORA-06550. I'm getting the same error but in my case, I don't think it could be a permission problem.

When I try to run any procedure from a determinated user I get this error:

ORA-06550: line 2, column 10:
PLS-00302: component 'PROVA_DEBUGGING' must be declared
ORA-06550: line 2, column 3:
PL/SQL:Statement ignored
I get this error when I execute the procedure with TOAD and SQL*Plus. The procedure is really simple (I've created it only for testing):
CREATE OR REPLACE PROCEDURE PROVA_DEBUGGING IS

BEGIN

DBMS_OUTPUT.Put_Line('TRYING TO DEBUG');
        
END PROVA_DEBUGGING;
/
I get this error with all the procedures and functions I've tried for this user.

At the beginning I thought it could be a user problem. But I created another user, with the same properties that I've been having the problems with, then I imported all the data. Therefore I have a clone user. With the second, I can run all without any problem, but with the first I always get the error.

Do you have any idea how to help? Thanks in advance.

You have created the procedure and own the procedure, therefore you can run the procedure. But this procedure is calling a supplied package, DBMS_OUTPUT. Have you verified that the user that owns the procedure you created has privileges to execute the DBMS_OUTPUT supplied package? Typically, users have been granted execute privs on DBMS_OUTPUT through the use of a database role. However, procedures require that the privilege be granted explicitly through the user and not through a role. Sign on as SYS and granted EXECUTE on DBMS_OUTPUT to the user that owns the procedure you created. Then sign on as the proc owner and execute the proc again. It should run just fine.

Dig Deeper on Oracle database design and architecture

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.

-ADS BY GOOGLE

SearchDataManagement

SearchBusinessAnalytics

SearchSAP

SearchSQLServer

TheServerSide.com

SearchDataCenter

SearchContentManagement

SearchHRSoftware

Close