You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Agneeswaran <ag...@nielsen.com> on 2016/06/07 12:35:25 UTC
Error in ODBC connection
Hi Team,
We are getting the following error message while Connecting to ODBC
server.Could you please suggest us.
Error
[unixODBC][Driver Manager]Data source name not found, and no default driver
specified
We have followed all the procedure as mentioned in the site:
https://apacheignite.readme.io/docs/odbc-driver
Binary used :apache-ignite-fabric-1.6.0-bin
Thanks,
Agneeswaran
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-in-ODBC-connection-tp5493.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Error in ODBC connection
Posted by Igor Sapego <is...@gridgain.com>.
Agneeswaran,
What are your code trying to do? Can you share a configuration? Code sample
could help
too.
Also, check if there are zombie or background processes of your binary and
kill them.
Best Regards,
Igor
On Wed, Jun 8, 2016 at 4:49 PM, Agneeswaran <
agneeswaran.ponnuraman.ap@nielsen.com> wrote:
> Hi Igor,
>
> Sorry, it is misprint.
>
> We have done a rebuild the whole binary on the same node. Seems the ODBC
> connection gets established but we are getting message keep on till we do
> ctrl+x.
>
> We have waited more than 5 minutes. Is this issue with the Cache
> configuration?.Please help us.
>
> [09:41:16,196][INFO][grid-timeout-worker-#161%null%][IgniteKernal]
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
>
> *Connection String.*
> std::string connectStr = "DRIVER={Apache
> Ignite};SERVER=dayrhegapd023.enterprisenet.org
> ;PORT=21050;CACHE=MARKET_POD_ACV_CACHE;";
>
> *Please find the following log file
> :/opt/ignite/work/log/ignite-6fa93c38.0.log*
>
> >>>
> +----------------------------------------------------------------------+
> >>> Ignite ver.
> 1.6.0#20160518-sha1:0b22c45bb9b97692208fd0705ddf8045ff34a031
> >>>
> +----------------------------------------------------------------------+
> >>> OS name: Linux 2.6.32-573.22.1.el6.x86_64 amd64
> >>> CPU(s): 40
> >>> Heap: 0.44GB
> >>> VM name: 33476@dayrhegapd022.enterprisenet.org
> >>> Local node [ID=6FA93C38-AF46-4B7E-9C83-BE6D2F11AE24, order=1,
> >>> clientMode=false]
> >>> Local node addresses:
> >>> [dayrhegapd022.enterprisenet.org/0:0:0:0:0:0:0:1%1,
> >>> 192.168.202.26/10.7.202.26, /127.0.0.1, /192.168.202.26]
> >>> Local ports: TCP:10800 TCP:11211 TCP:47100 UDP:47400 TCP:47500
> TCP:48100
>
> [09:39:16,183][INFO][main][GridDiscoveryManager] Topology snapshot [ver=1,
> servers=1, clients=0, CPUs=40, heap=0.44GB]
> [09:39:16,207][INFO][exchange-worker-#184%null%][GridCacheProcessor]
> Started
> cache [name=MARKET_POD_ACV_CACHE, mode=PARTITIONED]
>
> [09:39:16,302][INFO][exchange-worker-#184%null%][GridCachePartitionExchangeManager]
> Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
> [topVer=1, minorTopVer=1], evt=DISCOVERY_CUSTOM_EVT,
> node=6fa93c38-af46-4b7e-9c83-be6d2f11ae24]
> [09:39:16,313][INFO][exchange-worker-#184%null%][GridCacheProcessor]
> Started
> cache [name=PROD_HIER_CACHE, mode=PARTITIONED]
>
> [09:39:16,364][INFO][exchange-worker-#184%null%][GridCachePartitionExchangeManager]
> Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
> [topVer=1, minorTopVer=2], evt=DISCOVERY_CUSTOM_EVT,
> node=6fa93c38-af46-4b7e-9c83-be6d2f11ae24]
> [09:39:25,627][INFO][ignite-update-notifier-timer][GridUpdateNotifier] Your
> version is up to date.
> [09:40:16,191][INFO][grid-timeout-worker-#161%null%][IgniteKernal]
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=6fa93c38, name=null, uptime=00:01:00:009]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=40]
> ^-- CPU [cur=0.13%, avg=0.05%, GC=0%]
> ^-- Heap [used=91MB, free=79.88%, comm=310MB]
> ^-- Non heap [used=28MB, free=77.98%, comm=29MB]
> ^-- Public thread pool [active=0, idle=80, qSize=0]
> ^-- System thread pool [active=0, idle=80, qSize=0]
> ^-- Outbound messages queue [size=0]
> [09:41:16,196][INFO][grid-timeout-worker-#161%null%][IgniteKernal]
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=6fa93c38, name=null, uptime=00:02:00:011]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=40]
> ^-- CPU [cur=0.03%, avg=0.04%, GC=0%]
> ^-- Heap [used=94MB, free=79.15%, comm=310MB]
> ^-- Non heap [used=28MB, free=77.92%, comm=29MB]
> ^-- Public thread pool [active=0, idle=80, qSize=0]
> ^-- System thread pool [active=0, idle=80, qSize=0]
> ^-- Outbound messages queue [size=0]
> [09:42:16,198][INFO][grid-timeout-worker-#161%null%][IgniteKernal]
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
> ^-- Node [id=6fa93c38, name=null, uptime=00:03:00:013]
> ^-- H/N/C [hosts=1, nodes=1, CPUs=40]
> ^-- CPU [cur=0.03%, avg=0.04%, GC=0%]
> ^-- Heap [used=98MB, free=78.26%, comm=310MB]
> ^-- Non heap [used=28MB, free=77.91%, comm=29MB]
> ^-- Public thread pool [active=0, idle=80, qSize=0]
> ^-- System thread pool [active=0, idle=80, qSize=0]
> ^-- Outbound messages queue [size=0]
> [09:43:16,200][INFO][grid-timeout-worker-#161%null%][IgniteKernal]
> Metrics for local node (to disable set 'metricsLogFrequency' to 0)
>
>
>
> Thanks,
> Agneeswaran
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Error-in-ODBC-connection-tp5493p5531.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Error in ODBC connection
Posted by Agneeswaran <ag...@nielsen.com>.
Hi Igor,
Sorry, it is misprint.
We have done a rebuild the whole binary on the same node. Seems the ODBC
connection gets established but we are getting message keep on till we do
ctrl+x.
We have waited more than 5 minutes. Is this issue with the Cache
configuration?.Please help us.
[09:41:16,196][INFO][grid-timeout-worker-#161%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
*Connection String.*
std::string connectStr = "DRIVER={Apache
Ignite};SERVER=dayrhegapd023.enterprisenet.org;PORT=21050;CACHE=MARKET_POD_ACV_CACHE;";
*Please find the following log file
:/opt/ignite/work/log/ignite-6fa93c38.0.log*
>>> +----------------------------------------------------------------------+
>>> Ignite ver. 1.6.0#20160518-sha1:0b22c45bb9b97692208fd0705ddf8045ff34a031
>>> +----------------------------------------------------------------------+
>>> OS name: Linux 2.6.32-573.22.1.el6.x86_64 amd64
>>> CPU(s): 40
>>> Heap: 0.44GB
>>> VM name: 33476@dayrhegapd022.enterprisenet.org
>>> Local node [ID=6FA93C38-AF46-4B7E-9C83-BE6D2F11AE24, order=1,
>>> clientMode=false]
>>> Local node addresses:
>>> [dayrhegapd022.enterprisenet.org/0:0:0:0:0:0:0:1%1,
>>> 192.168.202.26/10.7.202.26, /127.0.0.1, /192.168.202.26]
>>> Local ports: TCP:10800 TCP:11211 TCP:47100 UDP:47400 TCP:47500 TCP:48100
[09:39:16,183][INFO][main][GridDiscoveryManager] Topology snapshot [ver=1,
servers=1, clients=0, CPUs=40, heap=0.44GB]
[09:39:16,207][INFO][exchange-worker-#184%null%][GridCacheProcessor] Started
cache [name=MARKET_POD_ACV_CACHE, mode=PARTITIONED]
[09:39:16,302][INFO][exchange-worker-#184%null%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=1, minorTopVer=1], evt=DISCOVERY_CUSTOM_EVT,
node=6fa93c38-af46-4b7e-9c83-be6d2f11ae24]
[09:39:16,313][INFO][exchange-worker-#184%null%][GridCacheProcessor] Started
cache [name=PROD_HIER_CACHE, mode=PARTITIONED]
[09:39:16,364][INFO][exchange-worker-#184%null%][GridCachePartitionExchangeManager]
Skipping rebalancing (nothing scheduled) [top=AffinityTopologyVersion
[topVer=1, minorTopVer=2], evt=DISCOVERY_CUSTOM_EVT,
node=6fa93c38-af46-4b7e-9c83-be6d2f11ae24]
[09:39:25,627][INFO][ignite-update-notifier-timer][GridUpdateNotifier] Your
version is up to date.
[09:40:16,191][INFO][grid-timeout-worker-#161%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=6fa93c38, name=null, uptime=00:01:00:009]
^-- H/N/C [hosts=1, nodes=1, CPUs=40]
^-- CPU [cur=0.13%, avg=0.05%, GC=0%]
^-- Heap [used=91MB, free=79.88%, comm=310MB]
^-- Non heap [used=28MB, free=77.98%, comm=29MB]
^-- Public thread pool [active=0, idle=80, qSize=0]
^-- System thread pool [active=0, idle=80, qSize=0]
^-- Outbound messages queue [size=0]
[09:41:16,196][INFO][grid-timeout-worker-#161%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=6fa93c38, name=null, uptime=00:02:00:011]
^-- H/N/C [hosts=1, nodes=1, CPUs=40]
^-- CPU [cur=0.03%, avg=0.04%, GC=0%]
^-- Heap [used=94MB, free=79.15%, comm=310MB]
^-- Non heap [used=28MB, free=77.92%, comm=29MB]
^-- Public thread pool [active=0, idle=80, qSize=0]
^-- System thread pool [active=0, idle=80, qSize=0]
^-- Outbound messages queue [size=0]
[09:42:16,198][INFO][grid-timeout-worker-#161%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
^-- Node [id=6fa93c38, name=null, uptime=00:03:00:013]
^-- H/N/C [hosts=1, nodes=1, CPUs=40]
^-- CPU [cur=0.03%, avg=0.04%, GC=0%]
^-- Heap [used=98MB, free=78.26%, comm=310MB]
^-- Non heap [used=28MB, free=77.91%, comm=29MB]
^-- Public thread pool [active=0, idle=80, qSize=0]
^-- System thread pool [active=0, idle=80, qSize=0]
^-- Outbound messages queue [size=0]
[09:43:16,200][INFO][grid-timeout-worker-#161%null%][IgniteKernal]
Metrics for local node (to disable set 'metricsLogFrequency' to 0)
Thanks,
Agneeswaran
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-in-ODBC-connection-tp5493p5531.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Error in ODBC connection
Posted by Igor Sapego <is...@gridgain.com>.
Agneewaran,
Do you really have two '=' after 'DRIVER' keyword in your connection string
or is it
misprint?
Best Regards,
Igor
On Wed, Jun 8, 2016 at 3:38 PM, Agneeswaran <
agneeswaran.ponnuraman.ap@nielsen.com> wrote:
> Hi Igor,
>
> Please find the connection string.
>
> std::string connectStr = "DRIVER=={Apache
> Ignite};SERVER=dayrhegapd023.enterprisenet.org
> ;PORT=21050;CACHE=MARKET_POD_ACV_CACHE;";
>
> We will try with the ODBC examples.
>
> Thanks,
> Agneewaran
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Error-in-ODBC-connection-tp5493p5529.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Error in ODBC connection
Posted by Agneeswaran <ag...@nielsen.com>.
Hi Igor,
Please find the connection string.
std::string connectStr = "DRIVER=={Apache
Ignite};SERVER=dayrhegapd023.enterprisenet.org;PORT=21050;CACHE=MARKET_POD_ACV_CACHE;";
We will try with the ODBC examples.
Thanks,
Agneewaran
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-in-ODBC-connection-tp5493p5529.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Error in ODBC connection
Posted by Igor Sapego <is...@gridgain.com>.
Also, is it possible for you to build and run our ODBC example, located at
platforms\cpp\examples\odbc-example? You can find instructions on how
to build it in README.txt and DEVNOTES.txt files.
Best Regards,
Igor
On Wed, Jun 8, 2016 at 2:59 PM, Igor Sapego <is...@gridgain.com> wrote:
> Agneeswaran,
>
> Can you provide your new connect string please?
>
> Best Regards,
> Igor
>
> On Wed, Jun 8, 2016 at 2:07 PM, Agneeswaran <
> agneeswaran.ponnuraman.ap@nielsen.com> wrote:
>
>> Hi Igor,
>>
>> Still we are facing the same issue, please find the following output,
>>
>> [ignite@dayrhegapd022 cpp]$ odbcinst -i -d -f
>> $IGNITE_HOME/platforms/cpp/odbc/install/ignite-odbc-install.ini
>> odbcinst: Driver installed. Usage count increased to 5.
>> Target directory is /etc
>> [ignite@dayrhegapd022 cpp]$
>>
>> Please find the following content in the file odbcinst.ini,
>>
>> File name : /etc/odbcinst.ini
>>
>> [Apache Ignite]
>> Description = Apache Ignite
>> Driver = /usr/local/lib/libignite-odbc.so
>> DriverODBCVer = 03.00
>> FileUsage = 0
>> UsageCount = 5
>>
>> Please suggest us.
>>
>> Thanks in advance.
>>
>> Wirh regards,
>> Agneeswaran
>>
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-ignite-users.70518.x6.nabble.com/Error-in-ODBC-connection-tp5493p5522.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>
Re: Error in ODBC connection
Posted by Igor Sapego <is...@gridgain.com>.
Agneeswaran,
Can you provide your new connect string please?
Best Regards,
Igor
On Wed, Jun 8, 2016 at 2:07 PM, Agneeswaran <
agneeswaran.ponnuraman.ap@nielsen.com> wrote:
> Hi Igor,
>
> Still we are facing the same issue, please find the following output,
>
> [ignite@dayrhegapd022 cpp]$ odbcinst -i -d -f
> $IGNITE_HOME/platforms/cpp/odbc/install/ignite-odbc-install.ini
> odbcinst: Driver installed. Usage count increased to 5.
> Target directory is /etc
> [ignite@dayrhegapd022 cpp]$
>
> Please find the following content in the file odbcinst.ini,
>
> File name : /etc/odbcinst.ini
>
> [Apache Ignite]
> Description = Apache Ignite
> Driver = /usr/local/lib/libignite-odbc.so
> DriverODBCVer = 03.00
> FileUsage = 0
> UsageCount = 5
>
> Please suggest us.
>
> Thanks in advance.
>
> Wirh regards,
> Agneeswaran
>
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Error-in-ODBC-connection-tp5493p5522.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Error in ODBC connection
Posted by Agneeswaran <ag...@nielsen.com>.
Hi Igor,
Still we are facing the same issue, please find the following output,
[ignite@dayrhegapd022 cpp]$ odbcinst -i -d -f
$IGNITE_HOME/platforms/cpp/odbc/install/ignite-odbc-install.ini
odbcinst: Driver installed. Usage count increased to 5.
Target directory is /etc
[ignite@dayrhegapd022 cpp]$
Please find the following content in the file odbcinst.ini,
File name : /etc/odbcinst.ini
[Apache Ignite]
Description = Apache Ignite
Driver = /usr/local/lib/libignite-odbc.so
DriverODBCVer = 03.00
FileUsage = 0
UsageCount = 5
Please suggest us.
Thanks in advance.
Wirh regards,
Agneeswaran
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-in-ODBC-connection-tp5493p5522.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Error in ODBC connection
Posted by Igor Sapego <is...@gridgain.com>.
Hi Agneeswaran,
You should install Apache Ignite ODBC driver using provided
ignite-odbc-install.ini
file as described at [1]. After that you are going to be able to connect to
the driver
using "{Apache Ignite}" as a value for the "DRIVER" attribute. Or simply
speaking,
you should modify your connection string like the following as described at
[2]:
std::string connectStr = "DRIVER={Apache Ignite};SERVER=
dayrhegapd022.enterprisenet.org;"
"PORT=21050;CACHE=MARKET_POD_ACV_CACHE;";
Please, let me know if this helps.
[1] - https://apacheignite.readme.io/docs/odbc-driver
[2] - https://apacheignite.readme.io/docs/connecting-string
Best Regards,
Igor
On Wed, Jun 8, 2016 at 9:00 AM, Agneeswaran <
agneeswaran.ponnuraman.ap@nielsen.com> wrote:
> Hi Igor,
>
> The connection string is,
> std::string connectStr =
> "DRIVER=/usr/local/lib/libignite-odbc.so;SERVER=
> dayrhegapd022.enterprisenet.org;PORT=21050;CACHE=MARKET_POD_ACV_CACHE;";
>
> This error occurs even in the empty string as std::string connectStr =" ";
>
> Please find the output for <ldd /usr/local/lib/libignite-odbc.so>
>
> [ignite@dayrhegapd022 Linux]$ ldd /usr/local/lib/libignite-odbc.so
> linux-vdso.so.1 => (0x00007fffc01c7000)
> /usr/lib64/libodbcinst.so (0x00007f32dd3df000)
> libignite-binary-1.6.0.8653.so.0 =>
> /usr/local/lib/libignite-binary-1.6.0.8653.so.0 (0x00007f32dd1b4000)
> libignite-common-1.6.0.8653.so.0 =>
> /usr/local/lib/libignite-common-1.6.0.8653.so.0 (0x00007f32dcfac000)
> libdl.so.2 => /lib64/libdl.so.2 (0x00007f32dcd9c000)
> libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f32dca95000)
> libm.so.6 => /lib64/libm.so.6 (0x00007f32dc811000)
> libc.so.6 => /lib64/libc.so.6 (0x00007f32dc47d000)
> libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f32dc266000)
> libltdl.so.7 => /usr/lib64/libltdl.so.7 (0x00007f32dc05d000)
> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f32dbe40000)
> /lib64/ld-linux-x86-64.so.2 (0x00000031b0600000)
> [ignite@dayrhegapd022 Linux]$
>
> Please let us know, whether we have missed anything.
>
> Thanks,
> Agneeswaran
>
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Error-in-ODBC-connection-tp5493p5512.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
Re: Error in ODBC connection
Posted by Agneeswaran <ag...@nielsen.com>.
Hi Igor,
The connection string is,
std::string connectStr =
"DRIVER=/usr/local/lib/libignite-odbc.so;SERVER=dayrhegapd022.enterprisenet.org;PORT=21050;CACHE=MARKET_POD_ACV_CACHE;";
This error occurs even in the empty string as std::string connectStr =" ";
Please find the output for <ldd /usr/local/lib/libignite-odbc.so>
[ignite@dayrhegapd022 Linux]$ ldd /usr/local/lib/libignite-odbc.so
linux-vdso.so.1 => (0x00007fffc01c7000)
/usr/lib64/libodbcinst.so (0x00007f32dd3df000)
libignite-binary-1.6.0.8653.so.0 =>
/usr/local/lib/libignite-binary-1.6.0.8653.so.0 (0x00007f32dd1b4000)
libignite-common-1.6.0.8653.so.0 =>
/usr/local/lib/libignite-common-1.6.0.8653.so.0 (0x00007f32dcfac000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f32dcd9c000)
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f32dca95000)
libm.so.6 => /lib64/libm.so.6 (0x00007f32dc811000)
libc.so.6 => /lib64/libc.so.6 (0x00007f32dc47d000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f32dc266000)
libltdl.so.7 => /usr/lib64/libltdl.so.7 (0x00007f32dc05d000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f32dbe40000)
/lib64/ld-linux-x86-64.so.2 (0x00000031b0600000)
[ignite@dayrhegapd022 Linux]$
Please let us know, whether we have missed anything.
Thanks,
Agneeswaran
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Error-in-ODBC-connection-tp5493p5512.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Error in ODBC connection
Posted by Igor Sapego <is...@gridgain.com>.
Hi Agneeswaran,
Could you please provide your connection string? Or are you using one of
the examples?
According to the error, ODBC driver was not properly installed in your
system. It is also possible,
that unixODBC can not find all the dependencies of the driver library. Can
you provide output of the
ldd command (ldd /usr/local/lib/libignite-odbc.so)?
Best Regards,
Igor
On Tue, Jun 7, 2016 at 3:35 PM, Agneeswaran <
agneeswaran.ponnuraman.ap@nielsen.com> wrote:
> Hi Team,
>
> We are getting the following error message while Connecting to ODBC
> server.Could you please suggest us.
>
> Error
> [unixODBC][Driver Manager]Data source name not found, and no default driver
> specified
>
> We have followed all the procedure as mentioned in the site:
> https://apacheignite.readme.io/docs/odbc-driver
>
> Binary used :apache-ignite-fabric-1.6.0-bin
>
> Thanks,
> Agneeswaran
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Error-in-ODBC-connection-tp5493.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>