• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Runtime error for a stored procedure call with input parameter of Table Type or Array, version 2019 R2 Build 2353

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

Resolved Runtime error for a stored procedure call with input parameter of Table Type or Array, version 2019 R2 Build 2353

  1. Issue
0
Votes
Undo
  1. Khaja Zaheeruddin
    Khaja Zaheeruddin
  2. PowerBuilder
  3. Tuesday, 28 June 2022 22:51 PM UTC

After upgrading Oracle Database to version 19c - we have an issue, a runtime failure when a stored procedure with an input parameter of a table type or an array is being called from the PBL.

Power Builder: Version 2019 R2 Build 2353

Oracle Database 19c Enterprise Edition Release 19.0.0.0.0

Note: The same code worked without any error on Oracle Database of version 12c

 

Attachments (3)
PB_Error_For_TableType_Parameter.jpg PB_Error_For_TableType_Parameter.jpg
PB_Error_SP_Signature.jpg PB_Error_SP_Signature.jpg
PB_Error_SP_Signature_Database.jpg PB_Error_SP_Signature_Database.jpg
  1. Array
  2. Oracle
  3. Parameter
  4. Stored Procedure
  5. Upgrade
  6. PowerBuilder Runtime
How to consume AWS SQS in PowerBuilder 2019?
Where to download the example source code
Responses (2)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 29 June 2022 00:20 AM UTC
  2. PowerBuilder
  3. # 1

Hi Khaja;

  Suggestion: Please try using PB2019 R3 with the latest Maintenance Release. There were some 19C fixes in between your release that might address this array issue.

Regards ... Chris

Comment
There are no comments made yet.
Khaja Zaheeruddin
Khaja Zaheeruddin Accepted Answer Pending Moderation
  1. Tuesday, 5 July 2022 15:45 PM UTC
  2. PowerBuilder
  3. # 2

Thanks for the response Chris.

I got the version "PB2019 R3 with the latest Maintenance Release" downloaded - but before the install would like to know the listed.

1. Can we rollback to a previous version - easily (if needed) ?

2. Do you think we should go-thru any release notes for the upgrade before proceeding with the upgrade ?

Thanks,

Zaheer.

Comment
Load more comments
Olan Knight
  1. Olan Knight
  2. Tuesday, 5 July 2022 15:49 PM UTC
I suggest saving ALL of your current code in a separate folder. This keeps backing out of the new MR simple.
  1. Helpful
Chris Pollach @Appeon
  1. Chris Pollach @Appeon
  2. Tuesday, 5 July 2022 17:54 PM UTC
FWIW: I would create a new VM (or use a new machine) and then install R3 on that one. Then perform a test migration & full unit test on your PB App using the R3 test machine. If all goes well, then follow Olan's suggestion & keep a backup of your PB App's R2 libraries before committing your actual PB Development PC's to R3. Note that once you install R3 over top of R2, you cannot return to R2.
  1. Helpful
Roland Smith
  1. Roland Smith
  2. Tuesday, 5 July 2022 19:12 PM UTC
The only way to revert from 2019-R3 to an earlier 2019 is to do a full uninstall and then reinstall the older build. You cannot have the two on the same machine at the same time unless you make a copy of 2019-R2 first. The R3 installer will remove folders & files from the ..\Appeon\PowerBuilder 19.0 folder.
  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.