Re: Oracle7 ODBC Errors (Lots of 'em)
Date: Wed, 23 Nov 1994 17:23:17 GMT
Message-ID: <CzqDMt.q59_at_dwp.la.ca.us>
In article <James.Lawrence.15.000FC819_at_epamail.epa.gov>, James.Lawrence_at_epamail.epa.gov (Lawrence James) says:
>
>In article <mcallister.3.00090CA2_at_neptune.grad.missouri.edu> mcallister_at_neptune.grad.missouri.edu (Andrew McAllister) writes:
>>From: mcallister_at_neptune.grad.missouri.edu (Andrew McAllister)
>>Subject: Oracle7 ODBC Errors (Lots of 'em)
>>Date: Mon, 7 Nov 1994 09:02:54
>>Summary: Lots of stupid errors in Oracle 7 ODBC
>>Keywords: Oracle7, ODBC, Errors
>>I'm getting lots of errors while using Oracle's ODBC drivers for
>>version 7.
...
>>Symptom: Various actions using MS Access 2.0 and MS Query produce the
>>following error: "ODBC Specification Comformance Error (-7711). This error
>>should be reported to the ODBC driver vendor."
>>
James,
I'd like to know what hardware/software configuration you are using. In general I think this error means that Windows has run out of resources, especially memory. There is a known memory leak in Access 2.0. For me, this error shows up on some machines when some AccessBasic code runs which is supposed to populate a table on Oracle. I have many tables in my application (all on Oracle), although none of them use a SELECT * FROM foo, they use SELECT field1, field2... type of query files.
The following cases apply:
Case 1: Client: Dell 486/33, 16 MB RAM, SQL*NET TCP/IP V1 for Windows, ChameleonNFS Server: IBM RS/6000, AIX V3.2.5, Oracle 7.0.16, SQL*NET TCP/IP V1 Result: No errors at all Case 2:
Client: Dell 486/33, 16 MB RAM, SQL*NET TCP/IP V1 for Windows, ChameleonNFS Server: Dell 486/33, 16 MB RAM, OS/2 2.1, IBM TCP/IP V2, Oracle 7.0.12
SQL*NET TCP/IP V1
Result: ODBC -7711 Error when AccessBasic Code runs
Case 3: Client: IBM PS/2 DX2/66, 16 MB RAM, SQL*NET TCP/IP V1 for Windows, Sun PC-NFS V5.0 Server: Dell 486/33, 16 MB RAM, OS/2 2.1, IBM TCP/IP V2, Oracle 7.0.12 SQL*NET TCP/IP V1
Result: ODBC -7711 Error when AccessBasic Code runs
The main conclusions are:
- Sun PC-NFS 5.0 causes errors, or
- Oracle 7.0.12 on OS/2 causes errors
- Some wierd ODBC/PC configuration setting I haven't identified yet.
I will soon put the Case 1 client on the Case 2 server and see if this is a problem.
If you think of something please let me know.
Best wishes,
Hector Pujol
hpujol_at_tsunami.dwp.la.ca.us
>
Received on Wed Nov 23 1994 - 18:23:17 CET