[DM_POLICY_E_EXIST_NO_BP_LOG]error: “BP Log (/path_to_dba/log/repo_id/bp/bp_transition_some_id.out) was not created.”
A commonly recommended solution for this error is to clear the dmcl cache on Content Server and bounce it.
However, we recently discovered another cause of this error.
When we changed the lifecycle implementation to Java, lifecycle related actions started failing with this error. Changing the implementation back to Docbasic got rid of the error. The lifecycle implementation can be changed using Documentum Application Builder. However, when you have Java customizations for the lifecycle, you have to use the Java implementation.
It turns out that any kind of execution failure related to state transition can lead to this error message. Even though the initial reaction is to look at permissions or cache, the cause can be anything. In a high availability (HA) configuration it turned out to be a filestore configuration issue and a missing web.xml on one of the method servers.
[UPDATE] In 6.7 SP1, we encountered this error whenever a Docbasic script tried to execute on the method server. In particular, a lifecycle action failed to execute if
Use Method Server was selected. It turned our that there were different versions of
dfc.jar present on the Content Server host. Once all the dfc.jar instances were replaced by copies of one
dfc.jar, the problem went away.