no:CC-0046 problem

hi, i ran consistencychecker job and under workflow header there are over 150 "Warning CC-0046"s.it is shortly like that:a workflow object references to an nonexistent package.as a solution emc says:set component_id and chronicle_id of the package to 16 zeros and destroy package.but then it gives an example, in that example they do not destroy the package, they set componentid and chronicle id of the package to 16 zeros.this is ok because this is what they say.but after this, the example saves the package.this is inconsistent.shall i destroy the package or save?emc's solution is below:

--- QUERY---: select ws.r_object_id as p1, pr.r_component_id as p2 from dm_workflow_s ws, dm_workflow_r wr, dmi_package_s ps, dmi_package_r pr where ws.r_object_id = wr.r_object_id AND wr.r_act_state != 2 AND pr.r_component_id > '0000000000000000' AND ws.r_runtime_state IN (1,3) AND ws.r_object_id = ps.r_workflow_id AND wr.r_act_seqno = ps.r_act_seqno AND ps.r_object_id = pr.r_object_id AND not exists (select a.r_object_id from dm_sysobject_s a where a.r_object_id = pr.r_component_id)

WARNING CC-0046: dm_workflow object with r_object_id '4d006e7880002501' references non-existent sysobject with r_component_id '09006e788000dffd'

WARNING CC-0046: dm_workflow object with r_object_id '4d006e7880000d09' references non-existent sysobject with r_component_id '09006e7880006e60'

Problem:

The r_component_id of the dmi_package and is making reference to a workflow instance doesn't exist anymore

Steps:

- Set the r_component_id and r_component_chron_id (Chronicle ID of the object identified at the corresponding index position in r_component_id.) to 16 zeros and destroy it.

- Or set r_component_id to a existing package with his chronicle_id in r_component_chron_id

API> retrieve,c,dmi_package where r_workflow_id='4d006e7880002501'

...

4d0a636280000900

API> set,c,490a636280000900,r_component_id

Set >0000000000000000

...

API> set,c,490a636280000900,r_component_chron_id

Set >0000000000000000

...

API> save,c,490a636280000900

...

API> set,c,490a636280000900,r_component_id

Set >090a636280004c85

...

API> set,c,490a636280000900,r_component_chron_id

Set >090a636280004655

...

API> save,c,490a636280000900

...

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

Julien.Fontaine

Try with one fist and turn again your consistency checker.

All comments

ihsankocak

i tried to destroy the packages but it gives an exception like "package does not exist".So how can i destroy a nonexistent pacakge.this solution is not correct.

Julien.Fontaine

I don't understand your trouble. Why you didn't destroy workflow object because they references non existent package ?

ihsankocak

thank you for your reply.i did not destroy the workitems because it says:" Set the r_component_id and r_component_chron_id (Chronicle ID of the object identified at the corresponding index position in r_component_id.) to 16 zeros and destroy it". i understand this as destroying package.you say it mentions about destroying workflows?

Julien.Fontaine

For example, you have :

dm_workflow object with r_object_id '4d006e7880002501' references non-existent sysobject with r_component_id '09006e788000dffd'

In this case, the r_component_id doesn't exist anymore, are you ok ?

The n you change the r_component_id to 16 zero and you destroy you're dm_workflow object !

ihsankocak

but dm_workflow does not have r_component_id.r_component_id belongs to dmi_package.i can not set 16 zeros to r_component_id because the package does not exist.

Julien.Fontaine

Ok, and if you delete your dm_workflow ?

ihsankocak

isn't it a riscy action?won't be some side-effects if i delete problemmed workflows?

Julien.Fontaine

Try with one fist and turn again your consistency checker.

ihsankocak

yes there is not any problem with destroying problemmed workflows.thank you.