Import InfoSphere Warehouse Cubing Services cube metadata

You can import cube metadata from an IBM® InfoSphere® Warehouse Cubing Services model. IBM Cognos® Cube Designer creates a project with a separate dynamic cube for each cube that is contained in the imported model.

Cognos Cube Designer retains the basic structure of imported cubes and dimensions when you import cube metadata, but there are some differences in underlying InfoSphere Warehouse Cubing Services models that can cause issues during import. The following table describes these issues and suggestions to work around them.

Table 1. Import issues and suggested solutions
Issue Workaround

InfoSphere Warehouse Cubing Services models use name-based member unique names (MUNs) to identify members whereas IBM Cognos Dynamic Cubes uses key-based MUNs.

In Cognos Dynamic Cubes, create the MUN expressions by using the supported Cognos expression syntax.

In InfoSphere Warehouse Cubing Services models, it is possible to create a dimension with multiple hierarchies and reference one single hierarchy in a cube. Cognos Dynamic Cubes does not support hierarchy selection, so all hierarchies are included by each cube that references the dimension.

In Cognos Dynamic Cubes, make a copy of the dimension and delete the unwanted hierarchies. You can then reference the new dimension in a dynamic cube.

Cognos Dynamic Cubes does not support shared attributes. As a result, only the first level that references the attributes contains the attributes. The other levels remain empty.

Delete the empty levels and, where appropriate, create the required attributes by dragging columns to the required levels.

In InfoSphere Warehouse Cubing Services models, expressions are created by using SQL. Cognos Dynamic Cubes converts the attribute references, but not the expression, to the dynamic query mode.

In Cognos Dynamic Cubes, create the expressions by using the supported Cognos expression syntax.

In InfoSphere Warehouse Cubing Services models, if a dimension has an attribute defined that is not part of any level, and the attribute is used to join to a fact table, Cognos Dynamic Cubes incorrectly imports the attribute, adds it to the lowest level, and marks the attribute as hidden.

In Cognos Dynamic Cubes, delete the incorrect attributes manually.

In InfoSphere Warehouse Cubing Services models, if the showMembers property is defined for a hierarchy, this property is lost during import.

In Cognos Dynamic Cubes, manually set the Show Extraneous Padding Members property.

In Cognos Dynamic Cubes, the default member of a hierarchy is not migrated during import.

Manually set the default member property.

Cognos Dynamic Cubes imposes restrictions on certain special characters that are used for cube names and other object names. If an unsupported special character is encountered, an error is shown.

Rename any InfoSphere Warehouse Cubing Services models to remove any unsupported characters before you import them.

In InfoSphere Cubing Services models, it is possible to define attributes under a measure dimension that can be used in expressions. Cognos Dynamic Cubes does not support this feature. Attributes are imported as query items in a measure dimension but are flagged as invalid.

Delete the query items in the measure dimension after you import an InfoSphere Warehouse Cubing Services model.

If security defined for InfoSphere Cubing Services models, it is lost during import.

In Cognos Dynamic Cubes, set up the required security definitions.

A log file is also created during the import process that includes details of any objects that cannot be fully imported.