| Fatal NI connect error 12203 resulting huge increase in sqlnet.log file [message #66900] |
Thu, 06 March 2003 02:49  |
Mitesh Vijayvargiy
Messages: 3
Registered: February 2003
|
Junior Member |
|
|
Hi,
I am getting the following error message in SQLNET.LOG file on the client machine. This is my upload program which takes few hours to complete and during the program run, the size of SQLNET.LOG file keeps on increasing and goes to 100's of MB and it contains only this error repeatedly.
But my program gets connected to Database and does the upload. But the size of SQLNET.LOG file grows like anything. Pls let me know what's going wrong.
-------------------------------------------------------
ERROR in SQLNET.LOG File -
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:ORAWIN95BINIFRUN60.EXE)(HOST=IT_DBA)(USER=IT))))
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.4.0.0 - Production
Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 8.0.5.0.0 - Production
Time: 06-MAR-03 12:37:08
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
-------------------------------------------------------
Regards,
Mitesh Vijayvargiy
|
|
|
|
|
|
| Re: Fatal NI connect error 12203 resulting huge increase in sqlnet.log file [message #66905 is a reply to message #66903] |
Fri, 07 March 2003 02:01  |
Mitesh Vijayvargiy
Messages: 3
Registered: February 2003
|
Junior Member |
|
|
Hi,
Actually I thought this error is appearing in only one of the machines, but when I am figuring out, I found the same error in almost all the client machines.
Though the programs are running fine getting the database connectivity, I am not able to find why it is giving error showing connection through BEQ protocol.
Pls someone tell me why this is happening and how I will find out which protocol it is using.
And Mahesh, I am using MTS architecture.
Regards,
Mitesh Vijayvargiy
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
