Re: Change repository owner

jwest_at_frii.com (Jim West) wrote:

>Howdy,
>
> I'm somewhat new to Designer/2000. We paid Oracle to develop our
>GUI app.
>
> Instead of heeding our wishes on ownership, the consultant chose a
>different owner name for the repository.

<SNIP>

Its probably being anally retentive but...

    Oracle originally recommended that a specific user be created as the repository owner with the sole purpose of owning the repository objects. I believe the idea was that it made controlling and identifing the repository objects much easier. (This was the gospel according to ORACLE back in the early days of CASE 5.1)  

At the same time it was recommended that mulitiple applications could and should reside within the same repository with each application being owned by a unique user.

I've utilized single repository/single application and single repository/multiple applications and never encountered significant problems occurring one way more than the other.

All of this is a long winded way of asking, Is it really worth the problems of changing the repository owner? Who the repository owner is won't impact the generation of objects (DDL, modules, etc) from the application, however the number of users who have administrative access because they know the application owner user/password might.

Assess your risks and then make your choice. If you decide that it is a major concern, then indeed identify that as a deliverable requirement and contact the consultant's supervisor. At the same time, if the consultant is/was hedging on this, what else has he done/not done that you might be missing by concentrating on this.

Food for thought... Received on Tue Feb 10 1998 - 00:00:00 CET