Integrity Checker reports many instances of this type of warning:
BMXAA0442I - WARNING -- BMXAA0498W - The following columns are defined to be 'same-as', but have different must-be settings:
ASSIGNMENT.TASKID Must-Be = 0 same as WORKORDER.TASKID Must-Be = 1
The must-be settings of the two columns should match, but they do not.
Because the columns are defined to be same-as, their definitions should be the same, including data type, length, scale, etc., and their must-be settings. Must-be is a flag. Its value can be 1 or 0 (true of false).
Resolving the problem
This problem does not need to be resolved. There is no known impact, other than resolving the Integrity Checker warning, if this problem is left unresolved. However, if so desired, you can use Database Configuration to modify the must-be setting of the first column to match that of the second column. Using the example in this technote, modify the must-be setting of ASSIGNMENT.TASKID to be 1 so that it matches the setting of WORKORDER.TASKID.
|Systems and Asset Management||Tivoli Asset Management for IT||Not Applicable|
|Systems and Asset Management||Tivoli Change and Configuration Management Database|
|Systems and Asset Management||Tivoli Service Request Manager|