Book a Demo

Author Topic: Import from ODBC changing column type  (Read 4089 times)

JamieK85

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Import from ODBC changing column type
« on: November 19, 2010, 09:23:33 am »
Hello,

I am using version 7.5.850 of Enterprise Architect to assist in the modelling for a major project.  I have being building elements of the data model in an Oracle (11G R2) database and then importing the DB schema through a ODBC connection.
Initial tests of this functionality earlier this year, yielded positive results with EA generating Table and View classes with exact column structures.  Unfortuantly I reran the import process recently and noticed that a datatype changed from NUMBER to VARCHAR2(255), also it appears to be inconsistant in that it may be the first number field or the last.
I have tested the import several different times, ie new EA diagrams, different tables, and all have turned out with the same results, number fields being changed to character fields.

Has anyone else experienced this issue?

Jamie

hd

  • EA Administrator
  • EA User
  • *****
  • Posts: 312
  • Karma: +0/-0
    • View Profile
Re: Import from ODBC changing column type
« Reply #1 on: November 19, 2010, 01:02:23 pm »
Using Microsoft ODBC for Oracle instead of Oracle's ODBC Driver? See 3rd items in Notes...
http://www.sparxsystems.com/enterprise_architect_user_guide/software_development/importdatabaseschemafromod.html

JamieK85

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: Import from ODBC changing column type
« Reply #2 on: November 19, 2010, 03:32:41 pm »
I am using the Oracle in OraClient11g_home1 driver in the ODBC setup.  This has worked perfectly in the past.  Will test using the Microsoft driver for Oracle shortly.

Jamie

RoyC

  • EA Administrator
  • EA Practitioner
  • *****
  • Posts: 1297
  • Karma: +21/-4
  • Read The Help!
    • View Profile
Re: Import from ODBC changing column type
« Reply #3 on: November 19, 2010, 04:35:57 pm »
No no - don't use the Microsoft driver. You were correct in using the product's own Oracle driver. What HD was suggesting is that you had experienced problems because you had been been using the Microsoft driver, which is Not A Good Thing.

Maybe submit a bug report for Support to examine the problem more closely?
Best Regards, Roy