Page Comparison

...

1. Check the Latest Loads section to see if you have any Load jobs with RUNNING status. You might think you don't have jobs running, but if you grabbed some load IDs from xDM and then did not submit those jobs or did not cancel, then you have "running" loads even if you are not actively loading data into them using SSIS/ODI/ETL. 

   xDM is telling you that since these loads are still open, you better cancel them in case you change the model out from under somebody who is trying to load data, assuming the old model is in place.

   1. How to do it? 
   2. Data Location logs
      Keep drilling until you see Latest Loads.
   3. 
2. Call the SEMARCHY_REPOSITORY.INTEGRATION_LOAD.CANCEL_LOAD procedure to cancel these RUNNING jobs. You cannot cancel the jobs from the workbench.
3. If you still see Load jobs that are running, it's because older loads are no longer showing up on the latest loads list. How can you see them? 
   1. You will have to query the repository.

      
      

      Code Block
      select loadid from semarchy_repo.mta_integ_load where status = 'RUNNING' and classname='IntegrationLoad';

      
      

   2. Grab those load IDs and cancel them.

   3. Here's a nice cheat/tip from Mike L. 

      Code Block
      select loadid, creator, 'exec SEMARCHY_REPOSITORY.INTEGRATION_LOAD.CANCEL_LOAD(' || loadid || ', ''' || creator || ''');' from SEMARCHY_REPOSITORY.mta_integ_load where status = 'RUNNING' and classname='IntegrationLoad' order by 1;

Cleaning up Integration Batches

An analogous issue is to have an open integration batch preventing model deployment.

1. Find suspended jobs:
   select * from MTA_INTEG_BATCH where STATUS = 'SUSPENDED' ;
2. Force their status to 'WARNING' (indicating that it completed) so that models can be deployed:
   update MTA_INTEG_BATCH set STATUS = 'WARNING' where STATUS = 'SUSPENDED' ;