dm_policy installation problem using DAR in Documentum 6.5 SP2

Hi there,

In my docbase I have a lifecycle (dm_policy) installed. In that dm_policy I want to add more object types, so that this lifecycle can be associated with new objects.

For doing this I have imported the existing documentum lifecycle into my Documentum Composer project and added the required types. After that I generated the DAR file and installed the same into the same docbase. During DAR creation I selected the existing object override installation option.

After installation of the DAR file I am able to see two instances of the same lifecycle, instead of a single modified lifecycle.

Are we doing in mistake? Is there any otherway that we should be using for modifying an existing lifecycle? We are facing this problem for the last few weeks and we are stuck on this. Any kind of help regarding this will be appreciated.

Thanks in advance for your help and time.

Raj Kumar

Find more posts tagged with

Comments

paramnemmini

Hi Rajkumar,

Did you get this problem resolved? I am facing the same issue. Please let me know.

Param

antey

Hi, Rajkumar!

Lifecycles (dm_policy objects) are usually stored in '/System/Application/<your dar name folder>'. If you install new DAR containing the same lifecycle, the lifecycle will be created in the new place. You should make some steps to fix it:

uninstall new (wrong) lifecycle (using API)
delete new (wrong) lifecycle (dm_policy object)
uninstall old lifecycle (using API)
link old lifecycle to the folder '/System/Application/<your new dar name folder>' (or folder where new lifecycle was located)
install old lifecycle
re-install your new DAR

After that you will have got one correct instance of lifecycle.

Anton

the_lord

Hi Rajkumar,

The possible reason is that the existing lifecycle is already attached to some objects.

So when you install new dar with updated lifecycle it will not replace the existing one.

Instead if you need to install new life cycle and remove existing one then update all the object's r_policy_id to '0000000000000000' who is having old lifecycle attached and then try to install new one, make sure that old lifecycle is not used by any object then after.

you can use below query :

update dm_sysobject (all) objects set r_policy_id = '0000000000000000' where r_policy_id = 'Old Lifecycle id';

you can try this and it may work.

Thanks,

Amit