Problems with the application are often the DBA's problem since a poorly designed/written/implemented application can impact the entire database work load. This in turn makes it the DBA's problem. A DBA needs to point out bad practice or code where he or she sees it to protect the database as much as possible. Sometimes no "fix" is going to be forthcoming. Sometimes you might get one down the road. And once or twice in your lifetime you might even get a immediate positive response. Maybe, but I agree with Niall, you need to take responsibility for trying to make things better. -- Mark D Powell -- Phone (313) 592-5148 ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Niall Litchfield Sent: Tuesday, January 09, 2007 1:55 PM To: Kerber, Andrew Cc: dd.yakkali@xxxxxxxxx; oracle-l@xxxxxxxxxxxxx Subject: Re: SQL *Net more data from client - waiting too long On 1/9/07, Kerber, Andrew <Andrew.Kerber@xxxxxxx> wrote: It also means its not a problem w/ Oracle, it's a problem with the application. Absolutely not picking on Andrew here, since this and some of the implications are a common view, but am I the only one to think that the distinction is somewhat false. Technically a bad app is not my problem as a DBA, but professionally and in reality I view it as my problem to diagnose, report and offer solution with applications. In other words I see application level design and performance problems as part of my purview. What do others think? -- Niall Litchfield Oracle DBA http://www.orawin.info