After each CP upgrade, check for inconsistencies with rebuildModelDBSchemaAndViews

After each CP upgrade, check for inconsistencies with rebuildModelDBSchemaAndViews

We see very often that after a Content Pack upgrade we may have some inconsistencies between the Class Model and the Data Model. These inconsistencies are usually noticed when data-in fails or the TQL engine returns errors. 

Customers are often asked to run rebuildModelDBSchemaAndViews on preview to see if such inconsistencies are present.

The current request is to have OOTB behavior to run this JMX method rebuildModelDBSchemaAndViews on preview mode and log the output in mam.packaging.log for future reference. This log is rarely used and after a CP deployment, the customer is already recommended to check this log so any inconsistencies will be easily noticed.

starting with CMS.05 we already have an undocumented API method to check for such inconsistencies similar to the JMX approach (QCCR1H125692 was implemented for the same health check reasons).

1 Comment
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.