1. chakrapani salumuri
  2. PowerServer
  3. Thursday, 24 November 2022 11:47 AM UTC

Hi

Please find the attached image and advice 

 

Attachments (1)
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 24 November 2022 13:18 PM UTC
  2. PowerServer
  3. # 1

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 

Comment
There are no comments made yet.
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Thursday, 24 November 2022 14:26 PM UTC
  2. PowerServer
  3. # 2

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

Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Thursday, 24 November 2022 15:34 PM UTC
  2. PowerServer
  3. # 3

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

Comment
There are no comments made yet.
Louis Arena Accepted Answer Pending Moderation
  1. Wednesday, 4 January 2023 22:29 PM UTC
  2. PowerServer
  3. # 4

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?

Attachments (1)
Comment
  1. Chris Pollach @Appeon
  2. Thursday, 5 January 2023 18:47 PM UTC
Hi Louis;

Looks like you are trying to execute a Stored Procedure through some type of mechanism (in-line or DWO based DML) and that is what is failing.

I would like to suggest that if you cannot figure this out, that you create a Support Ticket so that our Appeon Support team can help you resolve this issue.

FYI: https://www.appeon.com/standardsupport

Regards ... Chris
  1. Helpful
There are no comments made yet.
David Xiong @Appeon Accepted Answer Pending Moderation
  1. Friday, 6 January 2023 06:58 AM UTC
  2. PowerServer
  3. # 5

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

Comment
There are no comments made yet.
David Xiong @Appeon Accepted Answer Pending Moderation
  1. Friday, 6 January 2023 07:01 AM UTC
  2. PowerServer
  3. # 6

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

Comment
  1. Olan Knight
  2. Sunday, 26 February 2023 16:56 PM UTC
It is also MUCH cleaner to assigned update values to a string (or whatever appropriate data type) prior to using the string in a command/function/stored procedure/whatever. This also allows you to review the string in DEBUG mode if necessary.
  1. Helpful
There are no comments made yet.
Bryant Burnard Accepted Answer Pending Moderation
  1. Friday, 24 February 2023 22:51 PM UTC
  2. PowerServer
  3. # 7

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

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.