Sparx Systems Forum

Enterprise Architect => Bugs and Issues => Topic started by: berch33 on December 06, 2019, 06:25:03 pm

Title: Unique Contraint at Oracle Repository
Post by: berch33 on December 06, 2019, 06:25:03 pm

Hi there,
I need to know where my mistake is, or if its a real bug. The problem is reproducable.
My Setup: I set up an Oracle DB with 6 Useres and each one has its own tablespace, so I get 6 separate repositories.

I use ProCloud OLE DB, I can connect, I uesed the "project transfer" function of EA Client (V 15) to transfer a minimal Model (one Model incl. one view incl. one package incl. one diagram) that I created only for this use. Transfer successful, open repository with EA Client via ProCloud, also working, project integrity perfect, Oracle t_package shows 3 packages

Now the error: when I ADD another package "NewPackage", eg. to the "view"-Package, I get two errors:
- ORA-00001: Unique Contraint (username.PK_PACKAGE) violated
- ORA-00001: Unique Contraint (username.PK_OBJECT) violated

The Oracle DB t_package now STILL has only 3 entries, but the name of the last one (package) was now changed to "NewPackage", so an existing was changed instead of a new being added.
--> this only happens on the first occurrence, all I add later do not pose a problem.

Same thing with Diagrams, but with PK_DIAGRAM error

Can you understand? Can you help?

--> May the problem be, that using 6 Users with separate tabelspaces will NOT give them their own SEQUENCES? And this leads to the problems?

Title: Re: Unique Contraint at Oracle Repository
Post by: Geert Bellekens on December 06, 2019, 07:07:35 pm

You really shouldn't be using Oracle for Sparx. You are going to regret it, big time.
Everyone that has ever used EA on Oracle I know of regrets it and has already changed, or is planning to change to another database system.

The problem is that the performance of EA on an Oracle backend is terrible, and you won't figure that out until after a few months/years, when transferring to another database is going to be painful.

MS SQL Server or MySQL are the better choices

Geert

Title: Re: Unique Contraint at Oracle Repository
Post by: berch33 on December 06, 2019, 07:46:37 pm

Thanks for the info. WHAT DBMS IS reccomended?

Title: Re: Unique Contraint at Oracle Repository
Post by: Geert Bellekens on December 06, 2019, 07:51:27 pm

Quote from: berch33 on December 06, 2019, 07:46:37 pm

Thanks for the info. WHAT DBMS IS reccomended?

Quote from: Geert Bellekens on December 06, 2019, 07:07:35 pm

MS SQL Server or MySQL are the better choices

Geert

Almost all of my clients use SQL Server.

Geert

Title: Re: Unique Contraint at Oracle Repository
Post by: berch33 on February 28, 2020, 12:33:20 am

I switched, problems I have no more...

Also no problems i had with PostgreSQL...

--> Close