Using R-code MD5 values to determine files to deploy, schema triggers throw CRC errors after schema change and redeploy

When using R-code MD5 values to determine files to deploy, schema trigger procedures can start throwing CRC errors after schema change and recompile.

Apr 30, 2015
Knowledge

Title

URL Name

Using-R-code-MD5-values-to-determine-files-to-deploy-schema-triggers-throw-CRC-errors-after-schema-change-and-redeploy

Article Number

000186077

Environment

Product: OpenEdge Version: 10.2B, 11.x OS: All supported versions

Question/Problem Description

After making a schema change and recompiling code, need to redeploy changes as well.
Deployment is done via custom-built incremental package.
Files to include in deployment package are determined based on r-code's MD5 value.

Trigger procedure programs that were recompiled were not redeployed.
Programs that were missed during deployment now throw "CRC for <object> does not match CRC in <procedure>. Try recompiling. (1896)" error.

Steps to Reproduce

Clarifying Information

.r files are compiled with GENERATE-MD5 option active.
Schema change does change table CRCs (ie. dropping or adding fields), all code was recompiled to take that into account.

Error Message

CRC for <object> does not match CRC in <procedure>. Try recompiling. (1896)

Defect Number

Defect PSC00328565

Enhancement Number

Cause

The MD5 value of the r-code does not change as it should. (Documentation states "The MD5 value is virtually guaranteed to be different if the file content has changed. As with CRC, content changes include any schema changes. That is, if only the schema changes, the MD5 value also changes. ")

As a result, the tool fails to detect the trigger procedure must be included in the deployment package.

Resolution

Until the fix is available, use the workaround below.

Workaround

1. Update the packaging tool to check both the MD5-VALUE and the TABLE-CRC-LIST for the r-code. The TABLE-CRC-LIST does change to reflect the new table CRC as expected.

2. Make a dummy change to the trigger procedure (e.g. add a comment or white character(s)). This will force the MD5 value to change.

Notes

Attached .zip file contains a test case to show the MD5-value remaining unchanged.

References to written documentation:
ABL Reference - COMPILE statement, GENERATE-MD5 option.

Keyword Phrase

Last Modified Date

4/30/2015 11:30 AM

Using R-code MD5 values to determine files to deploy, schema triggers throw CRC errors after schema change and redeploy

Files(1)

Was this article helpful?

Was this article helpful?

Using R-code MD5 values to determine files to deploy, schema triggers throw CRC errors after schema change and redeploy

Information

Related Articles