Devart Forums

First of all it seems that the main problem I encountered when using ODAC 5.x under a multi processor linux platform is fixed in ODAC 6.x. Under Linux I always received a "core dump" if I ran a multi thread application which uses TOraSessionTOraQuery (each thread had an own Session/Query). Now this works perfectly. (Yippee!)

But there is one kind of error left that appears only under linux and is reproducable under single and multi processor platforms. If I run my test app (which I can send to you if you want) and create e.g. 10 threads then there is a good chance (say 1 of 10 application starts) that I receive an 231 runtime error. This error is not kylix specific because I don't get this error if I use an Oracle access component different from ODAC.

It would be nice to have a fast solutions on this problem because then I could use ODAC for my Linux development.

Refers to ODAC 6.0.0.4 and ODAC 6.0.0.5

Please send your test application to odac*crlab*com.

FYI.

I have sent the test application by email.

Additional information:

I have tested my test application under Linux (Kylix3) with your DBExpress driver Version 3.10.8 and get the same error on a multi processor environment:

Runtime error 231 at 080587A5
19193 Speicherzugriffsverletzung

(Speicherzugriffsverletzung is the german equivalent to "memory access violation")

Under DBExpress I use TCRSqlConnection with direct NET connection, so no oracle client is involved.

Hope this helps.