360Eyes: How to solve the primary key problem with CMS_OVERLOAD

360Eyes: How to solve the primary key problem with CMS_OVERLOAD

Environment

  • Product version(s): Any
  • Third-party technology: SAP BusinessObjects BI 4.x (UNX universes with overloads / security profiles)
  • Database (if applicable): Any

Symptoms

The job fails when it processes a universe that contains overloads (Data Security Profiles or Business Security Profiles).

  • The job ends in error.
  • The job logs show an error referencing a pair of IDs, such as (9604, 2719617): the first one is the snapshot ID, the second one is the overload ID.

Error Message

Example:

Steps to Reproduce

  1. In the Information Design Tool, create two overloads (security profiles) with the same name on the same universe.
  2. Publish the universe.
  3. Run the job on this universe: the error appears in the job logs.

Cause

This problem arises from the duplication of universe overload names.

  • Context: The universe contains at least two Data Security Profiles, or two Business Security Profiles, with the same name.
  • Technical explanation: Overload names (SI_SL_BUSINESS_NAME) must be unique within a universe. When two overloads share the same name, the job cannot process the universe.

Resolution

Identify the overloads that share the same name, then rename them. Until they are renamed, you can exclude the universe from the job.

In the queries below, replace OVERLOAD_ID, UNIVERSE_ID and OVERLOAD_NAME with the values retrieved in the previous steps.

Option 1: Permanent Fix

  1. Retrieve the overload ID from the job logs.

    In the example above, (9604, 2719617), 9604 is the snapshot ID and 2719617 is the overload ID.

  2. Retrieve the universe ID and the overload name from the InfoStore.

    Run this query first, with the overload ID found in the logs:

    select SI_SL_BUSINESS_NAME, SI_ID, SI_CUID, SI_SL_DSP_TO_UNIVERSES
    from CI_APPOBJECTS where SI_SPECIFIC_KIND='DSL.DataSecurityProfile'
    and SI_ID=OVERLOAD_ID

    If it returns nothing, run this one instead:

    select SI_SL_BUSINESS_NAME, SI_ID, SI_CUID, SI_SL_BSP_TO_UNIVERSES
    from CI_APPOBJECTS where SI_SPECIFIC_KIND='DSL.BusinessSecurityProfile'
    and SI_ID=OVERLOAD_ID

    The only difference between these two queries is the SI_SPECIFIC_KIND: Data Security Profile vs Business Security Profile. Note which one returned a result.

    Example of a valid return:

    You now have the universe ID (first ID of SI_SL_DSP_TO_UNIVERSES or SI_SL_BSP_TO_UNIVERSES) and the overload name (SI_SL_BUSINESS_NAME).

  3. Find the duplicates in the InfoStore.

    Use the same SI_SPECIFIC_KIND as the query that returned a result in step 2, and insert the universe ID and the overload name retrieved in step 2.

    For a Data Security Profile:

    select SI_SL_BUSINESS_NAME, SI_ID, SI_CUID
    from CI_APPOBJECTS where SI_SPECIFIC_KIND='DSL.DataSecurityProfile'
    and children("SI_NAME='DSL.Universe-DataSecurityProfile'", "SI_ID=UNIVERSE_ID")
    and SI_SL_BUSINESS_NAME = 'OVERLOAD_NAME'

    For a Business Security Profile:

    select SI_SL_BUSINESS_NAME, SI_ID, SI_CUID
    from CI_APPOBJECTS where SI_SPECIFIC_KIND='DSL.BusinessSecurityProfile'
    and children("SI_NAME='DSL.Universe-BusinessSecurityProfile'", "SI_ID=UNIVERSE_ID")
    and SI_SL_BUSINESS_NAME = 'OVERLOAD_NAME'

    Example of a valid return, showing two overloads with the same name:

  4. Rename the overloads.

    In the Information Design Tool, rename one or both overloads so that they have different names. Overload names must be unique throughout the universe.

Option 2: Workaround

Until the overloads are renamed, exclude the universe from the job:

  1. Retrieve the universe ID (see steps 1 and 2 of Option 1).

  2. Launch the job with this parameter (both id and cuid are accepted):

    -ids_to_exclude=UNIVERSE_ID

Example:

Additional Information

  • If the issue persists, please contact support with your job logs, a screenshot of the query results and the steps you followed in this article.