[unixODBC-support] Oracle9i & unixODBC & FreeTDS

Stefan Radman Stefan.Radman at CTBTO.ORG
Fri Jun 2 08:26:18 BST 2006

> Both of these odbc.ini files are symbolic links to
> (I presume this should function ?)
Yes, it should function but it's not a good idea. Remove at least the
symbolic link $HOME/.odbc.ini
$HOME/.odbc.ini is expected to be writeable by the user owning $HOME and
that's most likely not the case.
It's enough to have the DSN you need in either of them (e.g.

What does "odbcinst -j" report?

> Unixodbc version: 2.1.1
That version is quite outdated (23-Mar-2002).
You should get a more recent one (e.g. 2.2.11)

> The oracle user has an env var ODBCSYSINI=/usr/local/etc/odbc.ini and
an ODBCINI=/etc/odbcini
You don't need either of these variables. You can unset them.
"odbcinst -j" tells you where unixODBC expects its config files and its
easiest to use these defaults.

ODBCSYSINI is used to point unixODBC to a different system-wide
configuration directory that contains the system-wide odbc.ini and
odbcinst.ini. It must point to a directory.
ODBCINI is used to point to a different user odbc.ini (alternative to
$HOME/.odbc.ini). It must point to a file.
If you really want to set them the correct setting for your case:

If nothing of that information helps have a look at this thread
At least it's related.



	From: unixodbc-support-bounces at easysoft.com
[mailto:unixodbc-support-bounces at easysoft.com] On Behalf Of Lars
	Sent: Friday, 02 June, 2006 01:05
	To: unixodbc-support at easysoft.com
	Subject: [unixODBC-support] Oracle9i & unixODBC & FreeTDS

		Hello list, 

		I'm having a problem with a oracle HS, unixodbc &
freetds...I'm posting this here first because the trace shows unixodbc
is unhappy.

	Oracle HS is writing this in the HS log file: 

		[Generic Connectivity Using ODBC] version:

	connect string is: defTdpName=ascom;SYNTAX=(ORACLE8_HOA,





	<datasource name='ascom' type='GENERIC_ODBC_FOR_HS'


	<misc year2000Policy='-1' consumerApi='1'

	parserDepth='2000' noInsertParameterization='true'


	ORACLE GENERIC GATEWAY Log File Started at 01-Jun-06 23:57:47

	[unixODBC][Driver Manager]Data source name not found, and no
default driver

	specified (SQL State: 00000; SQL Code: 0)

	(Last message occurred 2 times)

		The part from unixODBC seems to be stopping the show
here I think...but I'm not sure.

	Strange thing is that I can connect&query with isql on this db
and that seems to work excellent.

	The fact that isql working makes me believe unixodbc & freetds
are ok from the commandline.

		Some info: 

		Unixodbc version: 2.1.1


	Compile-time settings (established with the "configure" script):

	Version: freetds v0.63

	MS db-lib source compatibility: no

	Sybase binary compatibility: unknown

	Thread safety: yes

	iconv library: yes

	TDS version: 8.0

	iODBC: no

	unixodbc: yes 

		Odbcinst.ini has an entry for freetds

	Oracle user has a $HOME/.odbc.ini 

	The system has /etc/odbc.ini 

	Both of these odbc.ini files are symbolic links to

	(I presume this should function ?)

		The oracle user has an env var
ODBCSYSINI=/usr/local/etc/odbc.ini and an ODBCINI=/etc/odbcini

		Still, when called through HS unixODBC seems unable to
find the dsn files, most likely due to my stupidity J

	I've tried setting the envs in listener.ora, it seems to go the
unixodbc according the listener trace, but unixodbc in turn is

		What am I missing here ?

	Thanks for any help J




			The information contained in this e-mail,
including any attachments to it, is confidential and intended 
	only for the person(s) to whom it is addressed. Any examination,
distribution, disclosure, printing, or 
	copying of this information, or reliance upon this information
by any person other than the intended 
	recipient(s) is strictly prohibited. If this e-mail has been
misdirected and you are not the intended 
	recipient, please notify the sender immediately and delete this
e-mail from your system. The views and 
	opinions contained in this transmission represent those of the
author and do not necessarily reflect 
	those of AIRCOM International. AIRCOM International may monitor
incoming and outgoing e-mails. By 
	replying to this message, you consent to this monitoring. This
e-mail has been scanned by McAfee Group 
	Shield prior to transmission. However, recipients are advised to
apply their own antivirus detection 
	measures to this e-mail and any attachments upon receipt. AIRCOM
International does not accept 
	liability for any damage or losses arising as a result of
receiving this e-mail.

More information about the unixODBC-support mailing list