Skip to Main Content
Forums

SQL & PL/SQL

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Error PLS-00231

32685May 19 2004 — edited Sep 10 2008

Hello

In the select statement of a cursor I need to perform some reasonably complex calculations on a variety of columns. I was hoping to use a set of functions defined in a package to perform the calculations, but I am getting the

PLS-00231 function 'string' may not be used in SQL

Error, is the only way round this to take the functions out of the package and have them as separate functions, or will it work if I simply put them in a separate package from the one that contains the cursor?

Cheers

David

Comments

Kamal Kishore
Try adding the PRAGMA to the function. 
FUNCTION function_name(...) RETURN VARCHAR2 ;
    PRAGMA RESTRICT_REFERENCES(function_name, WNDS, RNDS, WNPS,RNPS);
APC
There are a number of things it could be.

My #1 candidate is, we can only use functions in SQL statements that are public i.e. declared in a package spec. This is the case even for SQL statements executed within the same Package Body. The reson is that SQL statements are executed by a different engine which can only see publicly declared functions.

Cheers, APC
32685
Hi Andrew

That's exactly it! I moved the functions back to the original package, published them in the spec and it worked. Excellent!

Cheers

David
446518
Great!!

Helped me a lot

Though the message - function XX may not be used in SQL, is not relevent.

Krishna
564378
Wow, that cost me some time.
Thanks a lot, it saved my day.
450441
My god, users who search the forum before posting.

Surely it's a sign of the End of Days.
Amritpal
Thanks a lot, I just Googled the error PLS-00231, the very first link brought me here, and you were spot on. Declare the functions in the Package Spec to make them Global, and that solved the issue.

Thanks.
Amrit
659130
I also have this problem.

Making the function public helps ... but I can not make the function public. This violates the design.

The PRAGMA also says that it must be right behind the function definition AND in the package specification.


Is there a other - a private - way?

(Oracle 8i / PLSQL 8.1.7.4.0)



I also can not split the call from the SQL Statement, because it is part of a cursor loop: 
FOR a IN (SELECT asd,
                         asaa,
                         asdasda,
                         h.sssde,
                         HLP_FNC_GET_BLABLUBB(j.adasdassss) dasdasssss
                  FROM   T_fhexxxsadfast h,
                         t_FFasee112w_SA   j
                  WHERE  h.soasde = j.soasde) 
        LOOP
anonymized code.

Edited by: user5828099 on 10.09.2008 07:57

Edited by: user5828099 on 10.09.2008 08:02
1 - 8
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Oct 8 2008
Added on May 19 2004
8 comments
19,758 views