Running the CDM Denormalization utility

Perform the following steps to denormalize CDM:

1. Log into Mid Tier by using the following URL:
   http://<midTierServer>:<port>/arsys
   <midTierServer> is the name of the web server where the BMC Remedy Mid Tier is installed.
   <port> is the port number of the web server where the BMC Remedy Mid Tier is installed, which is required only if the web server is not using the default port (80 if using Microsoft IIS or 8080 if using Apache Tomcat).
2. Open the Atrium:CDMFlatteningProcessUI form by modifying the URL to 
   http://<midTierServer>:<port>/arsys/forms/<arserver>/Atrium:CDMFlatteningProcessUI.
3. The Atrium CDM DeNormalization Console opens in a new window.
4. Select the following:
   • (mandatory)Have you taken AR database backup ?
   • (optional) Do you want to rebuild indexes on the impacted tables at the end ?
     
     
     

5. Click Start CDM DeNormalization.

   Note

   Start CDM DeNormalization is unavailable until you have selected Have you taken AR database backup?.

   The status of denormalization is displayed in a table.
   The following color coding is used to denote different statuses:

   Green: Success

   Amber: In progress 

   Red: Failed

   
   
   

6. The utility performs certain prevalidation tasks before running the denormalization tasks.
   See CDM-denormalization-prevalidation-tasks.
7. A list of the all the classes that are denormalized is logged into the log file. 
8. The CDM denormalization process begins.
   At this stage, various tasks are performed to denormalize the classes.
   You must factor in the downtime that is required during the denormalization process.
   See Performing-the-CDM-denormalization-execution-tasks.
9. The CDM denormalization utility performs post-validation tasks. 
   Ensure that post-validation stage is completed successfully.
   If any post-validation errors are reported, the utility exits.
   You must fix the errors and run the utility again.
   When you run the utility, it skips all the tasks that were earlier completed successfully and resumes from the step the error occurred.
   See Performing-the-CDM-denormalization-post-validation-tasks.

10. The following message is displayed after the denormalization process has completed successfully.

    
    
    

11. Click OK.
12. (Optional) In the cdmflattenning.log file, verify if the CDM classes and relationships are denormalized and the data is migrated to the BMC_BaseElement and BMC_BaseRelationships class.
    The log file is located at the following location:
    <install dir>\BMC Software\AtriumCore\cmdb\utils\cdmflattening\log\cdmflattenning.log
13. Refresh the BMC AR System Mid Tier and sync the cache.
14. Migrate the delta data.
    See Migrating-delta-data-after-CDM-denormalization.

After the denormalization process is complete and the data migration is confirmed, you can delete the BMC.CORE:BMC_Product_, BMC.CORE:BMC_Component_, and BMC.CORE:BMC_LogicalSystemComponent_ forms. You can use Developer Studio in base development mode to delete these forms. 

For detailed documentation on searching corresponding forms, see The main data table for a form.

Limitations

• When you run the CDM denormalization utility, a custom CatSubclasses that is within the BMC_Software abstract class with attributes of a custom CatSubclass is not moved to the BaseElement class.
• After you run the CDM denormalization utility, the fields related to those attributes are moved to the BaseElement class. These fields are displayed automatically only for the English locale view.
• After you run the CDM denormalization utility, the join definition for the deprecated class below the denormalized class is not updated with the form name of the parent class.

Where to go from here

CDM-denormalization-prevalidation-tasks