Home » RDBMS Server » Networking and Gateways » ORA-12203: Unable to connect to destination. (Oracle 10g)
ORA-12203: Unable to connect to destination. [message #422012] Sun, 13 September 2009 04:54 Go to next message
mbmalasenthil
Messages: 27
Registered: July 2008
Junior Member
Hi,

I have Oracle 10g installed on my system. I notice that when i start my machine without connecting to internet i am able to connect to the db from informatica using ODBC connection. But if i start my machine with the net connection it gives me the error ORA-12203: Unable to connect to destination. I opened ODBC and tried to test the connection but ended up getting the same error. I opened the listener.log file and found the following error:
<code>
13-SEP-2009 15:12:11 * ping * 0
13-SEP-2009 15:12:12 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=SYSTEM))(COMMAND=status)(ARGUMENTS=64)(SERVICE=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT =1521)))(VERSION=168821248)) * status * 0
13-SEP-2009 15:12:19 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=3200)) * establish * orcl * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
13-SEP-2009 15:12:19 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=3201)) * establish * orcl * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
13-SEP-2009 15:12:19 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=3203)) * establish * orcl * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
13-SEP-2009 15:12:19 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=3204)) * establish * orcl * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
13-SEP-2009 15:12:20 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=))(SERVICE_NAME=orcl)) * (ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=3206)) * establish * orcl * 12514
TNS-12514: TNS:listener does not currently know of service requested in connect descriptor
</code>
I notice here that the port it uses to connect is not 1521. What could be the problem. Any help would be appreciated.

Thanks,
Senthil
Re: ORA-12203: Unable to connect to destination. [message #422013 is a reply to message #422012] Sun, 13 September 2009 05:00 Go to previous message
Michel Cadot
Messages: 64151
Registered: March 2007
Location: Nanterre, France, http://...
Senior Member
Account Moderator
ORA-12203: TNS:unable to connect to destination
 *Cause: Invalid address specified or destination is not listening.
 This error can also occur because of underlying network or network
 transport problems.
 *Action: Verify that the net service name you entered was correct.
 Verify that the ADDRESS portion of the connect descriptor which
 corresponds to the net service name is correct.  Ensure that the
 destination process (for example the listener) is running at the
 remote node.

ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
 *Cause:  The listener received a request to establish a connection to a
 database or other service. The connect descriptor received by the listener
 specified a service name for a service (usually a database service)
 that either has not yet dynamically registered with the listener or has
 not been statically configured for the listener.  This may be a temporary
 condition such as after the listener has started, but before the database
 instance has registered with the listener.
 *Action:
  - Wait a moment and try to connect a second time.
  - Check which services are currently known by the listener by executing:
    lsnrctl services <listener name>
  - Check that the SERVICE_NAME parameter in the connect descriptor of the
    net service name used specifies a service known by the listener.
  - If an easy connect naming connect identifier was used, check that
    the service name specified is a service known by the listener.
  - Check for an event in the listener.log file.

Regards
Michel
Previous Topic: Network connection ways of debugging web report on different operating systems with VMware
Next Topic: Telnet 1521
Goto Forum:
  


Current Time: Fri Dec 09 15:10:40 CST 2016

Total time taken to generate the page: 0.25973 seconds