I reinstalled my DW where the SM management server is running with UR9. I followed this instruction till the first red paragraph. Before I go ahead I want to make things clear:
- I have to disable job shedule via Get-SCDWJob | foreach-object { Disable-SCDWJobSchedule -JobName $_.Name }
- re-register SCSM to the DW
- Start MPSyncJob if it is not already running via Start-SCDWJob -jobname 'MPSyncJob'
- add group for Report Users under Data Warehouse - Security - User Roles
- wait for an hour, if jobs like EXTRACT are running, then execute command from (1.) BTW I don't understand why to disable all jobs again, because I think MPSyncJob should run. Or should I exclude MPSyncJob from disabling?
- Install UR9
- Run the disable job schedules command again (exclude MPSyncJob?) And why disbale and not enable or rather start jobs in certain order? With respect to 2. This was the output before I register SM to DW:
BatchId Name Status CategoryName StartTime EndTime IsEnabled
------- ---- ------ ------------ --------- ------- ---------
80 DWMaintenance Not Started Maintenance True
83 Extract_DW_SCSM_ Running Extract 10.09.2021 03:20:00 False
Test2016
76 MPSyncJob Running Synchronization 10.09.2021 03:16:00 True
After register the output of get-scdwjob does not change (I wait more then 24h). It seems the MPSyncJob stucks because there was no progress, see also the img below.
Then I decided to troubleshot the stucked job as described here but since hours no progress as well. The MP syncronization progress in the console is the same as you can see in picture above, aslo the start time does not change.
BatchId Name Status CategoryName StartTime EndTime IsEnabled
------- ---- ------ ------------ --------- ------- ---------
80 DWMaintenance Not Started Maintenance True
133 Extract_DW_SCSM_ Not Started Extract False
Test2016
134 MPSyncJob Running Synchronization 13.09.2021 02:52:00 True