Re: Change repository owner

Ok....

<a light bulb goes on>

From this and other posts, I *now* know that there are really TWO different "owners" here.

There is the repository owner, and the APPLICATION owner. I believe that what I *really* want to do is change the Application owner!!

The Oracle consultant did create some DDL to gen objects. These objects took the name of what I *thought* was the repository owner causing us some issues with our C++ applications with regards to grants.

It appears that the repository owner and application owner are the same and being unaware of the fact that there are two different owners here assumed incorrectly that it was the repository owner that I wanted to change.

Sarah et. al., much thanx for enlightening me to this! :)

<Jim is much happier now>
<Jim now attempts to find the post that he recalls the steps in changing the Application owner>

[Quoted] Again, thanx from this very green Oracle developer! I definitely live by the adage of "The more I know, the more I don't know." I've been a software developer for 17+ years now and have just now decided to look into this new fangled stuff called Databases. :) I know enough SQL to be dangerous. I've done quite a bit of PERL and C++ programming to interface to DB's.

This Designer/2000 (and MS Access) stuff has really showed me that I still have A LOT to learn!

On Tue, 10 Feb 1998 01:42:44 GMT, sikes_at_erols.com (Sarah Sikes) wrote:

>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