i used the search function several times, but didn’t find the specific answers, so i have three questions/problems left:
I use TDM in Version 18.104.22.168 to create a physical model for Oracle 10g.
When generating an ALTER-Script TDM generates a temporary copy of an original table in which the constraint-names are the same. This causes a “unique constraint name violation”, when executing the script (“SQL Error: ORA-02264: name already used by an existing constraint”).
I found a post in which you refere to CR# 64291 that concerns this problem. I guess this problem is not fixed in my version (22.214.171.124) yet?
In one table, i have defined an alternative key. The problem is, that one of the attributes (an end-date) shall be nullable. As i know oracle can handle alternative keys in which an attribute may be null, but in TDM i can’t deactivate the “not null”-checkbox for the attribute. Caused by my ‘old’ version (126.96.36.199) again?
(Optional Question: 3. Is it possible to generate a kind of “WHENEVER SQLERROR”-Statement for Oracle?)
If you like, i can send you a snapshot and the TXP-Files it refer to.
Thanks for your help. The answers i read till now were really helpful. Please don’t mind my english. Thanks!