Are you certain the connection isn't going thru the listener? Check
tnsnames.ora and verify that PROTOCOL=BEQ.
[EMAIL PROTECTED] wrote:
A developer/analyst was running 4 reports on our datawarehouse, connecting
locally using SQL Plus from a telnet session on the Unix box. He then
started
A developer/analyst was running 4 reports on our datawarehouse, connecting
locally using SQL Plus from a telnet session on the Unix box. He then
started 4 queries, spooling the output to the unix server (again, local).
He was curious as to why the sessions were both taking so long and why they
:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 1:10 AM
To: Multiple recipients of list ORACLE-L
Subject: Re: SQL*Net Connection under-performing
Vivek
I had similar issues with a large customer. I solved this by setting
up pre-spawned dedicated processes
-Original Message-
From: Ferenc Mantfeld [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 1:10 AM
To: Multiple recipients of list ORACLE-L
Subject: Re: SQL*Net Connection under-performing
Vivek
I had similar issues with a large customer. I solved
[mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 04, 2003 1:10 AM
To: Multiple recipients of list ORACLE-L
Subject: Re: SQL*Net Connection under-performing
Vivek
I had similar issues with a large customer. I solved this by setting
up pre-spawned dedicated processes
:
Sent by:Subject: RE: SQL*Net Connection
under-performing
[EMAIL PROTECTED
04, 2003 1:10 AMTo: Multiple recipients of list
ORACLE-LSubject: Re: SQL*Net Connection
under-performing
Vivek
I had similar issues with a large
customer. I solved this by setting up pre-spawned dedicated processes in the
listener. Full in structionsavailable on Metalink. I
recipients of list ORACLE-L
Subject: Re: SQL*Net Connection under-performing
Vivek
I had similar issues with a large customer. I solved this by setting
up pre-spawned dedicated processes in the listener. Full in structions
available on Metalink. I brought down 1 minute login times to under 10
seconds
Title: Details about Tar logged
SITUATION - WithDBServerCPU Idle being 0 %
load average 60-70 % :-
tnsping Connect toone of the Databases (1)takes about
10,000 ms
truss
-fdD tnsping connect string
29504: 20.0006 18.8113 read(3, "\0 K\0\004\0\0\0 "\0\0
?".., 2064) = 75
Thus
18
What does tnsping from other machines to the slow database, database 1,
return? Is this a problem only from this one machine or from many
machines?
I would wager that the problem is that database 1 2 are being
resolved through different paths at the TNS level. Perhaps one is
using a local
MantfeldDreaming costs you nothing. Not dreaming costs you
everything.
- Original Message -
From:
VIVEK_SHARMA
To: Multiple recipients of list ORACLE-L
Sent: Monday, February 03, 2003 6:58
PM
Subject: SQL*Net Connection
under-performing
SITUATION - WithDBServerCPU Idle being
Is there any possible way to retain/reinstate/continue a SQLNet connection
if there is say a 10-second network outage?
For example: If a session is established and then the network cable is
unplugged for 5 seconds and then replaced. Is there anyway to keep that
connection alive?
Michael
If using TCP/IP, you don't have to do anything. 10 seconds is short
enough time for the connection to still be alive.
--
Lyndon Tiu
Quoting Bond Mike A Contr OC-ALC/LPRC [EMAIL PROTECTED]:
Is there any possible way to retain/reinstate/continue a SQLNet
connection
if there is say a
If you are using TCP/IP, then yes. It's highly dependent on your OS
TCP/IP stack though. I tried it with Linux and it seems fine.
--
Lyndon Tiu
Quoting Bond Mike A Contr OC-ALC/LPRC [EMAIL PROTECTED]:
Is there any possible way to retain/reinstate/continue a SQLNet
connection
if there is
Mike,
Sorry there is no way to keep the connection alive. It's a TCP/IP thing. I
wish you could do that too.
Dick Goulet.
Bond Mike A Contr OC-ALC/LPRC [EMAIL PROTECTED] wrote on 1/28/03 1:14
pm:
Is there any possible way to retain/reinstate/continue a SQLNet connection if
there is say a
Quoting [EMAIL PROTECTED]:
Mike,
Sorry there is no way to keep the connection alive. It's a
TCP/IP thing. I
wish you could do that too.
Dick Goulet.
Bond Mike A Contr OC-ALC/LPRC [EMAIL PROTECTED] wrote on
1/28/03 1:14
pm:
Is there any possible way to retain/reinstate/continue
B Is there any possible way to retain/reinstate/continue a SQLNet connection
B if there is say a 10-second network outage?
B For example: If a session is established and then the network cable is
B unplugged for 5 seconds and then replaced. Is there anyway to keep that
B connection alive?
, January 28, 2003 4:14 PM
To: Multiple recipients of list ORACLE-L
Subject: SQL Net connection.
Is there any possible way to retain/reinstate/continue a
SQLNet connection
if there is say a 10-second network outage?
For example: If a session is established and then the network cable
hi gurus,
Does SQL*net has a limit on concurrent simulataneous access/connection to the the
database. I simulated 600 web user accesing the oracle DB thru a PHP script which
connects to the data base,fetches the data, and disconnects. From the listener.log,
connections is about 7/8
Hi
I
have an NT server which successfully does a SQL Net connection to various
databases on other boxes.
It
can ping database X by ip address, but can't do a SQL Net connection (by ip
address) to it.
I
have another box with the same default gateway, subnet mask
20 matches
Mail list logo
