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: Red de la Cruz <Red.DelaCruz_at_JAMESMARTIN.COM>
Date: Mon, 17 Jul 2000 22:01:29 -0400
Message-Id: <>


My 2 cents:

In addition to this:
1. Which I consider very important is to setup your standards:

	1.1 naming stds for all objects - Analysis objects:
	 	entity, processes/functions, domains, columns, diagrams,
repository, etc.
	    Design and development objects:
		tables, shortname, FK, PK, modules,server
objects(package,function, proc, 		triggers), etc.)
	1.2 GUI standards - so you could control the look and feel of your
screens and 				  reports(I suggest that right now
you do your templates). 					  There's

one product of Oracle which is HeadStart which could very well help you alot(in my case it did).
	1.3 Coding standards - when is the code put into the form trigger?
in the program 		unit? in the module library? in the application
2. I agree with the stable data model. Stable in the sense that before transforming your ERD into a logical design(meaning logical tables)and eventually generating your modules, there should be very minimal data model changes or none at all. Changes have a big impact on your modules and your logical tables.
3. You need a Repository Administrator for this job.
4. Perform version control every time you'll have a major milestone.
5. You need to draw the line when to quit generation and do it in Developer.
100% generation on our scenarion is not achievable.

Red de la Cruz
Senior Consultant
James Martin + Co.

-----Original Message-----
From: Rusnak, George A. II [mailto:rusnakg_at_SDCL.LEE.ARMY.MIL] Sent: Monday, July 17, 2000 10:45 PM
To: Multiple recipients of list ORACLE-L Subject: RE: Tips for Building the Designer2000 Repository

We am currently involved in a very large project that is using Designer. I would suggest that if you intend to use Designer that you consider a few things.

1) Make sure you have a STABLE data model that supports your business.
2) If you buy into Oracle Designer then buy into the Oracle methodology.
3) Get Just in Time (JIT) training on Oracle Forms esp.. a custom course on
Forms triggers.
5) We have a gentleman on site that you NEED to discuss your Designer development strategy with:
     David Wendelken
     CASEtech Inc. <> 

Al Rusnak

DSN 687-4937
COM (804)734-4937   -----Original Message-----
Sent: Friday, July 14, 2000 2:08 PM
To: Multiple recipients of list ORACLE-L

We are considering using Designer for application development. In the real world, how close can you get to 100% generation? If changes are made using Developer, can the changes be included in the application version that is stored in the repository?

-----Original Message-----
<mailto:Henry.O'> ]
Sent: Friday, July 14, 2000 11:42 AM
To: Steve Orr

Dunno ... I've got designer running in ONE tablespace (USERS) and it seems ok.
(Yes, yes, bad bad bad)
Designer apears CPU bound more than disk bound, especially when reverse engineering stuff, so I'd make sure you had a fast client PC first rather than
worrying about splitting the respository up into 15 tablespaces. (15 tablespaces for designer is a joke quite frankly) Another thing you'll need is plenty of rollback.

HTH .... "Steve Orr" <> on 14/07/2000 09:19:06 To:, cc: (bcc: Henry O'Keeffe/PSD/LONDON/FTI)

Sometimes Oracle's recommendations are good and sometimes they are puzzling.

I'm installing Designer2000 (version 6i) today and going thru the docs. Oracle recommends creating 15 tablespaces dedicated for Des2k objects. I like the idea of segregating like objects into separate tablespaces. But, for a large repository, the recommended size for 8 of these tablespaces is less than 5MB. Eight itty bitty teeny tiny datafiles < 5MB ??? (This is on a

scale of MS Access :-) Is it really worth it or should I ignore Oracle's recommendations and lump some of these tablespaces together (except for those containing I/O contending objects)?

(I'm putting the repository on a small Sun pizza box dedicated to DBA management stuff like statspack, the OEM and RMAN repositories, my own stuff, etc. No capacity problems are anticipated on this box.)

Any other tips on sizing and init.ora parms for supporting the Des2k repository? Any other DBA issues for maintaining the repository?

All off-the-wall-2-bit-recommendations are welcome from my DBA friends on the lists. :-) TIA.

Puzzled as usual...
Steve Orr

If you're bored, then visit the list's website: <> (updated
to unsubscribe, send a blank email to to subscribe send a blank email to

If you're bored, then visit the list's website: <> (updated daily) to unsubscribe, send a blank email to to subscribe send a blank email to
Author: Rusnak, George A. II
  INET: rusnakg_at_SDCL.LEE.ARMY.MIL

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
To REMOVE yourself from this mailing list, send an E-Mail message
to: (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
Received on Mon Jul 17 2000 - 21:01:29 CDT

Original text of this message