OBJ_M_UNIVSLC Table

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

I am trying to find out what the OBJ_M_UNIVSLC table is used for. I am also trying to find out what action from supervisor/Designer/BO query triggers this table to be updated/inserted/deleted.

Any help would be greatly appreciated.

Thanks
Pavan
kondurp@bscc.bls.com
770-351-1341

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

2

Hi Pavan,

When you open the universe parameters from File…Parameters, there is a description field,
This is stored in OBJ_M_UNIVSLC table.

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

3

I looked up the definition of this table on the CD and it told me that it keeps slices of the universe redefinition. This doesnot help me much. I looked at the table layout and it has 4 columns 1) M_UNIS_N_ID
2) M_UNIS_N_BLKID
3) M_UNIS_N_ID
4) M_UNIS_C_BULK

What i am looking for is what does BO store in each of these columns and what actions cause it to insert data and delete data from this table.

Thanks
Pavan

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

4

Hi, Pavan.

Hamid is correct: the description for the universe is stored in the UNIVSLC table.

Additionally, what you want to know is the following: The UNIVSLC table exists for two reasons: 1. There is no limit to the amount of text you can write into the universe’s description field (a.k.a. the “universe help” field to an end-user) 2. There is a limit of 254 characters per “slice”

And so, any text in this field that is longer than 254 characters will be broken up into slices, which are saved in the UNIVSLC table, and each slice is identified by the following:

  1. M_UNIS_N_ID - Universe repository ID
  2. M_UNIS_N_BLKID - Individual ID of each slice. If your universe description is less than 254 characters, you will have only one slice, with ID=1. Subsequent slices (if your description is more than 254 characters) are numbered accordingly.
  3. M_UNIS_C_NAME - Name of block. The universe description is named “Help” (don’t ask why). I don’t think any other values in this column are possible; the flexibility of the structure allows for future enhancements to the universe domain.
  4. M_UNIS_C_BULK - Bad name for “text.” This column contains the “bulk” of the slice of the full description text.

So, if your universe description is 314 characters, you will have 2 slices (slice 1 with 254 chars., slice 2 with 60), and if you concatenate the “bulk” of the slices, you get your full 314 characters.

Hope this helps.
Luis Gonzalez

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

5

That this information is ALSO stored in UNV_UNIVERSE_DATA, with the same structure. This table contains also other information types, like the comments from the summary tab etc.

I do not really understand the reason for the duplication.

Jean-Francois Cayron

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

6

Luis and Hamid thanks for your response. This informations was really useful.

Do you know why a record would be deleted from this table. For some reason that i dont know there was a record deleted from this table which disabled us to log into the repository from Business Objects. This record corresponding to a specific universe only got deleted from the obj_m_univslc table and did not get deleted from the obj_m_universe table.

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

7

Jean-Francois,

I think the duplication is supposed to save some work. The information stored in OBJ_M_UNIVSLC is used by Supervisor, for example, to quickly present some information on the Universe without accessing the Universe domain (where table UNV_UNIVERSE_DATA is stored).

Cheers,
Luis

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

8

Hi, Pavan.

I can’t think of why if would have been deleted unless you removed the description from the universe.
Sorry I can’t help… hopefully you’ve resolved the issue (with a Scan & Repair, maybe?)…

Cheers,
Luis

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