-
タイトル
Import of a Hotfix Transport fails if the object was already customized before. -
説明
The Transporter tool, compares the value in DialogColumn.Template, notice that the expected original value is not there and shows a step to resolve that conflict:
If the current value was selected, the Transporter does not change anything. That means, the old (wrong) value remains in QBMBufferConfig -> wrong.
If the value from the Transport package was selected (Transport value), the value is changed in QBMBufferConfig -> correct.
So, the only problem is, that the Transporter compares the OLD value at the wrong place and shows the "Merge conflict" dialog.
In that situation, the value in QBMBufferConfig has to be compared with the OLD value in the Transport package.This is specially relevant while installing Cumulative Updates on version 9.0 LTS as the user might think the import was successful if the CU installation logs are not examined, and the merge conflict warnings are not noticed. This would result in an incompletely installed Cumulative Update.
-
原因
This is due to the known Product Defect #444145. It is resolved on version 9.2.2 or upper.
Release notes: When importing a hotfix transport into the customer database, an error occurs if the customer has already made their own modifications to the same data. As a result, the database transporter presents a dialogue indicating a merge conflict.
The error has been fixed and the transporter now compares the data with the original data from the QBMBufferConfig table. -
対策
Select the transport value when prompted and review the logs when using the Database Transporter tool, as information about conflicts can be stored there.