Connection Pooling causes sqlnet.log error 12203
391300Apr 15 2003 — edited Apr 16 2003We have a VB 6 application that uses ADO and ODBC connection pooling via the SQLSetEnvAttr ODBC API function. This application uses Oracle 8.0.5.0
database and Oracle (8.0.5.10) drivers on the client. After the application is exited, a file named sqlnet.log is created in the current working directory. The file contents are as follows:
Fatal NI connect error 12203, connecting to:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle80)(ARGV0=oracle80ORCL)(ARGS='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=C:\MYPROGRAM.EXE)(HOST=Host)(USER=User))))
VERSION INFORMATION:
TNS for 32-bit Windows: Version 8.0.5.0.0 - Production
Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 8.0.5.0.0 - Production
Time: 02-APR-03 16:13:29
Tracing not turned on.
Tns error struct:
nr err code: 12203
TNS-12203: TNS:unable to connect to destination
ns main err code: 12560
TNS-12560: TNS:protocol adapter error
ns secondary err code: 0
nt main err code: 102
TNS-00102: Keyword-Value binding operation error
nt secondary err code: 0
nt OS err code: 0
We have removed all other services from the TNSNAMES.ORA except our TCP service and removed all listeners from the LISTENER.ORA on the server except our TCP port. The application seems to function correctly and also queries the database correctly, but causes a crash on some systems. We are wondering if anyone has seen this error in the sqlnet.log file and found a resolution or if anyone has seen this problem using ODBC connection pooling.