Problem :: We were facing issue in one of our Process App where we cannot migrate any instances from older version and also not getting any error in SystemOut logs. We have tried everything and finally raised PMR to IBM. PMR went on for few months and finally we got the problem.
Issue: This is happening if you are creating new instances of ProcessApp using REST-API. in IBM BPM Process Server environment, we should not have any instance in LSW_BPD_INSTANCE table with value TIP='T' as there are not TIP version in Process Server Environment.
Though if you are creating new instance using REST-API on Default snapshot that instance will have value TIP='T' in LSW_BPD_INSTACE table, which is defect.
When we migrate instances to one snapshot to another, IBM BPM ignore all the instances having TIP='T' and thus these instances are not getting migrated.
SOLUTION: there are two things we can do.
1.) Change value for all instances from 'T' to 'F' in TIP column of LSW_BPD_INSTACES. This will let us migrate all older instances which we were not able to migrate earlier.
2.) there is an I-Fix which we should install to fix this problem for future instances.
Below are the detail for Permanent fix using IFIX.
http://www-01.ibm.com/support/docview.wss?uid=swg1JR44597
Issue: This is happening if you are creating new instances of ProcessApp using REST-API. in IBM BPM Process Server environment, we should not have any instance in LSW_BPD_INSTANCE table with value TIP='T' as there are not TIP version in Process Server Environment.
Though if you are creating new instance using REST-API on Default snapshot that instance will have value TIP='T' in LSW_BPD_INSTACE table, which is defect.
When we migrate instances to one snapshot to another, IBM BPM ignore all the instances having TIP='T' and thus these instances are not getting migrated.
SOLUTION: there are two things we can do.
1.) Change value for all instances from 'T' to 'F' in TIP column of LSW_BPD_INSTACES. This will let us migrate all older instances which we were not able to migrate earlier.
2.) there is an I-Fix which we should install to fix this problem for future instances.
Below are the detail for Permanent fix using IFIX.
http://www-01.ibm.com/support/docview.wss?uid=swg1JR44597