CDM denormalization prevalidation tasks
When you run the CDM denormalization utility, the utility performs certain prevalidation tasks before the actual denormalization happens.
The details of the prevalidation tasks are recorded in the cdmflattening.log and <localhost>.txt file located at the following location:
<install dir>\BMC Software\AtriumCore\cmdb\utils\cdmflattening\logs
The CDM denormalization utility performs the following prevalidation tasks.
| No. | Prevalidation check | Troubleshooting information |
|---|---|---|
| 1 | The utility checks for mandatory fields in the denormalized classes. | The CDM denormalization utility exits if you have used mandatory fields in the classes that will be flattened. You must change the mandatory attributes to |
| 2 | The utility checks for custom filters in the denormalized classes. | The CDM denormalization utility exits if you have used custom filters in the classes that will be flattened. You must remove the filters from the classes to be flattened and move the filters to the |
| 3 | The utility checks for custom active links in the denormalized classes. | The CDM denormalization utility exits if you have used custom active links in the classes that will be denormalized. You must remove the active links from the forms that are mapped to the classes that are to be flattened and move the links to the form representing BMC_BaseElement class. |
| 4 | The utility checks for custom escalations in the denormalized classes. | The CDM denormalization utility exits if you have used custom escalations in the classes that will be denormalized. You must remove the escalations from the forms that are mapped to the classes that are to be flattened and move the escalations to the form representing the BMC_BaseElement class. |
| 5 | The utility checks for custom classes entry in the denormalized classes list. | The CDM denormalization utility exits if you have modified the cdmflatten.properties file by adding additional classes in the list of classes to be denormalized. You must remove the custom classes from the list because CDM denormalization is supported only for out-of-the-box classes. |
| 6 | The utility checks for Attribute Name conflict. | The CDM denormalization utility exits if there are attributes with same name among the classes to be flattened. You must rename the duplicate attributes. |
| 7 | The utility checks for Attribute Field ID conflict. | The CDM denormalization utility exits if there are attribute fields with the same ID. You must change the field ID of the duplicate attribute field. |
| 8 | The utility checks for custom Indexes conflicts. | Re-attach the index. |
| 9 | The utility checks if CDM denormalization is already performed. | --- |
| 10 | The utility checks for AI/NE/RE jobs that are running. | Stop the jobs and continue. You must manually stop any third party tools that you use to integrate CMDB data. |
Comments
Log in or register to comment.