After adding a new field to a table and to one of its keys, the Copy to Prod-status function (-CPY DATABASE xxxxxxxx(T001),PROD) fails with these error messages:
DDPSV20001 STRUCTURE VERIFY FAILED
DDVKEY0017 UNEQUAL MAX-KEY-LENGTHS FOR SAME DATACOM-ID
DDWKEY0008 WARNING MIXED FLD TYPES FOR DATACOM-ID
While there could be many reasons for a Database structure to fail verification, in this case, since a field was added to a table and key, the focus should be on the key definition. Here, the messages about “SAME DATACOM-ID” give a clue that there could be a problem with a Shared Key definition.
When multiple keys have the same DATACOM-ID (also called Shared KeyIDs), there are certain considerations and restrictions about how these keys are defined.
If the intention is for these keys to be shared, further analysis of the key definitions must be made to ensure they are correct and meet the restrictions.
If these keys are not shared, the errors can be resolved by changing the DATACOM-ID of the key that is modified in this project, and repeating the process to update and copy it to production status.
For more information about using Shared DATACOM-ID values (Shared Keys), please refer to Knowledge Base document TEC1081311, with the title "Can I use the same Datacom-ID for different keys defined in different tables in my database?"
For more information about designing Keys, please refer to the following Guides:
CA Datacom/DB Version 14.02 Database and System Administration Guide, in the section “Designing Keys”
CA Datacom/DB Version 15.00 Database and System Administration Guide, in the section “Designing Keys”
As always, please contact CA Technologies support for CA Datacom if you have further questions.