UNIVERSE CONFIGURATION: WHICH REPOSITORY TABLE

Hi,

I have had to replace a corrupted Universe file in the Business Objects repository.

As a result I have lost all the Universe configuration for the different user groups, specifically the row level security settings.

Does anyone know which table(s) this data is stored in, as I want to restore it from last night’s database backup.

Many thanks, John.

[Edited, removed “Urgent” from topic title. In addition please realize that typing everything in CAPS is considered SHOUTING. Thank you, Andreas.]


John Warne Smith (BOB member since 2005-04-18)

Hi mister Smith :wink:

I strongly recommand you to make a full restoration of all your db (all your domains sec, doc and unv).
Row level restrictions are stored in these tables :

  • OBJ_M_UNIVCST
  • OBJ_M_UNIVDBCST

Regards
An other Smith :wink:

Please don’t SHOUT in your topic headings :slight_smile:

If you’re recovering your repository you ought to be recovering all the tables, not just one, otherwise you could get inconsistencies.

Have you asked BusObj tech support? I would imagine they’re best placed to advise.


RobinM :uk: (BOB member since 2003-02-25)

Row level restrictions are stored in the OBJ_M_UNIVDBCST table. As others have cautioned though, restoring just this single table is asking for trouble. I think the safest is to restore that table to a test environment, and use it as documentation for the row level restrictions, which you then MANUALLY add back to the production repository.


Dwayne Hoffpauir :us: (BOB member since 2002-09-19)

I agree with Dwayne :yesnod:

Cause if you restore your repo you will loose today activity (export of unv and doc / user doc exchange / administration …)

Regards

Hi,

Thank you both for your replies.

The situation is that the Business Objects repository is stored on the Oracle production database that is shared by SAP.

The Oracle DBA has told me that they cannot roll back the BusObj repository from last night, as all the SAP data will have to be restored also, which they will NOT do.

The most suitable option is to take a copy of the Test repository from 2 months ago, but I would prefer to only update the tables containing the Universe config data only if possible.

I have lost:
The user groups to which the Universe was assigned
The Universe configuration associated with each group

If you could tell me which tables to restore that would be great, and if this does not work then I will have to consider a full repository reload.
In this case of a full load, will all report files etc be lost also?

Many thanks, John.


John Warne Smith (BOB member since 2005-04-18)

Mister Smith,

Go on OCS web site and download this doc BORepository61b.pdf which contains all the table names you need.

Are you sure informations (links, security, restrictions) are lost. Cause under BO first these informations are set to hidden and then they are deleted when you make a scan and repair. Did you make one today ?

Regards

Hi John,

I am thinking along the same lines as Goiffon & Smith. Are you 100% sure that restoring is the only option available to you? How did you go about replacing the initial corrupted file?


irish_stan :ireland: (BOB member since 2003-05-13)

Hi,

I deleted the corrupted file using the Supervisor module, and then uploaded the local backup of the same Universe file that I keep on my PC.

If there is a way to recover the configuration setting without doing a backup then i would very much appreciate hearing about it.

Even if I backup only a few tables I will have to rebuild the config for user groups that have been created in the last 2 months.

Thanks, John.


John Warne Smith (BOB member since 2005-04-18)

Dwayne solution is the best i think. Just restore the two tables i mentioned above in your test environnement and then recreate the restrictions manually under supervisor in your prod repo.

Regards

Hi,

Thanks for all your help!

So to confirm, is the best approach to copy these two tables from the Test repository into Production (having taken a copy of the 2 current Production tables in case it does not work), and then see if the config is picked up again when I log on using Supervisor?

Will this also re-create the link to the Universe file for each relevant user group?

I may have misunderstood, but the other option I thought you were outlining was to use the data in the Test tables, then manually re-configure the data in Production?

Thanks, John.


John Warne Smith (BOB member since 2005-04-18)

All the links are stored in OBJ_M_RESLINK. What you have to do is to restore last nignt data in your test environnement and then recreate the links and restrictions in prod using supervisor and recreate what you see under test environnement

Regards

Hi,

That sounds like a good approach, but I am not able to connect to the SQ1 database using Supervisor.

I do not have a BO key file for this database, and when I tried to create one using the ‘Admin’ function it said “there is no security domain setup for this connection”.

Is there a way I can connect to Test (which is simply a replication of Prod) using Supervisor, to do what you suggested and manually replicate the config from one environment to the other?

Cheers, John.


John Warne Smith (BOB member since 2005-04-18)

Hi,

The reason I couldn’t create a new BO key for our Test environment is because the Oracle team had created two different username/passwords, only one of which could access the security domain tables.

I am now connected to Test and Production via Supervisor and will replicated the config manually.

Thank you all very much for you time and help - it is greatly appreciated.

Fingers crossed!

Many thanks, John.


John Warne Smith (BOB member since 2005-04-18)

Also you’ll want to get that repository off of the SAP production database! The DBAs should have known better.


b_demann :us: (BOB member since 2003-03-20)