I believe Martin was referring to the Oracle trace files. These will be on your database server. Check with your DBA if you're not sure where they live.
Steve On Tue, 2008-10-28 at 10:32 -0400, Carl Furst wrote: > Thanks for the reply! I appreciate the help. I don't suppose you would know > where either: > > a) Apache has configuration for where to dump trace files > b) where I would, in general, find trace files for Apache. > c) Is there a gdb or other tool that would help be examine them. > > Thanks Again, > Carl. > > On Tue, Oct 28, 2008 at 10:19 AM, Martin Hall <[EMAIL PROTECTED]>wrote: > > > Didn't see a reply to this one.... > > > > You're right. 3113 and 3114 are usually as a result of the server > > process crashing. You may have some useful information in the trace files. > > There's a lot of potential causes for this error, so useless to speculate > > on causes until you can get something more concrete out of the traces. > > > > Cheers > > > > Martin > > > > > > Old Orange Juice wrote: > > > >> Hey all, > >> > >> I'm really at the end of my rope with this one problem I'm having. I > >> need some clues. I've looked everywhere where I know to look but I > >> need some suggestions on where else to look. > >> > >> My company has a web based cms systems written in OOD PERL running > >> under Apache 2.2 Oracle client 9.0.2 and mod_perl 2. When we start our > >> test servers, all is fine, however after about oh 50 or so requests, > >> we find our server comming back from all requests with 3113 and 3114 > >> oracle errors, end of file and not connected to Oracle.. At this point > >> all subsequent requests come back with the same error. > >> > >> It's as if the Oracle server accepts connections from our test server > >> and thus shuts down all connections from our test and our QA servers. > >> However, our production servers which runs using the same httpd > >> binary, the same configs, the same DBI install and the same oracle > >> client install. I'm totally stumped. > >> > >> Thanks, > >> Ooj > >> > >> > >> > > > > > > ****************************************************************** This email is intended solely for the use of the addressee and may contain information that is confidential, proprietary, or both. If you receive this email in error please immediately notify the sender and delete the email. ******************************************************************
