Error importing Oracle schema

[Rinaldo]

Hi.

I am receiving an error message when importing an schema from an Oracle database. One of my procedures is raising me the following error:

DAO.Database [3072]
Expression too complex

I am using the native Oracle 10g ODBC Provider. What does it mean? Is there any kind of limitation when importing procedures from Oracle?

Regards,
Rinaldo

[Frank Horn]

The error message coming from DAO, this sounds like a bug in EA's persistency layer. Would be interesting to know whether the error also occurs when your model does not reside in an eap file (which is actually in MS Access format and being written to by EA through DAO) but in a decent database server. If you know how to set up a database repository for EA you may want to try this out. If not, don't bother, it's Sparx's work to trace the bug anyway.

A bug report would be called for. Problem is, how can Sparx reproduce it? They would need a database schema with sufficiently awful procedures (or whatever causes the error). You can attach a file to your bug report when you're a registered user, but this would still require that you have a script for the database, and of course one which is not top secret.

Anyway, it sounds like a serious bug. Importing a schema must never pop up an error message. The worst it should do would be to write a log with things like "procedure abc not imported for exceeding complexity".

[Rinaldo]

Hi Frank.

Yes, it really seems like an ugly bug. I will open a bug report and as possible, provide information to help the Sparx team to reproduce it.

We are at the very beginning of the works with EA and importing data from Oracle is fundamental to allow for the next steps.

Thanks,
Rinaldo

[toreg]

We recently experienced this same problem in EA 8.0    Did anyone ever receive a response back on how to resolve?