Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Error when calling an Oracle SP from PowerServer Code

  1. How-to
0
Votes
Undo
  1. Bryant Burnard
    Bryant Burnard
  2. PowerServer 2020 or older (Obsolete)
  3. Wednesday, 12 December 2018 21:29 PM UTC

Hi;

Using Windows 10, PB 2017 R3 Build 1858 (trial for a Proof of Concept), Oracle 11G and the Oracle Instant Client 18.3 64 bit

For the PowerServer side, using a Native Interface Oracle 10g/11g/12c transaction.

 

I'm using oracle stored procedures to update data in the app I help support. We use the following call format in PowerServer, it works fine in PB, but in PowerServer when I execute:

declare sp_x procedure for sp_x ( :ls_1, :ls_2, :ls_3, :ii_num) USING SQLCA;

execute sp_x;

I am getting this error:

Failed to convert parameter value from a String to a Decimal.

The three strings are all under 100 chars in length.

I have also tried to run these using 'execute immediate', and receive the same error.

 

Thoughts on how to get this going?

Bryant

 

 

 

  1. 64-bit
  2. Oracle
  3. PowerBuilder (Appeon)
  4. Stored Procedure
How do I specify MS Edge as the Browser for my App...
Powerserver Setup Issue???
Responses (3)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 12 December 2018 21:39 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 1

Hi Bryant;

  Do you get the same issue when using a SP based DataWindow as well against the same SP instance?

Regards ... Chris

Comment
There are no comments made yet.
Bryant Burnard
Bryant Burnard Accepted Answer Pending Moderation
  1. Wednesday, 12 December 2018 21:55 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 2

Hi Chris, the SP we are using are straight updates within the Oracle DB. Can't really call them, but I'll see what I can hard wire quickly. The DWs using SPs are working normally.

Comment
There are no comments made yet.
Bryant Burnard
Bryant Burnard Accepted Answer Pending Moderation
  1. Wednesday, 12 December 2018 23:37 PM UTC
  2. PowerServer 2020 or older (Obsolete)
  3. # 3

Hi Chris,

Found the error. On the PB side I was passing in strings to the stored proc. The stored proc had been declared with four arguments;

sp_x (arg1 in varchar2,

arg2 in varchar2,

arg3 in long, (an older Oracle long character type!)

arg4 in number)

In trying to make the DW for the test I realized the error. For Appeon web you need to change the sp parameter type from the old Oracle long char type, which Appeon looked and said number, to varchar2 (or clob). This works without the error.

Thanks for your help

Bryant

 

Comment
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Thursday, 13 December 2018 03:09 AM UTC
That is excellent news Bryant!

Thanks for letting us know the resolution.
  1. Helpful
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.