I am trying to move a replica database but the configuration fails on the ddictbuild

Document ID : KB000100522
Last Modified Date : 08/06/2018
Show Technical Document Details
Issue:
I am to use the swing box method, and having a problem moving the replica database to the environment. Pdm_configure is failing on the ddictbuild. My production system has the latest cumulative patch, and I have installed 14.1 with no patches. When I attempt to move the replica database to the swing box environment, the pdm_configure fails. Errors in the logs state the ddictbuild is failing.

In the ddict.sch file, the final line may look like:

"Could not find part table for Request_Workflow_Task"

It may be for a different table instead.
Cause:
It's possible for this type of failure to occur if a custom column was added to a database table that was added to Service Desk Manager after 14.1, in one of the cumulative patches.

For example, if you add a custom column to the table Request_Workflow_Task you may see this failure. The table Request_Workflow_Task does not exist in 14.1 GA, it was added in a cumulative patch
Resolution:
Prior to moving the replica database, you must apply the same cumulative patch level in your test system that you have in your production system. Once the system is on the same patch level, you can then proceed to move the database.
Additional Information:
Details on how to replicate a database are located here:

https://docops.ca.com/ca-service-management/14-1/en/implementing/how-to-move-the-ca-mdb-data-from-the-source-to-the-target-systems/move-the-ca-mdb-database-on-microsoft-sql-server