Getting DM_POLICY_E_EXIST_NO_BP_LOG

Hi,

We have recently migrated to Documentum 6.5 SP 1. As a part of the regular testing, we did with our system, all of a sudden, we are getting the following error -

[DM_POLICY_E_EXIST_NO_BP_LOG]error: "BP Log (/opt/documentum/dba/log/00000001/bp/bp_transition_01000001801d451c.out) was not created."; ERRORCODE: 100; NEXT: null

This was working earlier and all of a sudden we started to get this error.

Any kind of help is appreciated.

Thx,

Ravikanth

Find more posts tagged with

Comments

mszurap

Hi,

Check whether your Java Method Server is running. If not, start it, if it's running, then restart it.

I faced this problem too, when I modified too many times my lifecycle module (I hot deployed it) and somehow the JMS could not load it anymore, so a bounce helped me out.

Mike

K.Chandru

I guess the problem is with Caching

Rename $DM_HOME/bin/dmcl to $DM_HOME/bin/dmcl.old

Set the following flag in the dmcl.ini on the Content Server and
restart the server
client_persistent_caching = F

valentinbragaru

Hi I have the same problem, problem is solved by removing lifecycle(API destroy,c,{r_object_id},T) an reinstall them again

Priyanku

Resolution :-

-------------------

1. Recreate the /opt/documentum/dba/log/00000001/bp folder with installation owner

2. Clear cache

3. Restart docbase and JMS