RE: Logon ONLY once in ACCESS2.0-SQL*NET...

From: p00775 <p00775_at_psilink.com>
Date: Tue, 04 Oct 94 10:14:07 -0500
Message-ID: <2990365676.1.p00775_at_psilink.com>


>When I use MS ACCESS 2.0 to Import/Export/Attach tables on ORACLE 7 through
>ODBC, I can logon ONLY ONCE in a time.
 

>For example, I can log on ORACLE to export a table from ACCESS to ORACLE7 in
>the first time. But if I want to import a table from ORACLE just after
>finishing the export, it prompts that ODBC fail when I try to logon. In the
>same time I can logon ORACLE from SUN workstation by way of SQL*Net. I cannot
>connect to ORACLE any more until I close and restart the ACCESS. Then I can
>logon again.

This sounds like a well known SQL*Net snafu. In your ORACLE.INI file, there is a line like "TCP_SERVICES_FILE=filename" This services file tells Oracle what TCP socket number to use when attempting to connect to an Oracle server. Typically the file contains a line like "orasrv 1525/tcp Oracle". One solution to the single-connect-only problem is to duplicate this line a bunch of times in the file, one per line. I've also heard that the lines position in the file can cause this problem, but I haven't found this to be true. I put about ten such duplicate lines in my services file and can have as many open connections as I want.

This probably belongs in the FAQ.

                                                Dave Trahan
                                                BrainTree Technology, Inc
                                                p00775_at_psilink.com
Received on Tue Oct 04 1994 - 16:14:07 CET

Original text of this message