Re: ODBC NT server client takes 30 minutes to connect o Oracle 7.3.2 server when on isolated network???

"Marky Mark" <DontSpamMe_at_Nospam.org> wrote in message news:3v9fit85l7fmeauolfaus5lm0ncg4mef7d_at_4ax.com...
> I'm having a weird connection problem with I put my HP 10 / Oracle
> 7.3.2 system in it's own sandbox with an NT4 stand-alone server
> acting as an ODBC client. The NT client uses an ODBC connection to
> talk to the Oracle database. If both are on the regular network
> (with an external gateway and the external name servers) everything
> works fine.
>
> However, I need to isolate them for special project, so both the NT4
> server and the HP 10 / Oracle 7.3.2 box are on their own physical
> network, i.e. I pull the hub's connection to the rest of the network
> and they just share the hub they are on.
>
> With their hub OFF the network, it takes an ungodly amounts of time
> to make an initial ODBC connection from the NT4 stand alone server
> to the Oracle database. 25-30 minutes. That's pretty terrible
> performance for such a high touted DB on a network with just the two
> machines and nothing else running.
>
> Both machines can ping each other by name. Other services like FTP
> and Telnet from the Oracle server (HP) side return right away.
>
> Likewise, when I start the Oracle listener on the HP-UX 10 system,
> it takes a full 30 minutes to start up, instead of less than 30
> seconds. I can do a DBSTART and the database comes up just fine, but
> LSNRCTL START just says 'please wait ...' and them clams up.
>
> I manage to find a file (listener.ora) that had the host name in it,
> so I change the host= line to use the IP address instead but that
> made no difference.
>
> I changed /etc/nsswitch.conf to the 'filesdns' HP example file so it
> should use the hosts file first and not be looking for either
> the gateway machine or the name server that are beyond that (no name
> servers on the internal net). Both the FDQN and the host name for
> itself and the client machine are in it's hosts file. I've removed
> the name server entries from /etc/resolv.conf.
>
> I'm assuming maybe something in the Oracle 7.3.2 configuration has
> to be adjusted, but I have no idea what. Anyone have any suggestions
> as to why these two would take so long to make an initial db connect
> when isolated on their own hub? Makes no sense to me, but then it's
> Oracle.
>
> I got thrown into this quagmire and know next to nothing about
> oracle, so I have no idea where to look or what to do to oracle to
> make it behave.
>
> Does anyone have any ideas? Should I just tell the company that
> oracle isn't worth the trouble supporting as a database for our
> product?
>
> TIA,
> Mark
>
>

First of all: Oracle 7.3.2 has been desupported *3 years ago* so I don't know why your firm is still using it.
That specific release came with a new Oracle trace facility, which was by default enabled, and which was in many cases responsible for the delays you report.
You should make sure the init.ora parameter oracle_trace_enable has been set to false.
Also you should try to see what happens when you connect using sqlplus and/or tnsping the database. If this was really a server problem and not an odbc problem, you would expect similar delays here. You could also tweak your sqlnet.ora
automatic_ipc = off
trace_level_client= off
names.directory_path=(tnsnames, onames)

etc.
Quite frankly I don't think it is Oracle. By disconnecting you must have created a network config problem. A gateway might have been misconfgured etc, etc, etc.

Hth,

Sybrand Bakker, Oracle DBA Received on Sat Jul 21 2001 - 23:12:02 CEST