Re: Oracle 8i login is very slow

"Frank Y" <zafemail_john_at_yahoo.com> wrote in message news:2fcf2d80.0304120212.46794e29_at_posting.google.com...
> Hi all,
>
> I have two Windows 2000 Servers:
> 1. Compaq Server with one 2.4G CPU, 1G RAM and 30G harddisk
> 2. Acer Server with one 2.4G CPU, 1G RAM and 30G harddisk
>
> The software configuration of two server are identical, they both
> have:
> 1 Windows 2000 Server with SP3
> 2 Oracle 8i ( Oracle configuration(such SGA, buffer size, etc...) are
> also identical
>
> But I found two strange things I cannot explain.
>
> 1.)
> When I local(not throuhg network) login Oracle on Compaq Server, it
> only takes no more than 1second to login. But When I local login
> Oracle on Acer Server it takes about 3 seconds to logon.
>
> 2.)
> I local login to Oracle on Acer Server, and followed by executing a
> query which involves external procedure call, it takes 5 seconds to
> finish that query. In the same session, I executed the same query
> again and again, it only took 2 seconds to complete. I donot know why
> the first execution of a query (with external procedure call) takes
> longer time. It seems Oracle takes some time to load the external
> procedure service in Acer server. Again the strange thing, there is
> not such issue in Compaq Server, no matter when I execute the same
> query, it always take 2 seconds.
>
> Could any one tell me why Oracle on Acer Server has slow response in
> certain situations (e.g Logon , and run first query involve external
> procedure). And any solution to solve the problem?
>
> Thanks in advance.
>
> John

If you're running a client app (e.g. SQL*Plus) directly on the Oracle server machine, you should make sure ORACLE_SID is set in the environment and TWO_TASK is unset. Then when you connect, just use "username/password" (i.e. leave out the "@servicename" part). This way the client will use BEQ instead of TCP. BEQ (bequeath) is a sort of IPC (inter-process communication) and will not go through SQLNet at all.

Regarding why the Acer server took 5 seconds to execute the query the first time, my guess is that the DLL for the external procedure wasn't loaded into memory yet, so it took extra time to load the DLL and then execute the query. The Compaq server probably has some other program which already loaded the DLL into memory. A single copy of a DLL in memory is shared among different programs so once a program loads it, it can be used by all programs that need it.

Hope that helps.

Cheers,
Dave Received on Sat Apr 12 2003 - 17:32:52 CDT