| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> 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 onForms triggers.
David Wendelken
CASEtech Inc.
dwendelken_at_casetech.net <mailto:dwendelken_at_casetech.net>
Al Rusnak
DSN 687-4937
COM (804)734-4937
-----Original Message-----
From: Shockey, David [mailto:DShockey_at_jwrinc.com]
Sent: Friday, July 14, 2000 2:08 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: Tips for Building the Designer2000 Repository
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-----
From: Henry.O'Keeffe_at_ft.com [ mailto:Henry.O'Keeffe_at_ft.com
<mailto:Henry.O'Keeffe_at_ft.com> ]
Sent: Friday, July 14, 2000 11:42 AM
To: Steve Orr
Cc: oracle-l_at_fatcity.com; oracledba_at_QuickDoc.co.uk
Subject: Re: Tips for Building the Designer2000 Repository
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" <sorr_at_arzoo.com> on 14/07/2000 09:19:06 To: oracle-l_at_fatcity.com, oracledba_at_QuickDoc.co.uk cc: (bcc: Henry O'Keeffe/PSD/LONDON/FTI)
Subject: Tips for Building the Designer2000 Repository
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
 |
 |