Re: "sql*net message from client" hang

2010-08-09 Thread Michael Ludwig
Dan schrieb am 09.08.2010 um 18:04 (-0400): > Hello, > I just wanted to provide some closure on this "issue", we found out > that there was a PIX firewall between the Perl app server and the > Oracle database, and once we removed this, the problem did go away. Good to see the culprit revealed (a

Re: "sql*net message from client" hang

2010-08-09 Thread Dan
;ll aim to fill our row cache with around 10 per go. */ > > >> /* Using 10 means any 'runt' packets will have less impact. */ > > >> > > >> > > >> int txfr_size = 10 * 1460; /* desired transfer/cache size */ > > >> > > >> > > >

RE: "sql*net message from client" hang

2010-07-12 Thread John Scoles
and or type of the constant my throw the bug as well. Might just be one of those majic munbers that pad the results just enough to make the query run fine. Hope this helps a little John Scoles > Date: Fri, 9 Jul 2010 17:47:24 -0400 > Subject: Re: "sql*net message from client&qu

Re: "sql*net message from client" hang

2010-07-09 Thread Dan
txfr_size / est_width; /* (maybe 1 or 0) */ >> >> >> >> /* To ensure good performance with large rows (near or larger */ >> /* than our target transfer size) we set a minimum cache size. */ >> >> >> if (cache_rows < 6) /* is cache a

Re: "sql*net message from client" hang

2010-07-09 Thread Dan
= (cache_rows > 0) ? 6 : 4; >} > if (cache_rows > 32767) /* keep within Oracle's limits */ > cache_rows = 32767; > > > > > > so the above might be buggering you up if your packet size is no longer > 1460? > > > > This might be it. > >

RE: "sql*net message from client" hang

2010-07-09 Thread John Scoles
} if (cache_rows > 32767) /* keep within Oracle's limits */ cache_rows = 32767; so the above might be buggering you up if your packet size is no longer 1460? This might be it. Cheers John Scoles > Date: Fri, 9 Jul 2010 10:15:03 -0400 > Subject: Re: "sql*net messa

Re: "sql*net message from client" hang

2010-07-09 Thread Dan
> > >>> > Cheers >>> > >>> > Martin >>> > >>> > >>> > On 08/07/2010 17:07, Howard, Chris wrote: >>> > >>> > If it always stops at the same place, it makes me think >>> > of a resource prob

Re: "sql*net message from client" hang

2010-07-08 Thread John Scoles
lways stops at the same place, it makes me think >> > of a resource problem, something like a quota? >> > >> > I don't remember of there are select quotas. >> > >> > Does it do the same if run as sysdba or some other >> > well-endowed database

Re: "sql*net message from client" hang

2010-07-08 Thread John Scoles
t; > > I don't remember of there are select quotas. > > > > Does it do the same if run as sysdba or some other > > well-endowed database user? > > > > > > > > > > > > -Original Message- > > From: Dan [mailto:dkele...@gmail.com ] > > Sent

Re: "sql*net message from client" hang

2010-07-08 Thread Dan
hing like a quota? > > I don't remember of there are select quotas. > > Does it do the same if run as sysdba or some other > well-endowed database user? > > > > > > -Original Message- > From: Dan [mailto:dkele...@gmail.com ] > Sent: Thursday, July 08

Re: "sql*net message from client" hang

2010-07-08 Thread Martin Hall
l.com] Sent: Thursday, July 08, 2010 10:02 AM To: dbi-users@perl.org Subject: "sql*net message from client" hang Hello, I have some code that has been running happily for many years, but suddenly started hanging on a simple select query to our Oracle DB. The DB shows it as an inactive sessio

RE: "sql*net message from client" hang

2010-07-08 Thread Howard, Chris
ailto:dkele...@gmail.com] > Sent: Thursday, July 08, 2010 10:02 AM > To: dbi-users@perl.org > Subject: "sql*net message from client" hang > > Hello, > I have some code that has been running happily for many years, but > suddenly started hanging on a simple select query t

"sql*net message from client" hang

2010-07-08 Thread Dan
Hello, I have some code that has been running happily for many years, but suddenly started hanging on a simple select query to our Oracle DB. The DB shows it as an inactive session with "SQL*NET message from client", so the DB thinks it is waiting for the perl script, but the perl script is hung