Here are some helpful steps to troubleshoot connection issues with Oracle DB. First it's best to validate the current product version of Oracle.DataAccess.dll being used. (Screenshot below).
For irAuthor, you will need to change the irAuthor configuration file (C:\Program Files (x86)\InRule\irAuthor\ irAuthor.exe.config) to include this version. This change will also be required within your application's configuration file:
<assemblyIdentity name="Oracle.DataAccess" publicKeyToken="89b483f429c47342" culture="neutral" />
<bindingRedirect oldVersion="184.108.40.206-220.127.116.11" newVersion="18.104.22.168" />
It is also important to note that InRule is built with the "Any CPU" option and the "Prefer 32-bit option" disabled. Therefore, if your application is 64-bit, it will require the 64-bit Oracle client, if your application is 32-bit, it will require the 32-bit Oracle client, and if your application is also built with the "Any CPU" option, then the Oracle client would need to match the bitness of the OS.
When InRule is looking for the Oracle client, it will first look for it in the GAC. If it doesn't find it there, then it will look for it in the bin directory (or bin\EndPointAssemblies) of the calling application. Once it has located the assembly, it will attempt to load it using System.Reflection.Assembly.Load(String), where the parameter is the fully qualified assembly name.