1. Douglas Lee
  2. PowerBuilder
  3. Thursday, 6 July 2017 18:16 PM UTC

I upgraded my Powerbuilder to 2017 and have a problem where when I try to query an oracle database, powerbuilder crashes.

I checked the database connections and everything seems correct. I can connect to the database and test the connection.

I then try to view the tables, run some sql, or run sql from a datawindow, PB17 crashes on me.

I've run as a normal user and as an administrator.    I'm running on a windows 10 machine.

Any help would be appreciated. Thanks.

David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Tuesday, 11 July 2017 14:52 PM UTC
  2. PowerBuilder
  3. # 1

We have successfully migrated a large PB application with Oracle to PB2017 and so far..... not had any issues.

If you can tell us what crash you are getting and a bit about your installation then I will happily help you. Great suggestions given so far too.

Regards

David

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 6 July 2017 18:51 PM UTC
  2. PowerBuilder
  3. # 2

Hi Douglas;

   Can you tell us ...

1) Oracle version & build?

2) What Oracle client are you using to connect (native, odbc, ADO.Net, etc)?

3) If "native" are you using the full Oracle client or the Instant client?

4) If using the PB 2017 Universal edition - did you install both the 32 &64 bit drivers?

5) Can you connect & run OK from iSQL*Plus (or equivalent) on the same PC?

6) Can you share with us your SQLCA connection values?

Many thanks!

Regards ... Chris

Comment
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Thursday, 6 July 2017 18:43 PM UTC
  2. PowerBuilder
  3. # 3

What version of Windows 10 are you running:  32 bit or 64 bit?

Remember that you must run the 32 bit Oracle Client in order to run with PB, even if you are on a 64 bit PC.

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.