Clovertech

Data Integrator – Driver Not foound

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › Data Integrator – Driver Not foound

  • Creator
    Topic
  • September 15, 2014 at 4:08 pm #54384
    Bill Amadio
    Participant

      We just recently purchased Data integrator. When I try an connect to Oracle I get driver not found. I opened a ticket with Infor Extreme and they provided me with a New ODBC.INI but I still get the same error. Any ideas???

    • Creator
      Topic
    Viewing 6 reply threads
    • Author
      Replies
      • September 15, 2014 at 5:39 pm #81259
        Jim Kosloskey
        Participant

          Bill,

          Make sure the Driver= argument has a proper path.

          Some of the distributed odbc.ini files did not have the proper path so the driver specified was not located.

          Also make sure the LIBPATH Environment variable has the path for Data Direct (Connectx.x).

          email: jim.kosloskey@jim-kosloskey.com 30+ years Cloverleaf, 60 years IT – old fart.

        • September 15, 2014 at 6:39 pm #81260
          Russ Ross
          Participant

            If memory serves me right, when you install cloverleaf you don’t get the ODBC stuff installed until you select that additional install.

            In addition to obtaining a license for the ODBC data integrator add on, you will likely need to circle back and do another install and select the ODBC stuff.

            I think the cloverleaf install menu choice for the ODBC component install is something like “data integrator”.

            On cloverleaf 6.0 I check if my ODBC licenses are working as follows before I start spending time doing any integrations:

            Code:

            hcilictest cl-aom-odbc-mw
            hcilictest cl-aom-odbc-tcl

            Then if your ODBC licenses are okay, you can see if the ODBC drives have been installed by seeing if the Connect# directory exists, where # is the version number so in my case it is Connect7.0

            For example

            Code:

            cd $HCIROOT/lib
            ls -l ;# look for a directory connect something

            If on a different version of Cloverleaf, could try this to see if you get any hit as to if the ODBC data direct drivers have or haven’t been installed:

            Code:

            find $HCIROOT | grep odbc

            Here is what I get when I run the find so you can get a idea for comparison:

            Code:

            /cloverleaf/cis6.0/integrator/docs/dataintegrator/cmdref/deprecated_odbc_commands.htm
            /cloverleaf/cis6.0/integrator/docs/dataintegrator/cmdref/odbc_command_reference_overview.htm
            /cloverleaf/cis6.0/integrator/docs/dataintegrator/cmdref/odbc_commands.htm
            /cloverleaf/cis6.0/integrator/docs/dataintegrator/usingtclext/odbc_tcl_api_and_c_api_differences.htm
            /cloverleaf/cis6.0/integrator/docs/dataintegrator/usingtclext/odbc_tcl_extensions.htm
            /cloverleaf/cis6.0/integrator/external/Perl/src/libwin32-0.27/ODBC/docs/odbc.html
            /cloverleaf/cis6.0/integrator/install/.odbcdevlnklst
            /cloverleaf/cis6.0/integrator/install/.odbclnk
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/reference/css/odbccprtref.css
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/reference/css/odbcfunctions.css
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/reference/css/odbcgloss.css
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/reference/odbccprtref.html
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/reference/odbcfunctions.04.1.html
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/reference/odbcfunctions.04.2.html
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/reference/odbcfunctions.04.3.html
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/reference/odbcgloss.html
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/troubleshooting/css/odbccprtdiag.css
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/troubleshooting/odbccprtdiag.html
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/userguide/css/odbccprtuser.css
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/userguide/images/odbcbulkload.gif
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/userguide/images/odbcfailover.gif
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/userguide/images/odbcloadbal.gif
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/help/userguide/odbccprtuser.html
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/include/odbcinst.h
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/lib/libodbc.a
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/lib/libodbc.so
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/lib/libodbcinst.a
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/lib/odbc.so
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/lib/odbccurs.so
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/lib/odbcinst.so
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/locale/en_US/LC_MESSAGES/odbc.m
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/locale/en_US/LC_MESSAGES/odbc.po
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/odbc.csh
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/odbc.ini
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/odbc.sh
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/odbcInfo
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/odbcinst.ini
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/samples/demo/demoodbc
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/samples/demo/demoodbc.c
            /cloverleaf/cis6.0/integrator/lib/Connect7.0/samples/demo/demoodbc.txt
            /cloverleaf/cis6.0/integrator/lib/odbcInfo
            /cloverleaf/cis6.0/integrator/tcl/lib/odbc
            /cloverleaf/cis6.0/integrator/tcl/lib/odbc/pkgIndex.tcl

            Since you talked to Infor they may have already told you this about maybe needing to do an additional install,  if not then maybe they just assumed you had already installed it.

            Forgive me for stating the obvious but that is what popped into my head and is easy enough to check.

            Russ Ross
            RussRoss318@gmail.com

          • September 15, 2014 at 6:47 pm #81261
            Russ Ross
            Participant

              Here is the command I ran to see what my LIBPATH is set to that Jim Kosloskey spoke of:

              Code:

              echo $LIBPATH | tr : ’12’

              which gave me the following:

              Code:

              /cloverleaf/cis6.0/integrator/clgui/java/bin
              /cloverleaf/cis6.0/integrator/clgui/java/bin/classic
              /cloverleaf/cis6.0/integrator/clgui/java/lib/ppc
              /cloverleaf/cis6.0/integrator/lib
              /cloverleaf/cis6.0/integrator/bin
              /cloverleaf/cis6.0/integrator/tcl/lib
              /cloverleaf/cis6.0/integrator/dbms/lib
              /cloverleaf/cis6.0/integrator/lib/Connect7.0/lib
              /usr/lib
              /lib
              /shlib
              /usr/shlib

              which contains the path to the Connect7.0 Data Direct ODBC libraries once a proper install has been completed.

              Russ Ross
              RussRoss318@gmail.com

            • September 15, 2014 at 7:16 pm #81262
              Bill Amadio
              Participant

                My odbc.ini is in the /lib/Connect7.0 but I get nothing back wen I run the echo $LIBPATH | tr : ’12’ – Thanks!

              • September 15, 2014 at 9:26 pm #81263
                Russ Ross
                Participant

                  I was curious about what file controls the part of the LIBPATH of interest and in my case is

                  /cloverleaf/cis6.0/integrator/lib/Connect7.0/odbcInfo

                  Here is a post that also warns to cycle the hostserver to pick up new enviorment changes to things like LIBPATH:

                  <a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=2938&highlight=libpath&#8221; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=2938&highlight=libpath

                  since cycling the hostserver is relatively quick and easy give that a try to see if that helps with the GUI/IDE.

                  When you say you get nothing back from echo $LIBPATH, does that mean nothing at all or just for the Connect lib?

                  If you get nothing back at all then your setroot environment is worth trying to resolve.

                  <a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=2930&highlight=libpath&#8221; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=2930&highlight=libpath

                  Are you running more than one version of cloverleaf at the same time on your server or did you do an upgrade of cloverleaf in place instead of a scratch install?

                  At the command line prompt can you launch hcitcl and then type the following successfully

                  Code:

                  package require odbc

                  if successful it will return the version number of the odbc package.

                  Also while still in interactive session of hcitcl do this and see if Connect lib dir shows up

                  Code:

                  echo $env(LIBPATH)

                  Perhpas going thru some of these steps could provide insight into which direction to pursue to try and correct.

                  Here is another post to add to the thought process

                  <a href="https://usspvlclovertch2.infor.com/viewtopic.php?t=1592&postdays=0&postorder=asc&highlight=libpath&start=0&#8243; class=”bbcode_url”>https://usspvlclovertch2.infor.com/viewtopic.php?t=1592&postdays=0&postorder=asc&highlight=libpath&start=0

                  Another point to keep in mind is to login as hci on the backend and not yourself.

                  Another question that came to mind is your setup a HA environment and if so was the additional install of the cloverleaf ODBC add-on done on all nodes in the HA cluster?

                  You might be running on a node that the additional install was not done on but can still see the Connect lib dir on the share SAN disk.

                  Russ Ross
                  RussRoss318@gmail.com

                • September 18, 2014 at 3:02 pm #81264
                  Bill Amadio
                  Participant

                    cat odbcInfo

                    LD_LIBRARY_PATH=/qvdx/cis6.0/integrator/lib/Connect7.0/lib

                    ODBCINI=/qvdx/cis6.0/integrator/lib/Connect7.0/odbc.ini

                    (clover2vm)DIR= /Connect7.0 $ package require odbc

                    -bash: package: command not found

                  • September 18, 2014 at 9:06 pm #81265
                    Bill Amadio
                    Participant

                      hcitcl>package require odbc

                      11.0

                      hcitcl>echo $env(LIBPATH)

                      /qvdx/cis6.0/integrator/lib

                  • Author
                    Replies
                  Viewing 6 reply threads
                  • The forum ‘Cloverleaf’ is closed to new topics and replies.