Re: ODBC and sqlnet don't mix

In article <317BDA30.7E0D_at_macromedia.com>, Rich Headrick <rheadric_at_macromedia.com> wrote:
>Greetings,
>
>I have had the worst experience in my entire career trying to install
>PO7, sqlnet,tcp/ip and one tiny little driver by Intersolv.
>
>First, had to set up the server(sun sparc with Oracle 7.2, sqlnet 2.x).
>Did it, not much of a problem. It accepts connections through tns.
>
>Second, had to set up my win95 pc with PO7 for win95. The engine
>installed fine. Then added the sqlnet/tcp/ip stuff. The tnsnames shit
>is really a drag. Couldn't Oracle have come up with a better method.
>Oh, by the way did I mention the fact that I did without the sqlnet
>manual, BECAUSE ORACLE GOT EM' BACKORDED. After installing the sqlnet
>stuff, I then ftp'd my sqlnet.ora, tnsnames.ora, and listener.ora.
>
>What a joke, what little tid bits of info I found actually included the
>step to ftp the config files to the server. There's NO EXCUSE for this
>Oacle Corp. It's just plain and simple laziness. The methods in which
>you have encapsulated you market has really put big bucks you pocket,
>but leaves a bad taste in ones mouth after doing an install & needing
>a little help. Shame on you
>
>At any rate, I finally got sqlnet up & running, after having to purchase
>the complete PO7 package. All I needed was sqlnet v2.x. Oracle
>wouldn't sell it. ALL OR NULL. So all is up and well. I can manage
>the server from my pc. Yippeee.
>
>Then theres the ODBC thing. We're developing a web app that uses ODBC
>as the connect to most major databases(stand alone and client/server).
>Fine, installed Intersolves 32bit ODBC driver. Went in and configured
>a few connects, and then attemped to use the connects in our product.
>Found out that when using sqlnet, all operations done durring that
>session must be within 1(one) thread.
>
>That hosed it. My client software crashes because sqlnet is a single
>thread product.

You should be able to use multiple threads just fine. You just can't login to one thread and try to open a cursor with that login on another.

If you're not doing that, then maybe it's the ODBC driver... Received on Wed Apr 24 1996 - 00:00:00 CEST