Author Topic: I can't connect to oracle from Enterprise Architec  (Read 4690 times)

AlcoaACESEA

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
I can't connect to oracle from Enterprise Architec
« on: July 27, 2011, 09:48:12 pm »
Always have ora-00942 : Table or view does not exist
But I'm able to connect to this database using sql.
Can someone provide some guidelines to fix this ?

Thanks

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13404
  • Karma: +567/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: I can't connect to oracle from Enterprise Arch
« Reply #1 on: July 27, 2011, 11:26:58 pm »
Probably a user rights issue.
Contact Sparx Support if you need more help.

Geert

AlcoaACESEA

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: I can't connect to oracle from Enterprise Arch
« Reply #2 on: July 27, 2011, 11:35:59 pm »
Yes but I can connect to oracle with the user using sql.
Do I need to define oracle user in EA ?

kepNCI

  • EA User
  • **
  • Posts: 127
  • Karma: +1/-0
    • View Profile
Re: I can't connect to oracle from Enterprise Arch
« Reply #3 on: January 11, 2012, 08:08:47 am »
Had the same issue. Was fixed when I updated Oracle ODBC driver to the latest r10 version. Was using the Oracle 8 ODBC driver, which as you stated, worked fine with SQL as well as with ODBC using MS Access and MS Visio. Even Vision was able to re-engineer the database.

Had to install Oracle 10 client in order to get the latest Oracle driver. In addition to creating new ODBC data sources with the new driver, One needs to make sure ORACLE_HOME parameter is set to the location of the new ODBC driver.  

Note: I do not recommend the following, but for non-EA related reasons, I was not able to reset my ORACLE_HOME and/or PATH. Insetad I took a risk and copied the v10 ODBC DDLs into the existing ORACLE_HOME file (as seen in my PATH), thus overwriting the v8 DDL files. I looked at the documentation on Oracle for Instant Client to identify the ODBC DDLs. This worked and I did not have to create new ODBC data sources.)