Message-ID: <10453508.1075852359566.JavaMail.evans@thyme> Date: Mon, 22 Oct 2001 14:28:33 -0700 (PDT) From: d.alexander@enron.com To: d.alexander@enron.com, justin.o'malley@enron.com, chris.gaskill@enron.com, jay.reitmeyer@enron.com, sheila.chang@enron.com, adam.bayer@enron.com, aaron.berutti@enron.com, milen.kurdov@enron.com Subject: Slower Reporting Runtimes Cc: david.dronet@enron.com, yan.wang@enron.com, rishi.mehta@enron.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Bcc: david.dronet@enron.com, yan.wang@enron.com, rishi.mehta@enron.com X-From: Alexander, Kim D X-To: Alexander, Kim D , O'Malley, Justin , Gaskill, Chris , Reitmeyer, Jay , Chang, Sheila , Bayer, Adam , Berutti, Aaron , Kurdov, Milen X-cc: Dronet, David , Wang, Yan , Mehta, Rishi X-bcc: X-Folder: \JREITME (Non-Privileged)\Deleted Items X-Origin: REITMEYER-J X-FileName: JREITME (Non-Privileged).pst Hi All, We've been looking into determining why certain reports are taking longer to run than usual. After examining the log, it seems that, either by fact or coincidence, the longer runtimes began to occur after our migration to the new database server -- no code had been changed. Although there are other possible causes to investigate, we can start by rebooting our machines to ensure there aren't any issues caused by low memory on the machines running reporting jobs as scheduled tasks. We will continue to look into the possible cause of the bottle neck, and will seek to have it resolved this week. However in the meantime please reboot your machine if it is running scheduled reporting jobs. Thanks, Kim