Removing Orphan WorkUnits

 2 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
msjmg111
Veteran Member
Posts: 74
Veteran Member
    We had an issue with a workflow table (WFACTVAR) that had grown very large and took hours to reorg. As a short cut, the dba issued a sql command that deleted everyting in that file. Now I have workunits in other tables (i.e. WFACTIVITY) and processflow doesn't know they exist. I would like to clean up the orphan records and put in the move/purge history script provided by Lawson. We only have about a half dozen processflows but more are on the way and I would like to get this under control. From your perspective, is using a sql script to delete my orphan records the way to go? Besides workunits is there any other records I should look into? For example, if I find and delete all workunits = 10, is there another table that may hold info pretaining to workunit 10? I'm just getting my feet wet on processflow, so I appreciate any assistance.
    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
      It's never a good idea to delete records via a SQL command - you end up creating more problems for yourself.
      Did you run the Move WorkUnits To History job? That should have handled this for you and then you could run the Purge WorkUnits job for records you don't need to retain.
      David Williams
      msjmg111
      Veteran Member
      Posts: 74
      Veteran Member
        Thanks for the reply. Unfortunately the records in WFACTVAR were deleted and now I've got the mess to deal with. I ran the script to move the records to history but it only took the ones created after the delete. I guess at this point I have no choice but to have the dba remove the workunits in WFACTIVITY.