While stress testing a batch report created using a Java Servlet against 8.1.5 on Solaris 2.6, initially a large report was taking 1 hour and 20 minutes. After performing a trace on the application, I discovered that no database activity was occurring at all, which was also evident by the cpu being idle. After a quick/dirty redesign of the application, the report now runs in 9 minutes or less, however, if one report is run and it takes 9 minutes...the exact same report can be kicked off minutes later and is still running after 27 minutes. We stopped and restarted JRUN, had no effect and then bounced the database and the report took 6 minutes. Any ideas on what might causing this and what I might be able to check? TIA, Rich -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Richard Huntley INET: [EMAIL PROTECTED] Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
