Skip to main content
  • Subscribe by RSS
  • Ex Libris Knowledge Center

    Installation and Configuration of ODBC for Voyager


    Prepackaged Reports (PPR, Reports.mdb) allow sites to make a read-only connection to Voyager's database on the server via Microsoft Access on a workstation using an ODBC connection. PPR allow institutions to query the database for information that may not be available via batch jobs or other reporting functions in Voyager.


    • Voyager Prepackaged Reports using MS Access require the installation of Oracle 10g Client 32-bit to function correctly.

    • Oracle 10g Client installer is available via FTP from using the 'odbc' user


    Download this client and not any other Oracle ODBC client package. Support can troubleshoot the Ex Libris ODBC installation package only.

    • 32-bit MS Access 2003 or greater (No 64-bit). To determine your Access version:
      • Open MS Access > File > Account > click About Access
      • Box will pop up; note version at top of box.
    • Administrator privileges on PC
    • tnsnames.ora template (See attached)


    Follow all of the steps below. Do not deviate from the instructions.  Install only the installation package specified in the previous section.

    1. Completely remove any Oracle 10g Client which was installed previously. Any subsequent versions of Oracle Client (e.g. Oracle 11g) should also be uninstalled if possible, to aid in preventing any complications.
    2. From Ex Libris ODBC installation package, run setup.exe
      1. Click "Next."
      2. Select "Administrator" as the installation type, and click "Next"
      3. At Available Product Components, click "Next"
      4. At Product-Specific Prerequisite Checks", click the check box next to any errors and select "Yes" in any "Warning" dialogs.
      5. At "Summary select "Install", installation will run for a few minutes.
      6. At "Oracle Net Configuration Assistant" select "Perform Typical Configuration" and click "Next". And click Next on the following screen.
      7. Once the installation has completed Click "Finish" -> "Exit" -> "Yes"
    3. Open the attached tnsnames.ora template in a plain-text text editor (e.g. Notepad)
    4. In tnsnames.ora replace with the IP or host name of the Voyager server.
    5. Copy the configured tnsnames.ora file to C:\oracle\product\10.2.0\client\network\ADMIN\
    6. Check permissions on tnsnames.ora to ensure "Full Control" is granted to "Authenticated Users"
    7. Locate and run the file odbcad32.exe as administrator(Right Click -> 'Run as Administrator'):
      1. 64-bit Windows: C:\Windows\SysWOW64\odbcad32.exe
      2. 32-bit Windows: C:\Windows\System32\obdcad32.exe
    8. Select the "System DSN" tab and select "Add."
    9. Select the driver "Microsoft ODBC for Oracle."
    10. Enter the following values:

    Data Source Name: VGER

    Description: Tables

    Username: ro_xxxdb (Replace 'xxxdb' with the db name of the voyager instance)

    Server: VGER



    1. Click 'OK' to close odbcad32.exe
    2. Open Reports.mdb from C:\Voyager\Access Reports\
    3. Select "External Data" from the MS-Access Ribbon and click "ODBC Database"
    4. Select "Link to the data source by creating a linked table."
    5. Select the "Machine Data Source".

    1. Select "VGER" and click "OK."
    2. Enter the following values and click "OK":

    User Name: ro_xxxdb (Replace 'xxxdb' with the db name of the voyager instance"

    Password: ro_xxxdb

    Server: VGER


    1. Click "Deselect All", and click "OK."

    1. Locate the navigation pane on the left hand side of the screen in MS-Access. At the top of the navigation pane select the drop down menu, and change the selection to "Forms".

    1. Open "Build Database Links to Voyager" form.
    2. Enter the following values and select "Connect"(Replace 'xxxdb' with the db name of the Voyager instance):

    ODBC Name: VGER

    Connect String: VGER

    DB User ID: ro_xxxdb

    Password: ro_xxxdb

    Tablespace: XXXDB  (typically you will want to use all caps for the Tablespace name)

    If this is unsuccessful, capitalize the Tablespace name and re-try this step.

    1. If successful results will appear as below. Otherwise, if failures occur, double-check the configuration and permission of tnsnames.ora, and the configuration of the DSN. For further assistance open a support case with Voyager support.

    • Article last edited: 07-Nov-2018