Changing Stepper Names

Problem

It's possible to change the name of a Stepper. This is expected and completely normal. But in a DEV environment, existing stepper instances will still refer to the old stepper name. This should never be an issue in PROD, since one wouldn't remove steppers that were being used. It's not blocking in DEV or PROD, since new stepper instances can run with no problem. But it can result in WARNINGS being logged similar to this:

com.semarchy.mdm.dataui.domain.appmodel.MetadataObjectNotFoundException: 
Cannot find metadata DirectAuthoringDefinition for name ProductFamilys

Solution

You can find Stepper Instances that are provoking this error with a query like this:

SELECT 
   si.id        stepper_instance_id
  ,si.app_name  
  ,il.creator
  ,il.classname
  ,il.status
  ,il.stepper_name
FROM      mta_stepper_instance si
left outer join mta_integ_load il on ( il.loadid::text = si.load_id ) /* modify this PostgreSQL syntax slightly for Oracle. */
where dloc_name = 'My Data Location' ;

You can fix Stepper Instances with a simple update statement:

update mta_integ_load set stepper_name = 'ProductFamilies' where stepper_name = 'ProductFamilys';