1. tim schmidt
  2. PowerBuilder
  3. Friday, 6 March 2020 15:45 PM UTC

Testing a connection to Oracle 19C.

Our login window is successful connecting to the database.

When we run our next select statement that just counts records in a table we get an error saying we are not connected.

Not sure why the connection is being dropped.

Appreciate your ideas.

 

Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Monday, 9 March 2020 18:49 PM UTC
  2. PowerBuilder
  3. # 1

Hi Tim;

  Oracle 18C & 19C are only just "officially" supported in the latest Maintenance Release for PB 2017 R3 (build 1915) and PB 2019 build 2170.

Regards ... Chris

Comment
  1. Michael Kramer
  2. Monday, 9 March 2020 20:36 PM UTC
Yes, and only supported via DBMS = ORA.

DBMS = O90 is for Oracle 9 and DBMS = O10 is for Oracle 10.
  1. Helpful
There are no comments made yet.
tim schmidt Accepted Answer Pending Moderation
  1. Monday, 9 March 2020 18:38 PM UTC
  2. PowerBuilder
  3. # 2

We now have this working using DBMS=O90 and 19C

Not sure why but so far users are ok.

Comment
  1. Armeen Mazda @Appeon
  2. Monday, 9 March 2020 18:44 PM UTC
Thanks for sharing your solution!
  1. Helpful
  1. Chris Pollach @Appeon
  2. Monday, 9 March 2020 18:46 PM UTC
Stop using ASAP - that is only for Oracle v 9.0!

You should be using DBMS="ORA"
  1. Helpful
  1. tim schmidt
  2. Tuesday, 10 March 2020 18:56 PM UTC
We know but it is working for the client now until we get ORA working.
  1. Helpful
There are no comments made yet.
tim schmidt Accepted Answer Pending Moderation
  1. Monday, 9 March 2020 18:20 PM UTC
  2. PowerBuilder
  3. # 3

Hi Chris,

When we login in we get connected ok to the database or at least no errors show up.

Right after we login I put in this and get the results below:

// login worked
messagebox("connected - sql code",  string(sqlca.sqlcode) + sqlca.sqlerrtext)
messagebox("connected - sql DB code",  string(sqlca.sqldbcode) + sqlca.sqlerrtext)

select count(*)
 into :ll_cnt
 from ediview.ediview_license;
 
messagebox("get license records - sql code", string(sqlca.sqlcode) + sqlca.sqlerrtext)

 

Comment
There are no comments made yet.
tim schmidt Accepted Answer Pending Moderation
  1. Friday, 6 March 2020 21:18 PM UTC
  2. PowerBuilder
  3. # 4

Our current situation is we do have PB17 R3.

Our client wanted to test Oracle 19C which we haven't even installed yet.

We sent them a version of PB17 R3 to test if they can connect to Oracle 19C. They do have the latest dll that came with R3.

Not the ideal situation but they were very curious if they could get it running so we obliged.

We will be installing 19C and testing next week.

 

 

 

Comment
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 6 March 2020 18:41 PM UTC
  2. PowerBuilder
  3. # 5

Hi Tim;

  Can you tell us ...

1) Are you using the native Oracle connection mechanism from the PB IDE and/or your PB App EXE?

2) Have you tried executing the SQL in the IDE's DB Painter via the iSQL pane?

Regards ... Chris

Comment
There are no comments made yet.
tim schmidt Accepted Answer Pending Moderation
  1. Friday, 6 March 2020 17:58 PM UTC
  2. PowerBuilder
  3. # 6

Yes we have.

Comment
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 6 March 2020 16:37 PM UTC
  2. PowerBuilder
  3. # 7

Have you applied the latest MR # 1915, which adds support for Oracle 19c to PowerBuilder 2017 R3?

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.