Hi just wanted to check if you are calling a 'wrapped' Oracle Package (Spec/Body) from PowerServer. I have found that if both the spec and body are wrapped you will get the error you are describing. IF you only wrap the body of the package, then PowerServer can figure out the call. (I"m using PowerServer 2022 Build 1892 and Oracle 19) 

HTH

Hi Chakrapani,

We simulated and reproduced the problem. But we don't quite know if it is the same in your case. We recommend that you submit a ticket at https://www.appeon.com/standardsupport/newbug and provide a reproducible test case so that we can better track and verify it.

Here is our PowerScript that simulates and reproduces the problem:

Declare usp_setclientinfo procedure for dbms_application_info.set_client_info(:ls_name||’@’||:ls_company) using sqlca;

The workaround is to replace “:ls_name||’@’||:ls_company” with a variable, for example:

string ls_parm

ls_parm = ls_name + ’@’+ ls_company

Declare usp_setclientinfo procedure for dbms_application_info.set_client_info(:ls_parm) using sqlca;

Regards,

David

Hi Louis,

We reproduced the issue. It is a bug. We suggest that you submit a ticket at https://www.appeon.com/standardsupport/newbug so our team can adequately track, prioritize and handle the case. 

At this moment, you can temporarily work around this issue using the following approach:

In your current connected database, create a new stored procedure to call msdb.dbo.sp_send_dbmail. Then in your PowerScript call this new stored procedure instead.

Regards,

David

I am having the exact same problem.  I am connecting a transaction as the SA on my MS SQL Server.  The IDE works perfect.  PS does not.  It is very frustrating have to change 1 thing, recompile, deploy, publish, etc. just to get this error over and over.  What can it really be and how best to debug it?

Make sure the username/password you configured has rights to this.

Hi

I'm not sure about DBMS_APPLICATION_INFO as this is a specific Oracle procedure, I wonder if the user you are connecting with has access to that procedure and it's dependancies? The error says it cannot parse the statement and the procedure may not exist.

Just a thought.

Regards

David

Hi;

  It looks like either your PowerServer generation was incomplete, the DB instance your pointing PS to is of a different schema or the DML your trying to perform is not supported by PS (check the PS unsupported features).

  If the above does not seem to apply to your case, then please open a Support Ticket.

Regards... Chris