Who Owns this Repository?

You need to figure out the repository owner for a repository. What do you do?

Guess, it’s dmadmin. Well, dmadmin is the conventional installation owner. Indeed, it is possible that there is no user named dmadmin in a repository.

So, maybe use the installation owner – the user id on OS used for installing the Content Server. Well, installation owner is separate from repository owner and there is no requirement for the two to be the same. Actually, they should be kept separate – in many organizations installation responsibilities are separated from day-to-day administration responsibilities.

Hmmm, is it same as the repository name? Maybe. When you configure a new repository, you have a choice to set up the database beforehand or to let the configuration script set it up for you. If you let the script do this work, it defaults the DB account to be the same as the repository name. In this case, this guess would be valid. However, it is not required to be so. If the database is already set up, you can provide this information to the configuration script and it uses the provided DB user to create the corresponding user in the repository. This user becomes the repository owner.

Then, is there an attribute on dm_docbase_config which identifies the repository owner? We are getting close. There isn’t an attribute called docbase_owner or repository_owner. However, the owner of the docbase config object (identified by owner_name) is the repository owner. If you are looking for the exact DB login name for the repository owner then look at the user_db_name attribute on the user object for the repository name. For the repository owner, it is same as the user_name by default.

Also, the operator_name on a dm_server_config object defaults to the repository owner name. Remember that this is just a default. Further, there can be multiple content servers serving one repository.

Advertisements

4 thoughts on “Who Owns this Repository?

  1. There is an quick and easy way to find these informations using DQL:

    select
    r_object_id,
    user_name,
    user_os_name,
    user_db_name
    from
    dm_user
    where
    user_name = ‘dm_dbo’

    The string “dm_dbo” is automatically translated in the name of the repository owner.

  2. Thanks for bringing it up – it is certainly very convenient.

    I avoided this usage since the Content Server Admin guide (5.3 SP1, pg 73) suggests that the repository owner’s alias is dm_dbo only for Oracle and Sybase RDBMS. If you could confirm that this works for all RDBMS back-ends it will be wonderful.

  3. I used dm_dbo on a variety of RDBMS and never noticed any problem if the Content Server was at least 5.x. In 4.x idql/iapi it doesn’t work, but such systems should be long gone 😉

    I checked the query above on an MS SQL based Content Server 5.3 SP4 and it worked fine.

    I never noticed the dm_dbo usage hint in the Admin guide before. But the documentation seems to be a little bit confusing. In the DQL Guide 5.3 SP1 on page 153 it states (for the unregister command):
    “If the RDBMS is Oracle and the owner is the DBA,
    you can use the alias dm_dbo.
    If the RDBMS is MS SQL Server or Sybase and if the
    owner is the DBA, you can use the alias dbo.”

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s