Troubleshooting: Conflicting message type in the MSGTYPES table
Problem
If
you have created your own message
types in previous versions of WebSphere Commerce, there is a possibility
that the messages are in conflict with new message types created in
WebSphere Commerce Version 7.0. The database premigration checker
will issue one of the following warnings if a conflict exists:
- The message type with MSGTYPE_ID = xxx in the table MSGTYPES will be in conflict with the message type introduced in the new release.
- The message type with NAME = yyy in the table MSGTYPES will be in conflict with the message type introduced in the new release.
Solution
If
the messages are in conflict,
modify the MSGTYPE_ID
or modify the NAME
or
change both.
The key is that both MSGTYPE_ID
and NAME
must
be unique in the table. Recompile the commands that refer to the custom
message types.
If you created your own message types in previous versions of WebSphere Commerce with
MSGTYPE_ID
= 1002, 1003, or 1004, and if you do not want to modify theseMSGTYPE_ID
values, you must perform some manual steps to update the conflicting message types created in WebSphere Commerce Version 7.0. Please contact IBM support for details.If you created your own message types in previous versions of WebSphere Commerce with
MSGTYPE_ID
= 1002, 1003, or 1004, and if you do not want to modify theseMSGTYPE_ID
values, you must install Fix Pack 1 before migration.