Troubleshooting
Problem
Data Type Map for Physical to Logical transformation of MySQL Physical Data Model in IDA is incomplete: some data types either are missing or lack length/precision settings.
Symptom
- Some data types of MySQL Physical Data Model get unexpectedly transformed into CHAR(10) during Physical to Logical transformation.
Output page of Transform To Logical Data Model wizard reports the following problems encountered during the transformation:
"Attribute <COLUMN> - could not resolve data type <TYPE>. Using default data type."
where <COLUMN> is the fully qualified name of a table column and <TYPE> is the data type which was transformed into CHAR(10).
- When browsing the resulting Logical Data Model which was produced via Physical to Logical transformation of MySQL Physical Data Model, an attempt to open Type tab of Properties view for some attribute of an Entity raises java.lang.NumberFormatException.
[{"Product":{"code":"SS9UM9","label":"IBM InfoSphere Data Architect"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"General Information","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"7.5.2;7.5.2.1;7.5.2.2;7.5.3;7.5.3.1","Edition":"","Line of Business":{"code":"LOB76","label":"Data Platform"}}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
25 April 2025
UID
swg21567279