DM_POLICY_E_EXIST_NO_BP_LOG

[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.

Add a Content Server to Repository (5.3 SP3 and later)

So you want to add a Content Server to your existing Documentum repository – how hard can it be? Not too much, but the process seems to change with every service pack. The good thing is that it is easier now, if you get it right.

We will not discuss clustering, automatic failover and such here.

Windows

1. Install Content Server binaries. Complete any other steps such as hotfixes for Centera, if being used.
2. Under %DM_HOME%\install there is a file cfsConfigurationProgram.exe. CFS stands for Content-File Server – which is what the additional Content Servers are called. Run this program and follow prompts. Most of the things will be straightforward – just make sure when admin/superuser account information is asked installation owner information is provided (rather than the repository owner). It will create server config, copy and modify the needed files, etc. These steps used to involve manual interaction earlier.
3. Check the file stores in use, particularly filestore_01. If its location points to a local drive it would mean that each Content Server will be looking at different physical locations when this file store needs to be used. This would need to change.
   1. You can either move the filestore to a new shared location or share the existing location on the first Content Server. This location looks like data/repo_name/content_storage_01 and the path is stored in a dm_location object named content_storage_01. The instructions for moving a file store can be found in the Content Server Admin guide under the heading of Maintenance. Mapping a drive might not work but UNC names such \\server\share\path can be used in dm_location.
   2. In production you might prefer to use a SAN/NAS type of storage rather than a simple folder share.

UNIX
Haven’t done this on UNIX recently but sharing a storage/path is easier in UNIX since it looks like any other file path.

LCMerror9001 – DTS Adobe Support Package

While installing Documentum Transformation Services you may encounter this cryptic error

LCMerror9001 – Turnkey service MySQL for Adobe LiveCycle does not exist.

If you searched the web you may find this document from Adobe which may not provide much help in fixing the problem.

Adobe Support Package for DTS 5.3 SP3 includes Adobe LiveCycle PDF Generator 7.0. It internally uses JBoss and MySQL. The above error can occur if there is a space in the path to the MySQL installtion. The service uses the the path to the binary, but the problem lies probably with the option it takes which is the path to my.ini.
Overall, the best approach is to avoid paths that include spaces.