Category: SQL*Net, Protocol Server

September 29

Say it’s that day again. You try to connect to a (new) database and once again you are facing SQL*Net problems.

C:/oracle/product/10.1.0/client/BIN>sqlplus /nolog
 
SQL*Plus: Release 10.1.0.4.0 - Production ON Thu Sep 29 10:37:15 2005
Copyright (c) 1982, 2005, Oracle.  ALL rights reserved.
 
 
SQL> conn scott/tiger@lab.amis.nl
 
 
ERROR: ORA-12154: 
TNS:could NOT resolve the CONNECT identifier specified

Blast!. What can you do? Once in a while i get a lot of these SQL*Net problems (network changes, etc, the wrong weather type). So to help you (and me), here i will you give you my grey-matter checklist 🙂 (it’s not complete but should help you to resolve 80% of the problems)

March 3

It’s possible to have also two different version listeners (the 9 and 10 version) running, by settting different ORACLE_HOME’s and PATH’s, and starting the different listeners. I like to have 1 listener – as long as this can be maintained regarding incompatibility and bugs etc – therefore my latest listener version is leading (version 10g). Set your ORACLE_HOME accordingly. My 10g Oracle home is placed in directory/oracle/rdb10g/ and my TNS_ADMIN directory is set to directory /oracle/network/admin.

C:\> export ORACLE_HOME=/oracle/rdb10g
C:\> export TNS_ADMIN=/oracle/network/admin
C:\> export PATH=$ORACLE_HOME/bin:$PATH