Removing the Oracle Names entry didn't seem to affect the performance of
connection creation. However, now that the SGA is much smaller, things seem
to zip along quite quickly. Transactions are very quick (although we aren't
doing an OLTP application), and connections only take a second or two to
establish.
Khalid.
"Khalid Eidoo" <someone_at_rogers.com> wrote in message
news:eXCI8.107189$ah_.8711_at_news01.bloor.is.net.cable.rogers.com...
> Well, I do have an entry for Oracle Names in my sqlnet.ora file. I will
> remove it and give it a go.
>
> Thanks,
>
> khalid.
>
> "Mladen Gogala" <mgogala_at_adelphia.net> wrote in message
> news:acsod4$s93rq$1_at_ID-82084.news.dfncis.de...
> > On Sun, 26 May 2002 10:53:24 -0400, Khalid Eidoo wrote:
> >
> > > The machines all sit together on a segmented 100Mb switch.
Consequently,
> > > pings are very low, usually 1-3Milliseconds. There is no firewall
> > > involved, the only other service we have running (SSH) connects almost
> > > instantly. I don't believe it is a network issue as it is something in
> > > the configuration of our listeners. I have included our listener
> > > information below.
> > >
> > > # LISTENER.ORA Network Configuration File:
> > > /home/oracle/config/9.0.1/listener.ora # Generated by Oracle
> > > configuration tools.
> > >
> > > FORSYS =
> > > (DESCRIPTION =
> > > (ADDRESS = (PROTOCOL = TCP)(HOST = forsys.terida.com)(PORT =
1521))
> > > )
> > >
> > > SAVE_CONFIG_ON_STOP_FORSYS = TRUE
> > >
> > > SID_LIST_FORSYS =
> > > (SID_LIST =
> > > (SID_DESC =
> > > (GLOBAL_DBNAME = forsys.terida.com)
> > > (ORACLE_HOME = /opt/oracle/product/9.0.1) (SID_NAME = forsys)
> > > )
> > > )
> > >
> > > # TNSNAMES.ORA Network Configuration File:
> > > /home/oracle/config/9.0.1/tnsnames.ora # Generated by Oracle
> > > configuration tools.
> > >
> > > FORSYS =
> > > (DESCRIPTION =
> > > (ADDRESS_LIST =
> > > (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
> > > )
> > > (CONNECT_DATA =
> > > (SERVICE_NAME = forsys)
> > > )
> > > )
> > >
> >
> > Do you have sqlnet.ora? If sqlnet.ora has several access paths
> > specified, your client might be waiting for an LDAP connection or
> > Oeracle*Names connection or even try to resolve a hostname like orasrv01
> > (I forgot the details about the default Oracle*Names server and I'm too
> > lazy to search the metalink right now.) I'm interested in sqlnet.ora
from
> both
> > client and server.
> > --
> > Mladen Gogala
> > Za Feral Spremni!
>
>
Received on Tue May 28 2002 - 14:21:05 CDT
