• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Running PowerBuilder 2017R on Windows 2016 using Oracle 12.2.0.1 (64 bit) ODBC driver

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

Resolved Running PowerBuilder 2017R on Windows 2016 using Oracle 12.2.0.1 (64 bit) ODBC driver

  1. How-to
0
Votes
Undo
  1. Edouard Koucherian
    Edouard Koucherian
  2. PowerBuilder
  3. Tuesday, 11 June 2019 23:12 PM UTC

Hello,

 

We are trying to run PowerBuilder 2017R on Windows 2016 using  Oracle 12.2.0.1 (64 bit) ODBC driver to connect to Oracle DB. The error which we are getting is IM014. Is PB 2017R still considered as a 32 bit application?

How we can run PB 2017R to use 64 bit Oracle driver on 64 bit Windows 2016 server? Any help will be appreciated. 

 

Thanks in advance

Edward K.

Can we use Dll's created in VC98 in Appeon PowerBu...
OpenSheetInTabGroup - move tabs to top?
Responses (4)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 23 July 2019 13:46 PM UTC
  2. PowerBuilder
  3. # 1

Hi Chris;

  Nothing in the near term for 64bit App support directly via the IDE. Appeon would also need to update the RUN & Debugger features for that as well of course, the DB Profiles to make use of the 64 DB client.

Regards ... Chris

Comment
There are no comments made yet.
Chris Vansant
Chris Vansant Accepted Answer Pending Moderation
  1. Monday, 22 July 2019 22:11 PM UTC
  2. PowerBuilder
  3. # 2

Does anyone know if Appeon is planning to update the PB IDE to run on 64-bit.  I am also starting to run into resistance for using the 32-bit Oracle drivers (Windows 10 Enterprise 64-bit OS).  One day soon we will be mandated to deploy with 64-bit Oracle 12.2 or 18 client installs.  If there are plans, what is expected timeframe?  Is there a roadmap?

Comment
Chris Vansant
  1. Chris Vansant
  2. Monday, 22 July 2019 22:29 PM UTC
Forgot to add, I am currently using PB 2017R3. I just saw some other related tickets. Sounds like I must use 32-bit Oracle Client for connectivity thru PB IDE, but can deploy for 64-bit and the deployed app can use the 64-bit Oracle client...is that correct? Any other options I should be aware of? (I have just made switch to PB2017, so haven't seen the deployment options as of yet.)
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 12 June 2019 18:53 PM UTC
  2. PowerBuilder
  3. # 3

Hi Edouard;

  I am not sure by your posting but if I interpret your statement correctly you seem to be running the PB IDE on W2016. If that is the case, please note that the IDE is not certified for any MS-Windows "Server" releases. Only W7, 8, 8.1 & 10.

  Please disregard if you did not install PB IDE on W2016.

Note: PB App EXE's produced from the IDE are supported on Windows "server" editions.

Regards ... Chris

Comment
Edouard Koucherian
  1. Edouard Koucherian
  2. Thursday, 13 June 2019 16:20 PM UTC
Hi Chris,



Thanks for the respond, To clarify, we are running application on Citrix farm (not the PB IDE), which is going to get upgrade to Windows 2016. The issue is to manage PB connectivity to Oracle 12c using ODBC driver on W2016. Is there any article regarding PB 2017R and W2016, where there is no SysWOW64 directory for 32 bit applications.



Thanks

Edward K.

  1. Helpful
There are no comments made yet.
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Wednesday, 12 June 2019 13:54 PM UTC
  2. PowerBuilder
  3. # 4

Hi Edward

The PB IDE is a 32-Bit application and so you will need a 32-bit Oracle driver. You can compile your application as 64-Bit to use the 64-Bit drivers in deployment.

Personally I would avoid using the 64-Bit altogether unless there is a major compelling business case for doing so.

Hope that helps

Regards

David

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.