[unixODBC-support] ODBC TIMING-OUT ISSUE

Lazghab Souheil Souheil.Lazghab at edb.com
Thu Mar 25 16:39:45 GMT 2010


The value for should be specified in seconds right? What is the MAX limit? Could be some hours?

Best Regards 
Souheil Lazghab
System Consultant
 
EDB Business Partner Norge AS 
Telefon: 22 52 80 80, Mobile: +47 90 69 66 40
E-post: Souheil.Lazghab at edb.com 
www.edb.com 
 
"EDB - En sterk og nær IT-partner


-----Original Message-----
From: Martin Evans [mailto:martin.evans at easysoft.com] 
Sent: 25. mars 2010 17:32
To: Support for the unixODBC project
Cc: Lazghab Souheil
Subject: Re: [unixODBC-support] ODBC TIMING-OUT ISSUE

Peter Harvey wrote:
> I was suggesting altering the code/program which is accessing the data. If you 
> do not have access to or an ability to change the code than you can ignore my 
> comment :)
> 
> --
> Peter

I'm not sure that is quite correct now Peter. There is a way to add
environment attributes and connection attributes into the odbc.ini.
Something like:

DMConnAttr = CONNECTION_ATTRIBUTE=value

See
http://www.easysoft.com/developer/interfaces/odbc/linux.html#env_unixodbc

Of course, you need to ascertain if you really want connection timeout
or query timeout.

Martin
-- 
Martin J. Evans
Easysoft Limited
http://www.easysoft.com

> On Thursday 25 March 2010 07:50:05 am Lazghab Souheil wrote:
>> Hi Peter,
>>
>> Thank you for  your help. I am wondering which file this
>>  SQLSetConnectionAttr should be located to? Is it in the default
>>  configuration file .odbc.ini? -----------------
>> [OracleODBC-10g]
>> Application Attributes = T
>> Attributes = W
>> BatchAutocommitMode = IfAllSuccessful
>> BindAsFLOAT = F
>> CloseCursor = F
>> DisableDPM = F
>> DisableMTS = T
>> Driver = Oracle 10g ODBC driver
>> DSN = OracleODBC-10g
>> EXECSchemaOpt =
>> EXECSyntax = T
>> Failover = T
>> FailoverDelay = 10
>> FailoverRetryCount = 10
>> FetchBufferSize = 128000
>> ForceWCHAR = F
>> Lobs = T
>> Longs = T
>> MetadataIdDefault = F
>> QueryTimeout = T
>> ResultSets = T
>> ServerName = fd10mf
>> SQLGetData extensions = F
>> Translation DLL =
>> Translation Option = 0
>> DisableRULEHint = T
>> UserID =
>>
>>
>>
>> Best Regards
>> Souheil Lazghab
>> System Consultant
>>  
>> EDB Business Partner Norge AS
>> Telefon: 22 52 80 80, Mobile: +47 90 69 66 40
>> E-post: Souheil.Lazghab at edb.com
>> www.edb.com
>>  
>> "EDB - En sterk og nær IT-partner
>>
>>
>> -----Original Message-----
>> From: Peter Harvey [mailto:pharvey at peterharvey.org]
>> Sent: 25. mars 2010 15:33
>> To: Support for the unixODBC project
>> Cc: Lazghab Souheil
>> Subject: Re: [unixODBC-support] ODBC TIMING-OUT ISSUE
>>
>> You may want to play around with the connection time out attributes (see
>> SQLSetConnectionAttr/SQLGetConnectAttr) from a second thread. If you are
>> lucky the client and server side will be able to process. For example;
>> getting SQL_ATTR_CONNECTION_DEAD may result in some sort of ping which
>> may keep your connection alive (assuming its your connection which is
>> timing out).
>>
>> --
>> Peter
>>
>> Lazghab Souheil wrote:
>>> Hi,
>>> I am using ODBC to make some processes communicate with identical
>>> ORACLE bases with identical schemas which are located in different AIX
>>> virtual portions through network.
>>> These processes reads from the original oracle base and writ/*e */ to
>>> its clone one which should be located on a remote AIX portion.
>>> This ODBC was recommended to us because it will make us able to run
>>> different process against different database storage platforms at any
>>> time. At the moment we are running only a single process at our ORACLE
>>> environments
>>> I am experiencing a timing out issue when the ODBC-DRIVER sends
>>> DELETING SQL statement against large tables (talking here about tables
>>> with 30 million records) during its updating routines at the cloned
>>> ORACLE base. As a consequence the next SQL statement defined at our
>>> process won't be executed because the ODBC driver had timed out due to
>>> the large processing time.
>>> This timing out issue was due to that the ORACLE environment at theses
>>> servers huge time to execute the DELET statement.
>>> We are looking for a way how we can configure the ODBC to extend its
>>> STAND BY time during executing theses large SQL statements.
>>> As far as I know the only possible value that we can extend here as it
>>> was described in your website is the CPTimeout defined at the
>>> odbcinst.ini file located under: /opt/unixodbc/etc
>>> -------------------------------------------------------
>>> [ODBC]
>>> Trace = No
>>> Trace File = /tmp/sql.log
>>> Pooling = Yes
>>> [INTERBASE-P]
>>> Description = Easysoft Driver for Interbase
>>> Driver = /usr/local/lib/libib6odbc.so
>>> Setup = /usr/local/lib/libib6odbcS.so
>>> FileUsage = 1
>>> DontDLClose = 1
>>> CPTimeout = 120
>>> [INTERBASE]
>>> Description = Easysoft Driver for Interbase
>>> Driver = /usr/local/lib/libib6odbc.so
>>> Setup = /usr/local/lib/libib6odbcS.so
>>> FileUsage = 1
>>> DontDLClose = 1
>>> CPTimeout = 0
>>> -------------------------------------------------------
>>> Can you help me with this issue?
>>> Best Regards
>>> *Souheil Lazghab*
>>> System Consultant
>>> EDB Business Partner Norge AS
>>> Telefon: 22 52 80 80, Mobile: +47 90 69 66 40
>>> E-post: _Souheil.Lazghab at edb.com_ <mailto:Souheil.Lazghab at edb.com>
>>> _www.edb.com_ <http://www.edb.com/>
>>> "EDB - En sterk og nær IT-partner
>>>
>>>
>>> _______________________________________________
>>> unixODBC-support mailing list
>>> unixODBC-support at mailman.unixodbc.org
>>> http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
> _______________________________________________
> unixODBC-support mailing list
> unixODBC-support at mailman.unixodbc.org
> http://mailman.unixodbc.org/mailman/listinfo/unixodbc-support
> 
> 


More information about the unixODBC-support mailing list