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

Resolved Erratic behavior after migration from PB8 to PB19 - DBCS v SBCS?

  1. Issue
0
Votes
Undo
  1. Kelly Amott
    Kelly Amott
  2. PowerBuilder
  3. Wednesday, 19 May 2021 20:58 PM UTC

I have a 32-bit app currently in use by our Finance team that was last compiled in PB8 and is running in a 32 bit Oracle 8 environment. I ran it through the migration tool and created a 64-bit PB19 version that is on 64-bit Oracle 19c.

First rounds of testing appeared to go well. We have since discovered that the migration either fixed something that shouldn't have worked in the previous version or doesn't work now. We also found that certain lists don't sort correctly. I'm still debugging to get the details on both. It could be DB related or it may be the app.

The easy comparison is just a side by side PB8 vs PB19 code compare. The only thing I can see that is different is that with the migration all the functions were modified - len to LenA, pos to PosA, etc. 

It's 64-bit code on 64-bit Server 2019 talking to a 64-bit DB. It doesn't throw errors. 

The question is, is there any reason to suspect that what we're seeing is due to the function updates? That's the only difference I'm seeing right now.

PowerClient : Windows permission error when trying...
use PrintSetup, how to set page range
Responses (3)
Roland Smith
Roland Smith Accepted Answer Pending Moderation
  1. Thursday, 20 May 2021 17:31 PM UTC
  2. PowerBuilder
  3. # 1

Is the sort in the SQL or the DataWindow?

 

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 20 May 2021 17:04 PM UTC
  2. PowerBuilder
  3. # 2

Hi Kelly;

   If you are still using the  LenA and PosA commands then there is something wrong with your Oracle connection / environment. O19C should be using UTF-8 to communicate to any App (not just PB). In the case of Oracle though, the PB runtime converts the incoming O19C data into UTF-16LE format. This format internally matches the same MS-Window's 10 encoding standard so that W10 and any App are on the same data format when processing.

  On the way back to the the DBMS, PB's Oracle "interface" driver combined with the O19C DB Client sotware convert the UTF-16LE data stream back into UTF-8 format for the O19C DBMS to handle.

  Note that your migrated PB App should be using SQLCA.DBMS ="ORA" as its connection setting and you should have replaced your old O8 Oracle Client (aka OCI.dll) with the O19C version.

HTH

Regards ... Chris

Comment
There are no comments made yet.
Matthew Balent
Matthew Balent Accepted Answer Pending Moderation
  1. Wednesday, 19 May 2021 23:15 PM UTC
  2. PowerBuilder
  3. # 3

How was the db upgraded?  You jumped a whole lot of DB versions here.  Is the collation and such the same?

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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.