THE INFORMATION IN THIS ARTICLE APPLIES TO:
DISCUSSION
You may have issues with the 64-bit ODAC drivers not connecting to the EFTDB when attempting to analyze the database for its upgrade. This happens because they do not have
the option to install the ODAC components to GAC and register them in machine config (www.oracle.com section Machine-Wide Configuration).
The steps below must be run manually for ODAC 64-bit components to be usable in the EFT installation while performing the database upgrade:
Once ODAC software (18.x/19.x) is installed, go to the install directory and navigate to odp.net\bin\4.
In this folder, open a command window as administrator and run the following commands:
OraProvCfg.exe /action:gac /providerpath:"Oracle.DataAccess.dll"
OraProvCfg /action:config /force /product:odp /component:dbproviderfactory /frameworkversion:v4.0.30319 /providerpath:Oracle.DataAccess.dll
Look in c:\Windows\Microsoft.NET\Framework64\ to see the correct versions for .net. There should be a v4.0.xxxx folder. Use this string as frameworkversion, as shown in above example. This will register the oracle ado.net provider in machine configuration and allow the EFT installer to use it.
To verify that the registration and configuration is done
correctly, you can open a PowerShell window and run the following command:
[System.Data.Common.DbProviderFactories]::GetFactoryClasses()
You should see a few entries like this below:
ODP.NET, Unmanaged Driver Oracle Data Provider for .NET, Unmanaged Driver Oracle.DataAccess.Client