DBAsupport.com Forums - Powered by vBulletin
Results 1 to 2 of 2

Thread: sqlnet error!!!

  1. #1
    Join Date
    Jan 2002
    Location
    Netherlands
    Posts
    1,587

    Question

    People,
    I have configured a database on 8.0.4 /NT4 with bequeath(local database).
    I get the following error if I use SQLplus to carry out my queries, but I have no problem whatsoever if i run the scripts thru the SQLworksheet.
    ###################################
    Fatal NI connect error 12203, connecting to:
    (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=oracle80)(ARGV0=oracle80orcl)(ARGS='(DESC RIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')))(CONNECT_DATA=(SID=ORCL)(CID=(PROGRAM=C:\WINNT\Syste m32\drwtsn32.exe)(HOST=LAPTOP_TARRY)(USER=WAGRED8))))

    VERSION INFORMATION:
    TNS for 32-bit Windows: Version 8.0.4.0.0 - Production
    Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 8.0.4.0.0 - Production
    Time: 12-FEB-02 12:04:22
    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: 530
    TNS-00530: Protocol adapter error
    nt secondary err code: 0
    nt OS err code: 0
    ####################################

    Why do I get this error?
    What does he seach for if i use the sqlplus, even though the supplier says (in case of bequeath) no additional protocol specification reqd?

    Thanx much,

    Tarry Singh
    Tarry Singh
    I'm a JOLE(JavaOracleLinuxEnthusiast)
    TarryBlogging
    --- Everything was meant to be---

  2. #2
    Join Date
    Sep 2001
    Location
    NJ, USA
    Posts
    1,287
    Probably u have not correct tnsnames.ora file, because
    your application try to connect to oracle thru dr.watson exe.
    ...
    CID=(PROGRAM=C:\WINNT\System32\drwtsn32.exe)
    ...
    and primary tns error code = 12203

    TNS-12203 TNS:unable to connect to destination
    Cause: Invalid TNS address supplied or destination is not listening. This error can also occur because of underlying network transport problems.
    Action: Verify that the service name you entered on the command line was correct. Ensure that the listener is running at the remote node and that the ADDRESS parameters specified in TNSNAMES.ORA are correct. Finally, check that all Interchanges needed to make the connection are up and running.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width