1. Stan Zihlman
  2. PowerBuilder
  3. Friday, 19 April 2019 18:46 PM UTC


Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 19 April 2019 18:52 PM UTC
  2. PowerBuilder
  3. # 1

Hi Stan;

  This situation normally occurs when during the PB IDE installation, the installer does not select the Oracle DB drivers for PB. In your case, the DLL named PBORA170.dll.

   This can also happen when you deploy your PB App's and then forget to also deploy the PBORA170.dll with your EXEs.

   For the IDE, just rerun the PB installation and select the missing DB client drivers.


Regards ... Chris

  1. Roland Smith
  2. Wednesday, 27 July 2022 17:03 PM UTC
PBORA170.DLL is for PB 2017 only, hence the 17 in the file name. PB 2019-R3 and newer do not have the version number in their name. A 64bit executable will require the 64bit runtime, including PBORA.DLL.
  1. Helpful
  1. Pete N
  2. Wednesday, 27 July 2022 17:34 PM UTC

Thank you for the info on the previous and current naming convention for PBORA DLLs.

I was able to solve this issue by running the installer for both 32-bit and 64-bit runtimes and removing them. Then re-installing 64-bit runtime.
  1. Helpful
  1. John Fauss
  2. Wednesday, 27 July 2022 18:03 PM UTC
If you are referring to the Oracle 32/64-bit (client) runtimes, please know that the PB IDE is 32-bit, hence it requires the 32-bit version of the Oracle client to be installed if you are going to connect to an Oracle database from within the PB development environment. The 64-bit Oracle client is used only when running a deployed PB application that was compiled/deployed for 64-bit.
  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.