Category Archives: Berry van den Heuvel

Application Role is not defined in the Enterprise Manager

Problem: Consistency Check Error No. 39051

Screenshot:

39051 Application Role is not defined in the Enterprise Manager

Error text:

[39051] Application Role "BIDelivers" is not defined in the Enterprise Manager.

Solution:

  • decide if you need this role

If you need it, then add it in the Enterprise Manager.

If you don’t need it, follow these steps;

  • close Consistency Check Manager
  • select Manage from the menu
  • click Identity…

Identity Manager

  • select the [ROLE]
  • delete [ROLE]
  • check in rpd
  • do a consistency check (CTRL+K) 

    The error message is gone.

Het bericht Application Role is not defined in the Enterprise Manager verscheen eerst op OBIEE 24/7.

Logical dimension table has a source that does not join to any fact source

Problem: Consistency Check Error no. 39008

Screenshot:

39009 Logical fact table has an aggregate source that does not join to a Dimension source at the proper level of detail

Error text:

[39008] Logical dimension table [LOGICAL_TABLE] has a source [SOURCE_TABLE] that does not join to any fact source.

Solution:

  • edit [LOGICAL_TABLE].[SOURCE_TABLE]
  • select tab Content
  • add the logical levels of the logical dimensions

Logical Table Source - content set

  • check in the rpd
  • do a constency check (CTRL+K)

Now, the error message is not displayed anymore.

Het bericht Logical dimension table has a source that does not join to any fact source verscheen eerst op OBIEE 24/7.

Logical fact table has an aggregate source that does not join to a Dimension

Problem: Consistency Check Error no. 39009

Error text:

[39009] Logical fact table [LOGICAL_TABLE] has an aggregate source [LOGICAL_TABLE].[SOURCE_TABLE] that does not join to a Dimension: [DIMENSION] source at the proper level of detail.

Solution:

  • edit [LOGICAL_TABLE].[SOURCE_TABLE]
  • select tab Content
  • remove or change the logical level of [DIMENSION]

Logical Table Source - content

  • check in the rpd
  • do a constency check (CTRL+K)

Now, the error message is not displayed anymore.

Het bericht Logical fact table has an aggregate source that does not join to a Dimension verscheen eerst op OBIEE 24/7.

Errors were encountered while processing the following catalog paths: 0

Problem: Catalog Manager: error while trying to edit XML

Screenshot:

Catalogmanager error 1

Catalogmanager error 2

Screenshot text:

Errors were encountered while processing the following catalog paths: 0

0 System is in Maintenance Mode. Please try again later.

Solution:

  • log in to OBIEE with the admin user
  • click Administration

Maintenance and troubleshooting

  •  click Toggle Maintenance Mode (the Maintenance Mode is ON now)

Maintenance and troubleshooting ON

  • open Catalog Manager
  • edit XML
  • save file

Now, the error messages are not displayed anymore.

Het bericht Errors were encountered while processing the following catalog paths: 0 verscheen eerst op OBIEE 24/7.

Logical column has no physical data source mapping

Problem: Consistency Check Error no. 38001

Screenshot:

38001 Logical column has no physical data source mapping

Screenshot text:

Error No. 38001 Logical column [TABLE].[COLUMN] has no physical data source mapping.

Solution:

  • (if not already done) open the rpd in online mode
  • (if not already done) import table that contains the physical column
  • (if not already done) drag this physical table to the logical source of [TABLE].[COLUMN]
  • edit logical source [TABLE]
  • choose tab Column Mapping
  • select the physical column for [COLUMN]
  • check in the rpd
  • do a consistency check (CTRL + K)

Now, the error message is not displayed anymore.

Het bericht Logical column has no physical data source mapping verscheen eerst op OBIEE 24/7.