Understanding the Repository - unv_universe and Tools/Dele

security Supervisor (4.x - 6.x)
1

erse

More curiosity on my part. I’ve experimented with deleting universes then looking for them in unv_universe to see if they disappear. I did this because I see universes in unv_universe that don’t appear in the list when I go into Supervisor and choose Tools/Delete Universe. The ones I deleted today disappeared from unv_universe. Why would I have universes in unv_universe that don’t appear in Tools/Delete Universe?

BO 4.1, Oracle 7.3

Thanks!

Cindy Clayton - Business Objects Consultant AT&T
336.698.2144

Give people more than they expect and do it cheerfully. Talk slowly but think quickly.
Smile when picking up the phone. The caller will hear it in your voice. Mind your own business.
Learn the rules then break some.
Judge your success by what you had to give up in order to get it.

Listserv Archives (BOB member since 2002-06-25)

2

Univ

In article
33AB9F0F694ED311B5810000C0AAE4F40283A177@gab200po08.ems.att.com, cindyclayton@ATT.COM (Clayton, Cindy, HRGBM) wrote:

More curiosity on my part. I’ve experimented with deleting universes then
looking for them in unv_universe to see if they disappear. I did this because I see universes in unv_universe that don’t appear in the list when I
go into Supervisor and choose Tools/Delete Universe. The ones I deleted today disappeared from unv_universe. Why would I have universes in unv_universe that don’t appear in Tools/Delete Universe?

The supervisor module gets universe details from the security domain not the universe domain, hence the table obj_m_universes is the one you need to look at. In this table is a field called m_uni_n_lat which is the last ction type - a value of 1 represents that the universe has been deleted and hence will not appear in the delete|universes list. If you compact the security domain then these should be removed.

Regards

Brian Patterson

Listserv Archives (BOB member since 2002-06-25)

3

Univ

The supervisor module gets universe details from the security domain not the universe domain, hence the table obj_m_universes is the one you need to look at.

Yes I see. One universe in that table…

In this table is a field called m_uni_n_lat which is the last ction type - a value of 1 represents that the universe has been deleted and hence will not appear in the delete|universes list. If you compact the security domain then these should be removed.

So what is the purpose of unv_universe?

Thanks!

Cindy

Listserv Archives (BOB member since 2002-06-25)

4

Univ erse

When you delete a universe through Tools/Delete you are doing a “logical” delete. The Last Action Type is set to 1 (deleted). When you do a Scan/Repair of the repository it should do a physical delete of the records.

Barbara Rosen
Business Objects Administrator
Global Database Technology
Salomon Smith Barney
barbara.rosen@ssmb.com

Listserv Archives (BOB member since 2002-06-25)

5

Univ erse

Barbara Rosen wrote…

When you delete a universe through Tools/Delete you are doing a “logical” delete. The Last Action Type is set to 1 (deleted). When you do a * Scan/Repair * of the repository it should do a physical delete of the
records.

Use the “Compact” option…

-Sai

Listserv Archives (BOB member since 2002-06-25)

6

In article
33AB9F0F694ED311B5810000C0AAE4F40283A5C7@gab200po08.ems.att.com, cindyclayton@ATT.COM (Clayton, Cindy, HRGBM) wrote:

The supervisor module gets universe details from the security domain not the universe domain, hence the table obj_m_universes is the one you need to look at.

Yes I see. One universe in that table…

In this table is a field called m_uni_n_lat which is the last ction type - a value of 1 represents that the universe has been deleted and hence will not appear in the delete|universes list. If you compact the
security domain then these should be removed.

So what is the purpose of unv_universe?

Cindy,

there is ever only one security domain (hold back any pedants!), however associated with this security domain you can have multiple universe domains - hence there can be an indefinite number of UNV_UNIVERSE tables, each within a separate schema. Presumably therefore the OBJ_M_UNIVERSE table provides a single point of reference for each of the universes, but also holds within in information relating to the universe configuration management if you like, i.e. when it was last changed, revision number and so on. In the (multiple) UNV_UNIVERSE tables you have slightly different (although some of it is duplicated) information relating to the universes present.

I presume that there is both OBJ_M_UNIVERES and UNV_UNIVERSE so that dependant upon what BO tool is being used, only one connection is required to be made to the repository, i.e. to get list of universes/reports etc etc, BO presumably connects using the security domain connection details. However, when a universe is selected, then the appropriate universe domain connection is used from that point on.

As you can see, I am not 100% sure on this one, however, what I do know is that however many universe domains are present, the OBJ_M_UNIVERESE table conatins details on all universes. Whereas the UNV_UNIVERSE table will only contain information relating to the universes within that specific domain.

Regards

Brian

Listserv Archives (BOB member since 2002-06-25)