QAD BI v3 – Tech Level 2 Certification - Part 2 > Troubleshooting Tools > DWD for Troubleshooting – Rerunning Jobs
  PPT
DWD for Troubleshooting – Rerunning Jobs
 
When troubleshooting on a multi-source system, sometimes the source system data being investigated is not in the stage tables because another source system ran after the one being investigated in the daily run.
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
 
The UPGRADE_ STEP2_XXXXXXX jobs are used by the upgrade job to generate source specific upgrade jobs. An earlier step in the UPGRADE process, converts the XXXXXX of the UPGRADE STEP2_XXXXXXXX job to another source name for each appropriate source. It also does the same with the SET_CONNECTION_XXXXXXX task name inside the upgrade job.
DWD for Troubleshooting – Rerunning Jobs
 
Right click on the UPGRADE_ STEP2_XXXXXXX job and choose Insert Copy of Job.
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
 
We add the set_job_chaining_enabled_to_no task to the beginning of the job because we don’t want the jobs that are being run as tasks here to launch other chained jobs via the parameter list. Everything inside this custom job will just run in sequence. Make sure too that the order number is in sequence, i.e. don’t have jobs with the same number otherwise they could both try to run at the same time.
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning jobs
DWD for Troubleshooting – Rerunning Jobs
 
If a straight forward DAILY_PERM_EXTRACT and DAILY_PROCESS is desired, remove the setp_job_process_running_type_to_hist task from the list. This task flags the jobs to know they are running in historical mode which we wouldn’t want for daily. The daily parameter setting was flagged in the second task and would still apply at this portion of the staging tables.
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
DWD for Troubleshooting – Rerunning Jobs
 
There are various fact tables in the job.
DWD for Troubleshooting – Rerunning Jobs
 
The fact_om_shipment and shipment stage tables have been removed. Other fact_ tables have been removed and only fact_om_invoice remains. That leaves lots of unnecessary stage tables for other fact tables that are not in the scheduler any more, but ensures that proper stage tables do get populated. This is a quick way to build a custom job without trying to figure out which stage tables are safe to remove and which are not.
DWD for Troubleshooting – Rerunning Jobs