IBM Support

Missing database schemas / catalogs when creating a data module

Technote (troubleshooting)


Problem(Abstract)

A JDBC connection to a data server tests successfully in Cognos Analytics, but schemas and/or catalogs from that data server are missing when creating a data module. The expected schemas / catalogs can be imported successfully into Framework Manager.

Cause

By default, Cognos Analytics filters out system and administrative catalogs / schemas for several types of data server technologies.

Resolving the problem

If the expected schemas/catalogs are 'system' or 'admin' owned, then they may be filtered out by Cognos Analytics' default settings.

Prior to 11.0.5
To change the filtering, you need to edit the corresponding technology's section in the \wlp\usr\servers\cognosserver\moser\import.xml file on the Cognos Analytics server's installation directory.

For example, for Netezza (PDA) remove or comment these lines:

<importRule connection="jdbc:netezza:.*">
<skip>
<catalog>SYSTEM</catalog>
<schema>ADMIN</schema>
</skip>
</importRule>

As of 11.0.5
The Schemas tab of a data server connection has a checkbox for showing the system owned schemas as per the following screenshot.

Related information

Improvements to Loading Database Schema Metadata in R5

Document information

More support for: Cognos Analytics

Software version: 11.0

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Reference #: 1976163

Modified date: 28 November 2016