Installation verification

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Installation verification

Tarala, Magesh

After Installing Driver Manager 2.3.0, I’m verifying the installation. I see an asterisk next to OK in “unixODBC Driver Manager configuration correct”.

I don’t see any indications of what’s wrong/incomplete in the logs.

 

How can I find what’s needed? How can I make the asterisk go away? Or is it ok to simply ignore it?

 

 

 

txbhunazu007:/home/magesh/sqldriver/msodbcsql-11.0.2260.0 # ./install.sh verify

 

Microsoft ODBC Driver 11 for SQL Server Installation Script

Copyright Microsoft Corp.

 

Starting install for Microsoft ODBC Driver 11 for SQL Server

 

Checking for 64 bit Linux compatible OS ..................................... OK

Checking required libs are installed ........................................ OK

unixODBC utilities (odbc_config and odbcinst) installed ..................... OK

unixODBC Driver Manager version 2.3.0 installed ............................. OK

unixODBC Driver Manager configuration correct .............................. OK*

Microsoft ODBC Driver 11 for SQL Server already installed ............ NOT FOUND

 

Install log created at /tmp/msodbcsql.17724.20020.26869/install.log.

 

One or more steps may have an *. See README for more information regarding

these steps.

txbhunazu007:/home/magesh/sqldriver/msodbcsql-11.0.2260.0 # cat /tmp/msodbcsql.17724.20020.26869/install.log

[Thu Jul 21 17:35:08 CDT 2016] Verifying on a 64 bit Linux compatible OS

[Thu Jul 21 17:35:08 CDT 2016] Checking that required libraries are installed

[Thu Jul 21 17:35:10 CDT 2016] Verifying if unixODBC is present

[Thu Jul 21 17:35:10 CDT 2016] Verifying that unixODBC is version 2.3.0

[Thu Jul 21 17:35:10 CDT 2016] Checking if Microsoft ODBC Driver 11 for SQL Server is already installed in unixODBC 2.3.0

 


_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
Reply | Threaded
Open this post in threaded view
|

Re: Installation verification

Michael König

Hi there!

 

I guess the question that matters at the end of the day is: Will my application run as intended. I would probably just run a set of integration tests which involve my application and the database in question. If you have no such tests (because the application ships without a test suite, for instance), I’d recommend to use the isql command line tool. Isql comes with the unixodbc package. Use it to connect with your database and fire a few queries. The most typical problems I encounter are: NULL values are not represented correctly, strings are not represented correctly, and unicode strings not represented correctly. Typical causes include SQLLEN bitness (32 vs 64 bits) mismatches in unixodbc and ODBC driver and badly configured locales.

 

I’d ignore the asterisk if the tests show that everything works as expected.

 

Cheers

 

Michael

 

From: <[hidden email]> on behalf of "Tarala, Magesh" <[hidden email]>
Reply-To: Support for the unixODBC project <[hidden email]>
Date: Friday 22 July 2016 at 00:42
To: "[hidden email]" <[hidden email]>
Subject: [unixODBC-support] Installation verification

 

After Installing Driver Manager 2.3.0, I’m verifying the installation. I see an asterisk next to OK in “unixODBC Driver Manager configuration correct”.

I don’t see any indications of what’s wrong/incomplete in the logs.

 

How can I find what’s needed? How can I make the asterisk go away? Or is it ok to simply ignore it?

 

 

 

txbhunazu007:/home/magesh/sqldriver/msodbcsql-11.0.2260.0 # ./install.sh verify

 

Microsoft ODBC Driver 11 for SQL Server Installation Script

Copyright Microsoft Corp.

 

Starting install for Microsoft ODBC Driver 11 for SQL Server

 

Checking for 64 bit Linux compatible OS ..................................... OK

Checking required libs are installed ........................................ OK

unixODBC utilities (odbc_config and odbcinst) installed ..................... OK

unixODBC Driver Manager version 2.3.0 installed ............................. OK

unixODBC Driver Manager configuration correct .............................. OK*

Microsoft ODBC Driver 11 for SQL Server already installed ............ NOT FOUND

 

Install log created at /tmp/msodbcsql.17724.20020.26869/install.log.

 

One or more steps may have an *. See README for more information regarding

these steps.

txbhunazu007:/home/magesh/sqldriver/msodbcsql-11.0.2260.0 # cat /tmp/msodbcsql.17724.20020.26869/install.log

[Thu Jul 21 17:35:08 CDT 2016] Verifying on a 64 bit Linux compatible OS

[Thu Jul 21 17:35:08 CDT 2016] Checking that required libraries are installed

[Thu Jul 21 17:35:10 CDT 2016] Verifying if unixODBC is present

[Thu Jul 21 17:35:10 CDT 2016] Verifying that unixODBC is version 2.3.0

[Thu Jul 21 17:35:10 CDT 2016] Checking if Microsoft ODBC Driver 11 for SQL Server is already installed in unixODBC 2.3.0

 


_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
Reply | Threaded
Open this post in threaded view
|

Re: Installation verification

Nick Gorham-2
In reply to this post by Tarala, Magesh
On 21/07/16 23:42, Tarala, Magesh wrote:

After Installing Driver Manager 2.3.0, I’m verifying the installation. I see an asterisk next to OK in “unixODBC Driver Manager configuration correct”.

I don’t see any indications of what’s wrong/incomplete in the logs.

 

How can I find what’s needed? How can I make the asterisk go away? Or is it ok to simply ignore it?


No idea, that not our code thats doing that.

--
Nick

_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
Reply | Threaded
Open this post in threaded view
|

Re: Installation verification

Daniel Kasak
In my experience, freetds works a lot better than Microsoft's implementation. I've used it quite extensively, including in a very large banking migration project. I believe Microsoft have abandoned their Linux client - at least that was my impression last time I looked into it.

Dan

On Fri, Jul 22, 2016 at 5:21 PM, Nick Gorham <[hidden email]> wrote:
On 21/07/16 23:42, Tarala, Magesh wrote:

After Installing Driver Manager 2.3.0, I’m verifying the installation. I see an asterisk next to OK in “unixODBC Driver Manager configuration correct”.

I don’t see any indications of what’s wrong/incomplete in the logs.

 

How can I find what’s needed? How can I make the asterisk go away? Or is it ok to simply ignore it?


No idea, that not our code thats doing that.

--
Nick

_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support



_______________________________________________
unixODBC-support mailing list
[hidden email]
http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support