Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Tips for Building the Designer2000 Repository

RE: Tips for Building the Designer2000 Repository

From: Steve Orr <>
Date: Tue, 18 Jul 2000 08:41:55 -0700
Message-Id: <>

Thanks for all the feedback on Des2K.

I've discovered one very irritating lack of feature... For reverse-engineering or registering a database for retrofit the repository and the schema need to be in the same database. I discovered this AFTER having created the repository on another machine so now I need to recreate the repository on the main development database. The other tools I've used allow reverse engineering over SQL*Net with one DB connection to the repository database and another to the source database to be reverse-engineered or documented. The docs say you can import the schema from the source to the repository DB. This is crazy. Why is Oracle so dumb on this one?

Irritated at Oracle again,
Steve Orr

-----Original Message-----
From: []On Behalf Of paquette stephane
Sent: Tuesday, July 18, 2000 1:05 AM
To: Multiple recipients of list ORACLE-L Subject: RE: Tips for Building the Designer2000 Repository

A stable data model ???
I've seen that in a dss application.
On oltp systems, I've been less lucky.

On the current project, I was in charge of studying the switch from AMC Designer to Oracle Designer 6. I've decided to stay with AMC Designer. Oracle Designer 6 was too much overhead (we're a .com) and very few people knew the product here.

At a previous client, we're using Designer 1.3.2, 2 Oracle gurus have spent weeks to configure it and build the templates, we achieve 90% generation.

I do not think 100% generation is possible. For example, the current version doesn't support Intermedia indexes which is common nowadays (since it's free).

Received on Tue Jul 18 2000 - 10:41:55 CDT

Original text of this message