KB1037

Installing Oracle Data Access Component

Summary

Oracle Data Access Component (ODAC) version 12.1 is required in order to import data from an Oracle database to Axiom Capital Tracking.

  • For cloud service systems, ODAC needs to be installed on the Axiom Cloud Integration Server.

  • For on-premise systems, ODAC needs to be installed on the Axiom Application Server.

Details

When using Oracle as the import source on the Source tab of an Axiom Capital Tracking import, ODAC version 12.1 must be installed on the Axiom Cloud Integration Server or Axiom Application Server (for on-premise systems).

The following error occurs if ODAC is not installed: "The 'OraOLEDB.Oracle' provider is not registered on the local machine."

Example error when ODAC is not installed on Axiom Cloud Integration Server

Resolution

Oracle Data Access Component (ODAC) version 12.1 can be installed by your Information Technology department's server administrator. They will also need to work with the Oracle database administrator to determine the connection string and login information to the Oracle database.

To install ODAC:

  1. Download ODAC121012_x64.zip to the Axiom Cloud Integration Server or the Axiom Application Server (on-premise deployments).

  2. Unzip the installation media.

  3. Right-click setup.exe and select Run as administrator.

  4. On the Welcome screen of the Oracle Universal Installer, click Next.

  5. On the Select a Product to Install screen, click Next. The required product is selected by default.

  6. On the Install Location screen, set the Oracle Base install location file path to C:\app\oracle (instead of using the default operating system user name).

  7. On the Available Product Components screen, click Next to accept the default components.

  8. On the Database Connection Configuration screen, you can optionally enter the connection alias now, or you can click Next to define it later (by editing the TNSNAMES.ORA file after the installation).

  9. On the Oracle Providers for ASP.NET screen, click Next. It is not required to run the SQL scripts.

  10. On the Summary screen, click Install.

  11. On the End of Installation screen, click Exit. It is not required to run the SQL scripts.

  12. If you did not define the connection alias as part of the installation (step 8), define it now by editing the TNSNAMES.ORA file. Your Oracle database administrator provides the connection string and the Oracle account used to authenticate to the database.
  13. Restart the server to register the Oracle Providers.

Verifying the Oracle database connection using Microsoft Data Link

Once ODAC is installed and the connection string is defined in the TNSNAMES.ORA file, confirm that the Axiom Cloud Integration Server or Application Server (on-premise systems) connects successfully to the Oracle database by using a Microsoft Data Link file.

To create a Microsoft Data Link file:

  1. Right-click on an empty space on the desktop, then select New > Text Document.

  2. Rename the text file and its extension to TestUDL.udl.

  3. When prompted, click Yes to confirm that you want to change the file name extension.

  4. Once the file and extension are renamed, the file icon on the desktop changes to reflect the new file type. Double-click the icon to open the file.

  5. In the Data Link Properties dialog, on the Provider tab, select Oracle Provider for OLE DB from the list, and then click Next.

  6. On the Connection tab, enter the appropriate TNS name and Oracle login information, and then click Test Connection.

  7. Launch the Axiom Desktop Client, and verify that an Axiom Capital Tracking import successfully connects to Oracle using the connection information from the previous step.

    NOTE: Axiom Cloud systems require a remote data connection to route the Oracle connection through the Axiom Cloud Integration Server. On-premise deployments do not use remote data connections, and will route the connection to Oracle using the Axiom Application Server automatically.

Outcome

Once Oracle Data Access Component (ODAC) version 12.1 is installed and the connection to the Oracle database is confirmed, Axiom Capital Tracking can successfully run imports that use Oracle as an external database source.

See also

Article information

Category

Imports

Applies To

All versions

Tags

Oracle, ODAC, TNSNAMES

Issue Number(s)

N/A