Troubleshooting
Problem
Customer would like to know what steps are involved in configuring the Controller application servers, before they can use the 'publish to Cognos BI Data Mart' functionality.
Cause
Controller can publish data to 2 different types of 'Data Mart'. You must select one of these when you first define your Data Mart template:
(1) Additional Target = 'none' (unticked)
This publishes data to the same RDBMS database which holds the Controller application data
(2) Additional Target = 'IBMCognos BI'.
This publishes data to a *different* (separate) RDBMS database (different from the Controller application data repository database)
The 'data mart' database may even be located on a completely separate/different server (for example different SQL server) from the one which hosts the Controller application repository database!
This Technote article demonstrates the steps involved in configuring the application server, before you will be able to use the functionality of (2).
More Information:
Previous versions of Controller could also publish data to a third target ("Additional Target = 'MS SSAS'")
(1) Additional Target = 'none' (unticked)
This publishes data to the same RDBMS database which holds the Controller application data
- In general this is not recommended because it will cause your Controller application repository database to grow very large (full of data mart data)
(2) Additional Target = 'IBMCognos BI'.
This publishes data to a *different* (separate) RDBMS database (different from the Controller application data repository database)
- In other words, it publishes Data Mart data to new tables inside a completely separate/unconnected database
- This is recommended by IBM.
The 'data mart' database may even be located on a completely separate/different server (for example different SQL server) from the one which hosts the Controller application repository database!
- Typically (in most scenarios) a customer would have a separate 'Cognos BI' RDBMS target data mart database for each 'application repository' database.
- For example, for repository database 'Controller_live' you would have a corresponding *separate* Data Mart database 'Controller_live_datamart'.
This Technote article demonstrates the steps involved in configuring the application server, before you will be able to use the functionality of (2).
More Information:
Previous versions of Controller could also publish data to a third target ("Additional Target = 'MS SSAS'")
- This published data to an OLAP cube, which resides on a Microsoft MSAS (Analysis Services) server.
- However, this functionality is now no longer supported by IBM.
Environment
These instructions are based on Controller 10.2.1, but (in general) you can use the same instructions for later versions of Controller.
- TIP: For instructions for Controller 8.x, see attached document '20. How to use the 'DmConv' tab inside Controller Configuration to publish CognosBI Data Mart.PDF'.
Resolving The Problem
1. Create new (blank) Data Mart (target) database for *each* separate database connection
2. Configure Controller application server to point to the new Data Mart database(s)
3. Restart Batch Server service to monitor these Data Mart(s).
Steps:
Part One: Create new (blank) Data Mart database for *each* separate database connection
Part Two: Configure Controller application server to point to the new DM databases
1. Logon to Controller application server as an Administrator
2. Launch "Controller Configuration" from the Start Menu
3. Select 'Database connections for publish to datamart'
4. Use the 'select' drop-down menu to choose the relevant database (e.g. 'Controller_live_application')
5. Fill in the details to connect to your 'data mart' database (e.g. 'RC_Controller_live_datamart')
6. Click the green 'tick' to test
7. Click the 'save' icon
8. Now click on 'Database Connections'
9. Highlight the relevant database connection (e.g. 'Controller_live_application')
10. Click on the green 'play' button:
2. Configure Controller application server to point to the new Data Mart database(s)
3. Restart Batch Server service to monitor these Data Mart(s).
Steps:
Part One: Create new (blank) Data Mart database for *each* separate database connection
1. Logon to the database server as an Administrator
2. Create a new database (e.g. 'RC_Controller_live_datamart')
Part Two: Configure Controller application server to point to the new DM databases
1. Logon to Controller application server as an Administrator
2. Launch "Controller Configuration" from the Start Menu
3. Select 'Database connections for publish to datamart'
4. Use the 'select' drop-down menu to choose the relevant database (e.g. 'Controller_live_application')
5. Fill in the details to connect to your 'data mart' database (e.g. 'RC_Controller_live_datamart')
6. Click the green 'tick' to test
7. Click the 'save' icon
8. Now click on 'Database Connections'
9. Highlight the relevant database connection (e.g. 'Controller_live_application')
10. Click on the green 'play' button:
11. Click on the 'browse' button and locate the relevant UDL file:
TIP: By default, for Controller 10.2.x this would be a file similar to: C:\Program Files\ibm\cognos\ccr_64\DMData\Controller_Live.udl.
- IMPORTANT: Make sure you look inside the 'DMData' folder (not the 'Data' folder)!
12. Click to select 'Datamart DB'
13. Look at 'Current Version'.
- If this is '0' then you will need to click 'Create DB'. After this has completed, click 'Upgrade'.
- If this is less than the value inside 'Upgrade to' then you must simply click 'Upgrade'.
14. After seeing the success message, click close:
Part Three: Restart Batch Server service to monitor these Data Marts.
1. Obtain a short period of downtime (specifically, no users running any batch jobs)
2. Click 'Batch Services'
3. Click 'Restart':
Related Information
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9S6B","label":"IBM Cognos Controller"},"ARM Category":[{"code":"a8m0z000000bpPuAAI","label":"Other"}],"ARM Case Number":"","Platform":[{"code":"PF033","label":"Windows"}],"Version":"All Versions","Edition":"Edition Independent","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Historical Number
1039214
Was this topic helpful?
Document Information
Modified date:
23 April 2020
UID
swg21347788