nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Found a bad objects dmi_workitem & dmi_package

gostishev_d

Hi!

I have a problem.

I found dmi_workitem & dmi_package objects in repository with no references.

The query

select count(*) from dmi_workitem where r_queue_item_id not in (select stamp from dmi_queue_item where delete_flag<>0)

returns result>0

Also, query

select count(*) from dmi_package where r_workflow_id in

(select r_workflow_id from dmi_workitem where r_queue_item_id not in (select stamp from dmi_queue_item where delete_flag<>0))

returns result>0

What does mean?

Can i delete this objects from database?

Thanks.

Find more posts tagged with

Comments

gostishev_d

Does not anyone encountered this problem?

DavidHaveman

Do they have connections to any active workflows? if a workitem doesn't go to a queue it won't have a queue item. do a query like

select * from dmi_workitem where r_workflow_id in (select r_object_id from dm_workflow ) and ( your original filter )

The same can be done for dmi_queue_item's using the "router_id" against the "r_object_id" of dm_workflow...

Good luck.

gostishev_d

I found dmi_workitem & dmi_package that are connected with active workflows.

But they have no links with dmi_queue_item objects.

I also found dmi_workitem & dmi_package that are connected with finished, aborted and terminated workflows.

What can I do with these objects in both cases?

They slow down the processing of query

DavidHaveman

What is the state of the active workflows? can they be restarted or resumed? That would be the cleanest option because that would allow them to finish their process. Does the dm_process object ( the object that defines the template for the workflow ) specify that these workflows should go to a queue or are they only automatic activities?

Look into the doucumentum jobs that come with the install, i believe the dm_Clean or dm_ConsistancyChecker jobs should be able to help you out and clear out those workflows. I'm hessitent to say "just use some dql queries" to delete them, because there could still be a reason that hasn't made itself apparent yet why those objects are still around. Also, DQL won't allow you to delete dmi_workitem entries. Look very closely at those processes before you delete those objects.

What is the full query and how many of these orphaned objects are still around? Documentum a is very powerful system and can handle a massive amount of load.

gostishev_d

Thanks for the reply

Find all workflows grouped by state:

select r_runtime_state, count(*) from dm_workflow group by r_runtime_state
result:
r_runtime_state count(*)
--------------- ----------------------
1 52081
4 92
(2 rows affected)

Find all dmi_workitem objects not associated with an dmi_queue_item grouped by state of workflows:

select wf.r_runtime_state, count(wi.r_object_id) from dmi_workitem wi, dm_workflow wf
    where wi.r_workflow_id=wf.r_object_id
    and wi.r_queue_item_id not in (select stamp from dmi_queue_item where delete_flag<>0)
    group by wf.r_runtime_state
result:
r_runtime_state count(wi.r_object_id)
--------------- ----------------------
              1                  113283
              4                     354
(2 rows affected)

I hope to have built queries correctly

dm_DMClean runs every night but these objects are not removed...

And more, tell me how to relate an dmi_workitem with the dmi_package? On r_workflow_id???

Thank you for your attention!

DavidHaveman

Those counts don't look bad, the results only make up a very small percentage of workflows in your system.

select dmi_workitem.r_workflow_id, dmi_workitem.r_object_id as workitem_id, dmi_package.r_object_id as package_id from dmi_workitem, dmi_package where dmi_workitem.r_workflow_id = dmi_package.r_workflow_id and dmi_package.r_act_seqno = dmi_workitem.r_act_seqno

This brings back listing connecting dmi_workitems and dmi_packages. the Green filter connects the workitems and packages by the r_workflow_id, and the blue filter pairs only the correct packages with the workitems they are connected to by the r_act_seqno. dmi_package entries get recreated for each new dmi_workitem entry in a workflow process.