Scsm Data Warehouse Jobs Not Started
� the data warehouse is just dead. root cause � the dwmaintenance job has a stalled process. it�s a statusid of 7 (waiting) instead of 3 (not started). unless you reset this status, the data warehouse jobs won�t run and your report data is stale.. 4. wait for the mpsyncjob job to run, which will import the management pack to the data warehouse management group. to check the job schedule, just use this powershell one-liner, which will tell you schedule, start date and time, and the next run date and time.. This post will aid in troubleshooting the following issues concerning the service manager data warehouse: � slow execution of etl jobs � etl jobs failing to complete.
Within the data warehouse jobs on the data warehouse pane there should be 5 jobs. i had a similar issue where the other jobs would not kick in. i restart the 3 system center services on the data warehouse and ensured that the datawarehous registration had completed.. With a user base of up to 7000 users the script should not take longer then roughly 45 minutes to complete including running the cube jobs. when this has occurred for me and i have verified there are no locks i usually reboot the data warehouse management server and the dw database, if you can, then rerun the scripts.. The data warehouse is just dead. in some cases the root cause of these issues is dwmaintenance job that has a stalled process. it�s a statusid of 7 (waiting) instead of 3 (not started). you need to reset this status to get the data warehouse jobs running again..
Comments
Post a Comment