Re: Designer 2.1 Problem with DB-Design Capture

From: Diane <Diane_at_coalole.demon.co.uk>
Date: Sat, 13 Mar 1999 17:53:47 +0000
Message-ID: <pXlRDBArYq62IwNF_at_coalole.demon.co.uk>


In article <36eb5054.8218167_at_news.giganews.com>, Kim Hansen <nobody_at_post8.tele.dk> writes
>On Thu, 04 Mar 1999 14:11:25 +0100, Henrik Bachmann
><Henrik.Bachmann_at_bim-consulting.de> wrote:
>
>>Hi there,
>>
>>I have some problems with the "Design Capture" tool of the "Design
>>Editor" (Version 2.0.20.5.0 Conf. 2.17) in Oracle Designer/2000
>>Repository (7.0.3.0.0).
>>
>>I want to start the reverse engineering of a user scheme (Oracle 8.0.4,
>>but only 7.3.4. features implemented). The user 'USER' is the owner of
>>some tables (e.g. 'TABLE') and I have public synonyms like this:
>>
>> create public synonym TABLE for USER.TABLE
>>
>>When I try to reverse engineering the scheme I will run into the
>>following error:
>>
>> CDA-02000:
>> Database Synonym 'TABLE': Uniqueness conflict in Application System
>>'TEST'
>> version 1 with Table Definition 'TABLE'.
>>
>>But if I want to delete the synonyms in the "Server Model - Navigator"
>>the following error occurs:
>>
>> Design Editor:
>> Commit the results of the Design Capture before creating or deleting
>>objects.
>>
>>Oh yes - I realy wanna do this but you know what's happen:
>>
>> CDA-02000:
>> Database Synonym 'TABLE': Uniqueness conflict in Application System
>>'TEST'
>> version 1 with Table Definition 'TABLE'.
>>
>>Can I supress the reverse engineering of synonmys of tables?
>>
>>Is there anybody out there with hints and tips or tricks to reverse
>>engineer a database scheme.
>
>Drop the public synonyms before you reverse engineer, then recreate
>them, that's how I got to work.
>
>Kim Hansen.
>
>
>>I will be happy if someone knows sites or links where I can find
>>whitepapers, case studies or other stuff around the migration from
>>Oracle Forms 4.5 to Oracle Forms 5.0.
>>
>>Best regards
>>
>>Henrik Bachmann
>>mailto:Henrik.Bachmann_at_bim-consulting.de
>>
>>B.I.M.-Consulting Magdeburg http://www.bim-consulting.de/
>>D-39124 Magdeburg
>
This is a known bug BTW and fixed in 2.1.2

-- 
Diane
Received on Sat Mar 13 1999 - 18:53:47 CET

Original text of this message