Sql.ini and odbc block the computer

forum.gupta.bugreport (2005-2010)
Didier Tourneur

Sql.ini and odbc block the computer

Post by Didier Tourneur » 20 Feb 2006, 13:47

 Posted by:  Didier Tourneur 

Hello
Since the version 2005.1 when the remotedbname and the dsn are the same,
some transactions block all the processes on the client

example
[odbcrtr]
remotedbname=db,DSN=db

The solution is to kill the process

Someone have a idea to not rename the dsn

Didier

It 's on sqlserver

Clifford Bass

Re: Sql.ini and odbc block the computer

Post by Clifford Bass » 20 Feb 2006, 19:57

 Posted by:  Clifford W. Bass 

Hi Didier,

How about deleting your DSN and using a DSNless connection? For
example, use "Driver={Gupta SQLBase};Database=DB" for your connection
string.

Clifford Bass

Didier Tourneur

Re: Sql.ini and odbc block the computer

Post by Didier Tourneur » 21 Feb 2006, 09:37

 Posted by:  Didier Tourneur 

I create a new connexion with sqlserver.
In my section odbcrt I have only

[odbcrtr]
remotedbname=db,DSN=db

It's only win td2005.1

Didier

Clifford Bass

Re: Sql.ini and odbc block the computer

Post by Clifford Bass » 21 Feb 2006, 20:26

 Posted by:  Clifford W. Bass 

Hi Didier,

The issue of remote and DSN names being the same and causing trouble
has been a long standing problem. I am not familiar with TD, so am not able
to be specific. I presume that there is some specific reason for not
renaming the DSN. Any reason you could not rename the database instead?
For the 2 cents that it may be worth in the future to you... I make it a
policy to make sure the database names and the DSN names are different;
usually appending _ODBC to the end of the database name (i.e. MYDB and
MYDB_ODBC).

Clifford Bass

Didier Tourneur

Re: Sql.ini and odbc block the computer

Post by Didier Tourneur » 22 Feb 2006, 09:47

 Posted by:  Didier Tourneur 

I have changed the name, but it's difficult with 1 thousand end user

and it was ok with td 2005 and the previous versions

Didier

shyam

Re: Sql.ini and odbc block the computer

Post by shyam » 22 Feb 2006, 12:40

 Posted by:  shyam 

Hi Didier,

Are u using TD 2005.1 or TD2005.1 PTF1 because in PTF1 TD does not look in
the sql.ini for connection thru ODBC. It directly takes from the ODBC
Administrator. You just have to mention the dsn name in the application. So,
it should not matter what u specify in the sql.ini. I guess this was a
problem introduced with TD 2005.1 and that was fixed in PTF1 (TD referring
to sql.ini for connection thru ODBC). I think u can download and install
PTF1 and see if the problem still persists. Can give a try.

If u still see the problem let me know what kind of transactions are you
trying i mean are you having huge transactions or is it failing with less
transactions also.

Regards,
shyam

Return to “gupta.bugreport”

Who is online

Users browsing this forum: [Ccbot] and 0 guests