Troubleshooting Batch Reports


Published on

Overview of Troubleshooting Guide.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Troubleshooting Batch Reports

  1. 1. Troubleshooting Batch Reports To efficiently resolve problems
  2. 2. Introduction <ul><li>To Identify and Resolve problems with Batch Reports. </li></ul><ul><li>Kai Leung Liu, Sr. Oracle Architect Consultant, Kaitech, Inc. </li></ul>
  3. 3. Topics of Discussion <ul><li>What is a Trouble Report? </li></ul><ul><li>What to look at to Identify a Trouble Report? </li></ul><ul><li>How to troubleshoot your problem report? </li></ul><ul><li>What to look at in the backend to troubleshoot report? </li></ul><ul><li>Current Issues of Trouble Reports </li></ul>
  4. 4. Batch Reporting
  5. 5. What is a Trouble Report? <ul><li>When Queue Manager show terminated or hung report. </li></ul><ul><li>Explain how all the individual pieces fit together </li></ul>Spooler Unix Log Email RW Server Log Weblog DBA Queue Mgr CMN_LOG
  6. 6. What to look at to Identify a Trouble Report? <ul><li>The Queue Manager and User is our window to Reports status and progress. </li></ul><ul><li>The Spooler to see if you can find the Finished report. </li></ul><ul><li>The Email check to see if we received, we can check server to see if it exists. </li></ul><ul><li>Check the Weblog for the specific Report Server form the Application Server. </li></ul>
  7. 7. What to look at to Identify a Trouble Report? Continue. <ul><li>Check CMN_LOG see if there a clue of what else could have gone wrong. </li></ul><ul><li>Check the Unix logs to look for clues /utmp/repserver.log, /utmp/processserv.log and /tmp/dmsp.log. </li></ul><ul><li>Check RW_SERVER_JOB_QUEUE to see status of Reports from the Server. </li></ul><ul><li>Check DBA to see if database activities could have effected the reports. </li></ul>
  8. 8. How to troubleshoot your problem report? <ul><li>Use Queue Manager to determine status like terminated, hung, and etc. </li></ul><ul><li>Check Weblog to determine why the Report terminated. </li></ul><ul><li>Check CMN_LOG to see if processes or report log errors. </li></ul><ul><li>Check Unix Log to see if job ran under on server. </li></ul><ul><li>Check to see if it’s been Spooled with Easy Spooler and you can check /tmp/dmsp.log. </li></ul>
  9. 9. How to troubleshoot you problem report? Continue. <ul><li>Once job has been corrected. You need to restart report. Reports does not re-run within the same day. </li></ul><ul><li>The Report Server Table which is called RW_QUEUE_JOB_QUEUE need to remove specific job to re-run a terminated job. </li></ul><ul><li>Use Queue Manager to reset the terminated and hung job to re-run again. Simply modify something and save changes. It can not reset a current running job. </li></ul>
  10. 10. What to look at in the backend to troubleshoot report? <ul><li>The backend has the logs to check and files to help determine what has happened. </li></ul><ul><ul><ul><li>/utmp/repserver.log – Logs all report jobs submitted. </li></ul></ul></ul><ul><ul><ul><li>/utmp/processserv.log – Logs all procedures jobs submitted. </li></ul></ul></ul><ul><ul><ul><li>/tmp/dmsp.log – Logs all entries and status of easyspooler submission. </li></ul></ul></ul><ul><li>Check Email and spooled files. </li></ul><ul><ul><ul><li>/var/spool/dms/<instance> -- Report repository before goes to spooler. </li></ul></ul></ul><ul><ul><ul><li>/var/spool/elink/<instance> -- Email repository for 1 week. </li></ul></ul></ul>
  11. 11. Current Issues of TroubleShooting Reports <ul><li>Invalid Emails on Batch Report will cause Terminated reports. </li></ul><ul><li>Batch reports being reschedule before being submitted to Spooler. </li></ul><ul><li>Batch reports being reschedule during the spooling of Batch reports. </li></ul>
  12. 12. Summary <ul><li>How to Identify a Trouble report and ways to resolve and determine the problem. </li></ul><ul><li>**What to check if a report doesn’t run? </li></ul><ul><li>Do analysis first don’t go to DBA unless you see database errors? </li></ul><ul><li>1-900-KAITECH </li></ul>
  13. 13. Q & A <ul><li>Review doc Troubleshooting Guide for Reporting. </li></ul><ul><li>Answer Questions? </li></ul><ul><li>Next Week is a break and Lecture TBD. </li></ul>