Agneeswaran, What I can see is that SEGFAULT caused by the misuse of the SQLGetDiagRec - our current implementation of the function assumes that TextLengthPtr could not be NULL. Fix that and you are going to get some meaningful error message that we could analyze further. From the core dump it looks like a "Failed to run map query remotely." error message, but it's better to be sure.
Best Regards, Igor On Wed, Jul 13, 2016 at 11:14 AM, Agneeswaran < [email protected]> wrote: > Hi Igor, > > Please find the attached lib files, > > Thanks, > Agneeswaran > > lib1.zip > <http://apache-ignite-users.70518.x6.nabble.com/file/n6257/lib1.zip> > > lib2.zip > <http://apache-ignite-users.70518.x6.nabble.com/file/n6257/lib2.zip> > > lib3.zip > <http://apache-ignite-users.70518.x6.nabble.com/file/n6257/lib3.zip> > > lib4.zip > <http://apache-ignite-users.70518.x6.nabble.com/file/n6257/lib4.zip> > > lib5.zip > <http://apache-ignite-users.70518.x6.nabble.com/file/n6257/lib5.zip> > > > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Issue-with-concurrent-users-on-Ignite-1-6-0-ODBC-tp6217p6257.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
