Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Net8 problem 1

Status
Not open for further replies.

THoey

IS-IT--Management
Jun 21, 2000
2,142
US
I have several Oracle 7.3.4 databases that I attach to. Everything for these has worked well for months using 7.3.4 I also recently got assigned to an Oracle 8.1.6 database that I need to attach to, so I just installed Oracle 8.1.6 Client into a new directory on my machine.

I used Net8 Configuration assistant to setup the connections to the 7.3.4 databases and I tested the connections and they tested OK. I went into ODBC data sources and updated their entries there. If I go into Oracles ODBC 32bit Test, I am able to connect to the databases. But if I run 8.1.6's SQL*Plus, I get the following error:

ORA-12505: TNS:Listener could not resolve SID given in connect descriptor

I am new to Oracle 8.1.6. Is there something else I am missing?

Thanks for any help you can offer...


Terry M. Hoey
th3856@txmail.sbc.com

Ever notice that by the time that you realize that you ran a truncate script on the wrong instance, it is too late to stop it?
 
Problem solved... I needed use the full connect string, eg, CFONE.SBC.COM, vice just CFONE. I didn't have to do this with Oracle 7.3.4. Is there anyway around having to type all that?


Terry M. Hoey
th3856@txmail.sbc.com

Ever notice that by the time that you realize that you ran a truncate script on the wrong instance, it is too late to stop it?
 
hi terry -- i you look on your client you'll find that you've now got two tnsnames.ora files....... The new one is in the net8/network/admin directory.

You'll need to keep them both in step, which is a right pain....

I would imagine that you cfone db is defined differently in the net 8 tnsnames.ora, is that right?
Mike
michael.j.lacey@ntlworld.com
 
Yeah Mike, they are a bit different. The following is from 7.3.4:
Code:
CFONE.world = 
  (DESCRIPTION = 
    (ADDRESS_LIST = 
        (ADDRESS = 
          (COMMUNITY = tcp.world)
          (PROTOCOL = TCP)
          (Host = 999.999.999.999)
          (Port = 1521)
        )
        (ADDRESS = 
          (COMMUNITY = tcp.world)
          (PROTOCOL = TCP)
          (Host = 999.999.999.999)
          (Port = 1526)
        )
    )
    (CONNECT_DATA = (SID = TCP1)
    )
  )
And the following is from 8.1.6:
Code:
CFONE.SBC.COM =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = 999.999.999.999)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SID = TCP1)
    )
  )
Now, when I start SQL*Plus 8.1.6, I have to specify
CFONE.SBC.COM as my connect string, where before, with 7.3.4, all I had to use was CFONE.

But, at least it works...


Terry M. Hoey
th3856@txmail.sbc.com

Ever notice that by the time that you realize that you ran a truncate script on the wrong instance, it is too late to stop it?
 
i just copied my 734 tnsnames file in there to be honest...
Mike
michael.j.lacey@ntlworld.com
 
I might give that a try. Of course I will make a copy of the one I got first. It works, it just takes a little more typing...

Thanks for the hint...


Terry M. Hoey
th3856@txmail.sbc.com

Ever notice that by the time that you realize that you ran a truncate script on the wrong instance, it is too late to stop it?
 
I had this exact problem when I upgrade my client workstation to 8.1.6. For me the solution was to add a parameter to the sqlnet.ora file. As I recall the entry was

NAMES.DEFAULT_DOMAIN = world

for you it would probably be

NAMES.DEFAULT_DOMAIN = SBC.COM

For some reason the sample sqlnet.ora that comes with the install doesn't include the default_domain parameter.

 
Thanks for the tip Karluk. I will give it a try, once my new SysAdmin finishes running backups (why in the middle of the day, I don't know...)


Terry M. Hoey
th3856@txmail.sbc.com

Ever notice that by the time that you realize that you ran a truncate script on the wrong instance, it is too late to stop it?
 
If you don't want to maintain two sets of files (and who does!?), you can set the environment variable TNS_ADMIN to point to a specific subdirectory, then place a single set of files in this subdirectory. This will simplify your life considerably.

Oracle applications and utilities check for this environmental variable before going to the default directories.

On my PC, I have TNS_ADMIN=c:\oranet, with SQLNET.ORA, TNSNAMES.ORA, and LISTENER.ORA stored in that subdirectory. Then I deleted all of the other NET80, NETWORK, etc. subdirectories in my various ORACLE_HOMES.

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top