Re: database connectivity/tnsping problem

"B. Kloppt" <b_kloppt_at_my-deja.com> wrote in message news:3717b54f.0302050329.1001d0b3_at_posting.google.com...
> "JustAnotherDBA" <jadba_at_bellsouth.net> wrote in message
news:<N8F%9.11098$sm3.10960_at_news.bellsouth.net>...
> > The tnsping utility simply tells you if an Oracle listener is listening.
It
> > does not tell you if there is a database running on the server.
> >
> > So, the tnsping using an ip address IS doing Hostname Method of lookup
and
> > IS finding an Oracle listener at that ip address .
> >
> > The tnsnames (Local Method) should work... if everything is coded
correctly
> > (since you apparently have connectivity from the client to server -
Hostname
> > method worked).
> >
> > Are you sure you coded the service_name correctly in the tnsnames.ora ?
> > What does your listener.ora look like on the server (192.168.2.25)? What
> > does your init.ora look like on the server (especially the service_name
> > parameter)?
> >
> > Note: You should not specify a default domain of world. Actually, a more
> > appropriate default domain would be domain.la (in LA) and domain.ny (in
NY).
> > That way you could simply say connect to 'orcl' and it would find the
one in
> > your local domain. To get to the other domain , you will always need to
> > specify/fully-qualify the other domain.
> >
> >
>
> hi,
>
> thanks for your reply.
>
> i think the tnsping utility will tell me if there is a certain
> database running on the server, as long as it is _indeed_ running and

Sorry. I am positive you are mistaken. The tnsping utility will NOT tell you if a database is running on the server.

But, I suggest you always try stuff like this for yourself ... to prove if I am right or wrong :)

> the entry is found in tnsnames.ora.
> the tnsping utility will, however, fail if the pinged service/db does
> not exist.
>
> as for the coding of the service name in tnsnames.ora, i've checked
> that many times and it is indeed correct.
>

I see from other posts after this one, that you found an error in the client tnsnames.ora .

Good to hear you have solved your own problem :)

> here's what the listener.ora on the server (192.168.2.25) looks like:
> ---8<-------------------------------------------------------------
> # LISTENER.ORA Network Configuration File:
> /opt/oracle/product/9i/network/admin/listener.ora
> # Generated by Oracle configuration tools.
>
> LISTENER =
> (DESCRIPTION_LIST =
> (DESCRIPTION =
> (ADDRESS_LIST =
> (ADDRESS = (PROTOCOL = TCP)(HOST = dbserver.domain.la)(PORT =
> 1521))
> )
> )
> )
>
> SID_LIST_LISTENER =
> (SID_LIST =
> (SID_DESC =
> (SID_NAME = PLSExtProc)
> (ORACLE_HOME = /opt/oracle/product/9i)
> (PROGRAM = extproc)
> )
> (SID_DESC =
> (GLOBAL_DBNAME = orcl)
> (ORACLE_HOME = /opt/oracle/product/9i)
> (SID_NAME = orcl)
> )
> )
>
> ---8<-------------------------------------------------------------
>
>
> and here is the /opt/oracle/product/9i/dbs/init.ora from the same
> server (comments omitted):
> ---8<-------------------------------------------------------------
> db_name=DEFAULT
>
> db_files = 80 #
> SMALL
>
> db_file_multiblock_read_count = 8 #
> SMALL
>
> db_block_buffers = 100 #
> SMALL
>
> shared_pool_size = 3500000 #
> SMALL
>
> log_checkpoint_interval = 10000
>
> processes = 50 #
> SMALL
>
> parallel_max_servers = 5 #
> SMALL
>
> log_buffer = 32768 #
> SMALL
>
> max_dump_file_size = 10240 # limit trace file size to 5 Meg each
>
> global_names = TRUE
>
> control_files = (ora_control1, ora_control2)
>
> ---8<-------------------------------------------------------------
>
> as you can see, there is no service_name parameter.

So, it is probably defaulting to the same as the SID . This is a guess. Query the v$parameter view to see if this is correct.

>
>
> one other thing i've discovered:
> i can tnsping from either server to the other without errors.
> it's only when i tnsping from one workstation (where only the oracle
> client is installed) of one domain to the server of another domain
> that gives me errors.
>
> to put it bluntly:
>
> tnsping workstation.domain.ny -> dbserver.domain.ny : NO ERROR
> tnsping workstation.domain.la -> dbserver.domain.la : NO ERROR
> tnsping dbserver.domain.ny -> dbserver.domain.la : NO ERROR
> tnsping dbserver.domain.la -> dbserver.domain.ny : NO ERROR
> tnsping workstation.domain.ny -> dbserver.domain.la : TNS-03505:
> Failed to resolve name
> tnsping workstation.domain.la -> dbserver.domain.ny : TNS-03505:
> Failed to resolve name
>
> could this have something to do with the client software?
Received on Wed Feb 05 2003 - 19:29:20 CST