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.
HTH
Regards ... Chris
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.