The same UML model may not work correctly on different DBMSs. For example, a given model may work on a personal geodatabase (Access) but not work correctly in Oracle.
A common problem is the use of reserved keywords as geodatabase elements; for example, feature classes or fields. The same string may be a reserved keyword on Oracle, but not in Access. That is the case of “Type”, a commonly used name for fields.
Use the Semantics Checker to catch such problems. When running it, check the Include Warnings check box and look for error 3150 (Invalid field name: Reserved keyword). This warning catches reserved keywords for all possible target DBMSs.