Examine Failed Operations Caused by Rule Violations

If your deployment accidentally violates the rules you’ve set up on your database, you can generate a list of failed operations such as forecast, deploy, and packager that were caused by rules violations. This allows you to identify violations and resolve failures quickly. Learn more about Rules here.

Produce General statistics

Use the below queries to produce general statistics about executed operations.

SELECT * from dprj_forecast; or SELECT * from dprj_deploy_packager

Example output for dprj_forecast; :
Example output for dprj_deploy_packager; :

Detailed Operations Statistics

Use this query to produce detailed statistics regarding rule violations and to which projects/operations they are related.

SELECT o.project_name, o.action_type, r.LEVEL_NAME, r.PHASE, r.RULE_NAME, msg.MESSAGE
FROM RULE_RESPS as r
INNER JOIN RULE_RESP_MSGS as msg ON msg.FK_RULE_RESPS_ID = r.ID
INNER JOIN OPERATIONS as o ON r.FK_OPERATIONS_ID = o.ID
WHERE r.PARENT_TABLE = 'OPERATIONS' order by o.project_name;

This query should be executed via the DMC database.

Example output:

Detailed Change Impacts Statistics

Use this query to produce detailed statistics regarding the changes affected by rule violations and to which projects/operations they are related:

SELECT ch.change_description, r.LEVEL_NAME, r.PHASE, r.RULE_NAME, msg.MESSAGE
FROM RULE_RESPS as r
INNER JOIN RULE_RESP_MSGS as msg ON msg.FK_RULE_RESPS_ID = r.ID
INNER JOIN CHANGE_IMPACTS as ch ON r.FK_CHANGE_IMPACTS_ID = ch.ID
WHERE r.PARENT_TABLE = 'CHANGE_IMPACTS';

Example output: